Method for performing switching between service-based ran and non-service-based ran, and network element and apparatus

Abstract

Provided in the present disclosure are a method for performing switching between a service-based RAN and a non-service-based RAN, and a network element and an apparatus. The method comprises: according to a mapping relationship between a service-based RAN and a non-service-based RAN, a first network element mapping service-based RAN information into non-service-based RAN information, and a non-service-based RAN network element performing switching from the service-based RAN to the non-service-based RAN according to the non-service-based RAN information obtained by means of mapping; or, according to a mapping relationship between the non-service-based RAN and the service-based RAN, the first network element mapping the non-service-based RAN information to the service-based RAN information, and the service-based RAN network element performing switching from the non-service-based RAN to the service-based RAN according to the service-based RAN information obtained by means of mapping.

Description

Switching method, network element and device between service-oriented RAN and non-service-oriented RAN

[0001] This disclosure claims priority to a Chinese patent application filed on June 12, 2023, with application number 202310692742.4 and title “Switching method, network element and device for serviced RAN and non-serviced RAN,” the entire contents of which are incorporated herein by reference. Technical Field

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

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

[0004] When switching from a service-oriented RAN to a non-service-oriented RAN is required, or when switching from a non-service-oriented RAN to a service-oriented RAN is required, there is currently no solution for how to perform the switching between the service-oriented RAN and the non-service-oriented RAN.

[0005] Summary of the Invention

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

[0007] To solve the above problem, an embodiment of the present disclosure 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:

[0008] The first network element maps the serving RAN information to the non-serving RAN information according to the mapping relationship between the serving RAN and the non-serving RAN, and the non-serving RAN network element performs handover from the serving RAN to the non-serving RAN according to the mapped non-serving RAN information;

[0009] or,

[0010] The first network element maps the non-serving RAN information to the serving RAN information according to the mapping relationship between the non-serving RAN and the serving RAN, and the serving RAN network element performs handover from the non-serving RAN to the serving RAN according to the mapped serving RAN information.

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

[0012] NRF network element with network storage function;

[0013] Service-oriented RAN network elements;

[0014] Non-service RAN network elements;

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

[0016] Non-service AMF network element;

[0017] Protocol Data Unit Session Anchor PSA network element.

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

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

[0020] 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.

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

[0022] 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 the non-serving RAN information to the serving RAN information;

[0023] 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.

[0024] Wherein, when the first network element is the non-serving RAN network element, the method further includes:

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

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

[0027] The serving RAN network element receives the non-serving RAN information sent by the non-serving RAN network element.

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

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

[0030] In which case, when the first network element is the non-serving AMF network element, the method further includes:

[0031] 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.

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

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

[0034] Send a third mapping query response to the non-serving AMF network element, where the third mapping query response carries the mapped non-serving RAN information.

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

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

[0037] 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.

[0038] The present disclosure also provides a method for switching between a serving RAN and a non-serving RAN, which is applied to a non-serving RAN network element. The method includes:

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

[0040] The non-serving RAN network element performs handover from the serving RAN to the non-serving RAN according to the mapped non-serving RAN information.

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

[0042] NRF network element with network storage function;

[0043] Service-oriented RAN network elements;

[0044] Non-service RAN network elements;

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

[0046] Non-service AMF network element;

[0047] Protocol Data Unit Session Anchor PSA network element.

[0048] The present disclosure also provides a method for switching between a serviced RAN and a non-serviced RAN, which is applied to a serviced RAN network element. The method includes:

[0049] 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;

[0050] The service-oriented RAN network element performs handover from the non-service-oriented RAN to the service-oriented RAN according to the mapped service-oriented RAN information.

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

[0052] NRF network element with network storage function;

[0053] Service-oriented RAN network elements;

[0054] Non-service RAN network elements;

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

[0056] Non-service AMF network element;

[0057] Protocol Data Unit Session Anchor PSA network element.

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

[0059] 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:

[0060] According to the mapping relationship between the serving RAN and the non-serving RAN, the serving RAN information is mapped to the non-serving RAN information, and the non-serving RAN network element performs handover from the serving RAN to the non-serving RAN based on the mapped non-serving RAN information;

[0061] or,

[0062] According to the mapping relationship between the non-serving RAN and the serving RAN, the non-serving RAN information is mapped to the serving RAN information, and the serving RAN network element performs handover from the non-serving RAN to the serving RAN based on the mapped serving RAN information.

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

[0064] NRF network element with network storage function;

[0065] Service-oriented RAN network elements;

[0066] Non-service RAN network elements;

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

[0068] Non-service AMF network element;

[0069] Protocol Data Unit Session Anchor PSA network element.

[0070] 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:

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

[0072] 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.

[0073] 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:

[0074] 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 the non-serving RAN information to the serving RAN information;

[0075] 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.

[0076] In a case where the first network element is the non-serving RAN network element, the processor is further configured to read the computer program in the memory and perform the following operations:

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

[0078] 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:

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

[0080] In which, when 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:

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

[0082] In which, when the first network element is the non-serving AMF network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0083] 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.

[0084] 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:

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

[0086] Send a third mapping query response to the non-serving AMF network element, where the third mapping query response carries the mapped non-serving RAN information.

[0087] 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:

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

[0089] 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.

[0090] The present disclosure also provides a non-service RAN network element, including a memory, a transceiver, and a processor.

[0091] 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:

[0092] Acquiring mapped non-serving RAN information; wherein the first network element maps the serving RAN information to the non-serving RAN information;

[0093] Handover from the serving RAN to the non-serving RAN is performed according to the mapped non-serving RAN information.

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

[0095] NRF network element with network storage function;

[0096] Service-oriented RAN network elements;

[0097] Non-service RAN network elements;

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

[0099] Non-service AMF network element;

[0100] Protocol Data Unit Session Anchor PSA network element.

[0101] The present disclosure also provides a service-oriented RAN network element, including a memory, a transceiver, and a processor.

[0102] 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:

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

[0104] Handover from the non-service RAN to the service RAN is performed according to the mapped service RAN information.

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

[0106] NRF network element with network storage function;

[0107] Service-oriented RAN network elements;

[0108] Non-service RAN network elements;

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

[0110] Non-service AMF network element;

[0111] Protocol Data Unit Session Anchor PSA network element.

[0112] The present disclosure also provides a device for switching between a service-oriented RAN and a non-service-oriented RAN, including:

[0113] a first mapping unit, configured to map the serving RAN information into non-serving RAN information according to a mapping relationship between the serving RAN and the non-serving RAN, so that the non-serving RAN network element performs handover from the serving RAN to the non-serving RAN according to the mapped non-serving RAN information;

[0114] and / or,

[0115] The second mapping unit is configured to map the non-serving RAN information into the serving RAN information according to the mapping relationship between the non-serving RAN and the serving RAN, and the serving RAN network element performs handover from the non-serving RAN to the serving RAN according to the mapped serving RAN information.

[0116] The present disclosure also provides a device for switching between a service-oriented RAN and a non-service-oriented RAN, including:

[0117] A first acquiring unit is configured to acquire the mapped non-serving RAN information; wherein the first network element maps the serving RAN information to the non-serving RAN information;

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

[0119] The present disclosure also provides a device for switching between a service-oriented RAN and a non-service-oriented RAN, including:

[0120] A second acquiring unit is configured to acquire the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information into the service-oriented RAN information;

[0121] The second switching unit is configured to perform switching from the non-serving RAN to the serving RAN according to the mapped serving RAN information.

[0122] An embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method described above.

[0123] The above technical solution disclosed in the present invention has at least the following beneficial effects:

[0124] In the method, network element, and apparatus for switching between a serviced RAN and a non-serviced RAN according to the embodiments of the present disclosure, a mapping relationship between the serviced RAN and the non-serviced RAN is stored at a first network element, and the first network element performs mapping between serviced RAN information and non-serviced RAN information. Thus, switching between the serviced RAN and the non-serviced RAN is performed by either the non-serviced RAN network element or the serviced RAN network element. This solves the switching problem between the serviced RAN and the non-serviced RAN, avoids communication interruption, and improves user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0125] FIG1 is a block diagram of a wireless communication system to which embodiments of the present disclosure may be applied;

[0126] FIG2 shows a flowchart of one of the steps of the method for switching between a serving RAN and a non-serving RAN provided in an embodiment of the present disclosure;

[0127] FIG3 is a schematic diagram showing a principle of Example 1 provided by an embodiment of the present disclosure;

[0128] FIG4 is a schematic diagram showing the principle of Example 2 provided by an embodiment of the present disclosure;

[0129] FIG5 is a schematic diagram showing the principle of Example 3 provided by an embodiment of the present disclosure;

[0130] FIG6 is a schematic diagram showing the principle of Example 4 provided by an embodiment of the present disclosure;

[0131] FIG7 is a schematic diagram showing the principle of Example 5 provided in an embodiment of the present disclosure;

[0132] FIG8 is a schematic diagram showing the principle of Example 6 provided by an embodiment of the present disclosure;

[0133] FIG9 is a schematic diagram showing the principle of Example 7 provided in an embodiment of the present disclosure;

[0134] FIG10 is a schematic diagram showing the principle of Example 8 provided by an embodiment of the present disclosure;

[0135] FIG11 is a schematic diagram showing the principle of Example 9 provided by an embodiment of the present disclosure;

[0136] FIG12 is a schematic diagram showing the principle of Example 10 provided by an embodiment of the present disclosure;

[0137] FIG13 is a schematic diagram showing a principle of Example 11 provided by an embodiment of the present disclosure;

[0138] FIG14 shows a second flowchart of the method for switching between a serving RAN and a non-serving RAN according to an embodiment of the present disclosure;

[0139] FIG15 shows a flowchart of the third step of the method for switching between a serving RAN and a non-serving RAN according to an embodiment of the present disclosure;

[0140] FIG16 is a schematic structural diagram of a first network element provided in an embodiment of the present disclosure;

[0141] FIG17 is a schematic diagram showing the structure of a non-service RAN network element provided by an embodiment of the present disclosure;

[0142] FIG18 is a schematic diagram showing the structure of a service-oriented RAN network element provided by an embodiment of the present disclosure;

[0143] FIG19 shows one of the structural diagrams of the switching device between the service-oriented RAN and the non-service-oriented RAN provided in an embodiment of the present disclosure;

[0144] FIG20 shows a second structural diagram of the apparatus for switching between a serving RAN and a non-serving RAN provided in an embodiment of the present disclosure;

[0145] FIG21 shows a third structural diagram of the device for switching between a service-oriented RAN and a non-service-oriented RAN provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0147] Figure 1 shows a block diagram of a wireless communication system applicable to embodiments of the present disclosure. The wireless communication system includes a terminal device 101 and a network-side device 102. The terminal device 101 may also be referred to as a terminal or a user equipment (UE). It should be noted that the specific type of the terminal 101 is not limited in the embodiments of the present disclosure. The network-side device 102 may be a base station or a core network. It should be noted that the embodiments of the present disclosure only take the base station in the NR system as an example, but the specific type of the base station is not limited.

[0148] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

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

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

[0151] The technical solution provided by the embodiment of the present disclosure 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.

[0152] The terminal device involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing device connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called User Equipment (UE). A wireless terminal device can 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 "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 voice and / or data with a radio access network. For example, a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiated Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), 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, or a user device, but is not limited in the embodiments of the present disclosure.

[0153] The network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be called another name. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting 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 disclosure may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or code division multiple access (CDMA), a network device (NodeB) in wide-band code division multiple access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present disclosure. 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 geographically separated.

[0154] 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 two-dimensional MIMO (2D-MIMO), three-dimensional MIMO (3D-MIMO), full-dimensional MIMO (FD-MIMO), or massive MIMO. It can also use diversity transmission, precoding, or beamforming.

[0155] As shown in FIG2 , an embodiment of the present disclosure 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:

[0156] Step 201: A first network element maps serving RAN information to non-serving RAN information based on a mapping relationship between the serving RAN and the non-serving RAN. The non-serving RAN network element performs handover from the serving RAN to the non-serving RAN based on the mapped non-serving RAN information.

[0157] or,

[0158] In step 202, the first network element maps the non-serving RAN information to the serving RAN information according to the mapping relationship between the non-serving RAN and the serving RAN. The serving RAN network element performs handover from the non-serving RAN to the serving RAN according to the mapped serving RAN information.

[0159] In the embodiment of the present disclosure, the mapping relationship between the serving RAN and the non-serving RAN, or the mapping relationship between the non-serving RAN and the serving RAN, is stored in the first network element.

[0160] In one implementation, when a serving RAN is to be handed over to a non-serving RAN, a first network element maps serving RAN information to non-serving RAN information based on a mapping relationship between the serving RAN and the non-serving RAN. The non-serving RAN network element then parses the non-serving RAN information to complete the handover from the serving RAN to the non-serving RAN.

[0161] In another implementation, when the non-serving RAN is to be handed over to the serving RAN, the first network element maps the non-serving RAN information to the serving RAN information based on the mapping relationship between the non-serving RAN and the serving RAN. Then, the serving RAN network element parses the serving RAN information to complete the handover from the non-serving RAN to the serving RAN.

[0162] Optionally, when switching from a non-serviced RAN to a serviced RAN, the mapped serviced RAN information includes terminal context information, session information, information between XN interfaces, etc. That is, RAN serviceability can be servicing only the N2 interface, or only the XN interface, or both the N2 interface and the XN interface, without specific limitation here. The XN interface refers to the interface between RAN nodes; the N2 interface refers to the interface between gNB (base station) and the AMF.

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

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

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

[0166] Non-service RAN network elements;

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

[0168] Non-service AMF network element;

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

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

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

[0172] 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.

[0173] In the above embodiment, after receiving the first mapping query response and determining the mapped non-serving RAN information, the serving RAN network element sends the mapped non-serving RAN information to the non-serving RAN network element, and the non-serving RAN network element performs handover from the serving RAN to the non-serving RAN based on the mapped non-serving RAN information.

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

[0175] 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 the non-serving RAN information to the serving RAN information;

[0176] 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.

[0177] In the above embodiment, after the non-serving RAN network element receives the second mapping query response and determines the mapped serving RAN information, it sends the mapped serving RAN information to the serving RAN network element. The serving RAN network element then performs handover from the non-serving RAN to the serving RAN based on the mapped serving RAN information.

[0178] Example 1, as shown in Figure 3, under network element convergence, there is a handover between service-oriented RAN (FRAN) and non-service-oriented RAN (RAN) without user plane function (UPF) redistribution. The first network element is the NRF network element, and mapping is performed at the NRF network element.

[0179] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to NRF, requesting that FRAN information be mapped to RAN information.

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

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

[0182] Step 4: If auxiliary Radio Access Technology (RAT) usage reporting has been configured, the source NG-RAN node during the handover execution phase can provide RAN usage data reporting (auxiliary RAT usage data, handover flag) to the AMF.

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

[0184] Step 6: FAMF+Access Mobility Function (AMF) sends the PDU session information to be switched to the Session Management Function (SMF). SMF initiates PDU session modification based on the PDU session information to be switched and the auxiliary RAT usage data of FRAN, and sends the access network (AN) tunnel information of RAN to UPF+FUPF, while requesting UPF+FUPF to allocate CN (core node) tunnel information.

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

[0186] Step 8: The RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using the FRAN.

[0187] Step 9: Start the registration process.

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

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

[0190] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to UPF+FUPF to request that FRAN information be mapped to RAN information;

[0191] Step 2: After the UPF+FUPF maps the FRAN information to RAN information, it sends a mapping query response to the FRAN, along with the mapped RAN information. Because different sessions may use different PSAs, multiple PSAs exist if there are multiple sessions. When multiple PSAs exist, the mapping relationship can be applied to all PSAs or to the first PSA used when establishing a session. This is not a specific limitation.

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

[0193] 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.

[0194] 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).

[0195] 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 the auxiliary RAT usage data of FRAN, and sends the AN (access node) tunnel information of RAN to UPF+FUPF, while requesting UPF+FUPF to allocate CN (core node) tunnel information.

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

[0197] Step 8: The RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using the FRAN.

[0198] Step 9: Start the registration process.

[0199] Example 3, as shown in Figure 5, under network element fusion, the switching between the service-oriented RAN (FRAN) and the non-service-oriented RAN (RAN) with the intermediate UPF (I-UPF) inserted is performed. The first network element is the NRF network element, and the mapping is performed at the NRF network element.

[0200] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to NRF, requesting that FRAN information be mapped to RAN information.

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

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

[0203] 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.

[0204] 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).

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

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

[0207] Step 8: The RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using the FRAN.

[0208] Step 9: Start the registration process.

[0209] Example 4, as shown in Figure 6, under network element fusion, the switching between the service-oriented RAN (FRAN) and the non-service-oriented RAN (RAN) with the intermediate UPF (I-UPF) inserted is performed. The first network element is the PSA (UPF+FUPF) network element, and the mapping is performed at the PSA network element.

[0210] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to UPF+FUPF to request that FRAN information be mapped to RAN information;

[0211] Step 2: After the UPF+FUPF maps the FRAN information to RAN information, it sends a mapping query response to the FRAN, along with the mapped RAN information. Because different sessions may use different PSAs, multiple PSAs exist if there are multiple sessions. When multiple PSAs exist, the mapping relationship can be applied to all PSAs or to the first PSA used when establishing a session. This is not a specific limitation.

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

[0213] 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.

[0214] 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).

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

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

[0217] Step 8: The RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using the FRAN.

[0218] Step 9: Start the registration process.

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

[0220] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to NRF, requesting that FRAN information be mapped to RAN information.

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

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

[0223] 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.

[0224] 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).

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

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

[0227] Step 8: The RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using the FRAN.

[0228] Step 9: Start the registration process.

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

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

[0231] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to UPF+FUPF to request that FRAN information be mapped to RAN information;

[0232] Step 2: After the UPF+FUPF maps the FRAN information to RAN information, it sends a mapping query response to the FRAN, along with the mapped RAN information. Because different sessions may use different PSAs, multiple PSAs exist if there are multiple sessions. When multiple PSAs exist, the mapping relationship can be applied to all PSAs or to the first PSA used when establishing a session. This is not a specific limitation.

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

[0234] 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.

[0235] 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).

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

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

[0238] Step 8: The RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using the FRAN.

[0239] Step 9: Start the registration process.

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

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

[0242] The non-serving RAN network element receives the serving RAN information sent by the serving RAN network element.

[0243] In the above embodiment, the non-serving RAN network element maps the serving RAN information to the non-serving RAN information based on the mapping relationship between the received serving RAN information and the non-serving RAN; and performs handover from the serving RAN to the non-serving RAN based on the mapped non-serving RAN information.

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

[0245] The serving RAN network element receives the non-serving RAN information sent by the non-serving RAN network element.

[0246] In the above embodiment, the serving RAN network element maps the non-serving RAN information to the serving RAN information based on the received mapping relationship between the non-serving RAN and the serving RAN; and performs handover from the non-serving RAN to the serving RAN based on the mapped serving RAN information.

[0247] Example 7, as shown in Figure 9, under 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

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

[0249] 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.

[0250] 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.

[0251] 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).

[0252] 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 the auxiliary RAT usage data of FRAN, and sends the AN (access node) tunnel information of RAN to UPF+FUPF, while requesting UPF+FUPF to allocate CN (core node) tunnel information.

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

[0254] Step 7: RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using FRAN.

[0255] Step 8: Start the registration process.

[0256] Example 8, as shown in Figure 10, under 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 mapping is performed at the non-serviced RAN network element.

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

[0258] 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.

[0259] 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.

[0260] 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).

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

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

[0263] Step 7: RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using FRAN.

[0264] Step 8: Start the registration process.

[0265] Example 9, as shown in Figure 11, under network element fusion, switching between service-oriented RAN (FRAN) and non-service-oriented RAN (RAN) with intermediate UPF redistribution, the first network element is the non-service-oriented RAN network element, and mapping is performed at the non-service-oriented RAN network element

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

[0267] 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.

[0268] 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.

[0269] 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).

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

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

[0272] Step 7: RAN confirms the handover success by sending a Release Resources message to the source FRAN. It then triggers the release of resources using FRAN.

[0273] Step 8: Start the registration process.

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

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

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

[0277] In the above embodiment, the serving AMF network element maps the serving RAN information to the non-serving RAN information according to the first switching request and the mapping relationship between the serving RAN and the non-serving RAN; and the serving AMF network element transmits 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.

[0278] In other words, when switching between FRAN and RAN under non-network element convergence, 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.

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

[0280] 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.

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

[0282] Example 10, as shown in Figure 12, the handover 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

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

[0284] Step 1: FRAN initiates the handover start;

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

[0286] Step 3: FAMF sends a handover request to S-AMF. S-AMF can store the last used serviced public land mobile network ID (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 fully qualified domain name (FQDN) of the FSMF+SMF for each serviced connection, as well as the IP address and CN tunnel information at the FUPF+UPF for each serviced bearer. The S-RAN selects the T-AMF that can serve the mobile UE. The specific selection method can be queried through the NRF or based on the original local configuration.

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

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

[0289] Step 6: The SMF sends the 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.

[0290] Step 7: S-AMF calls Namf_Communication_CreateUEContext (Create UE context) request to T-AMF, and the main information carried is the 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 data network name (Data Network Name, DNN)).

[0291] 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 request, the target AMF provides the tracking request to the target RAN in the handover request.

[0292] 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).

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

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

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

[0296] 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)).

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

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

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

[0300] Send a third mapping query response to the non-serving AMF network element, where the third mapping query response carries the mapped non-serving RAN information.

[0301] In the above embodiment, after the non-serving AMF network element receives the third mapping query response, 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 based on the mapped non-serving RAN information.

[0302] In other words, when switching between FRAN and RAN under non-network element convergence, when FRAN determines to switch to RAN, S-AMF queries NRF for the mapping relationship between FRAN and RAN information, and then parses FRAN information into RAN information.

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

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

[0305] 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.

[0306] In the above embodiment, after the serving AMF network element receives the fourth mapping query response, it sends the mapped serving RAN information to the serving RAN network element, and the serving RAN network element performs switching from the non-serving RAN to the serving RAN based on the mapped serving RAN information.

[0307] Example 11, as shown in Figure 13, 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

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

[0309] Step 1: FRAN initiates the handover start;

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

[0311] 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. The 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.

[0312] Step 4: S-AMF sends an 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 AMF.

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

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

[0315] 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.

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

[0317] 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 request, the target AMF provides the tracking request to the target RAN in the handover request.

[0318] 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).

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

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

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

[0322] 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)).

[0323] 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).

[0324] In summary, the embodiments of the present disclosure store 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. Thus, the non-serviced RAN network element or the serviced RAN network element performs handover between the serviced RAN and the non-serviced RAN. This solves the handover problem between the serviced RAN and the non-serviced RAN, avoids communication interruption, and improves the user experience.

[0325] As shown in FIG14 , an embodiment of the present disclosure further provides a method for handover between a serving RAN and a non-serving RAN, which is applied to a non-serving RAN network element. The method includes:

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

[0327] Step 1402: The non-serving RAN network element performs handover from the serving RAN to the non-serving RAN according to the mapped non-serving RAN information.

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

[0329] In one implementation, when a serving RAN is to be handed over to a non-serving RAN, a first network element maps serving RAN information to non-serving RAN information based on a mapping relationship between the serving RAN and the non-serving RAN. The non-serving RAN network element then parses the non-serving RAN information to complete the handover from the serving RAN to the non-serving RAN.

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

[0331] NRF network element with network storage function;

[0332] Service-oriented RAN network elements;

[0333] Non-service RAN network elements;

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

[0335] Non-service AMF network element;

[0336] Protocol Data Unit Session Anchor PSA network element.

[0337] In summary, the embodiments of the present disclosure store 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. Thus, the non-serviced RAN network element or the serviced RAN network element performs handover between the serviced RAN and the non-serviced RAN. This solves the handover problem between the serviced RAN and the non-serviced RAN, avoids communication interruption, and improves the user experience.

[0338] As shown in FIG15 , an embodiment of the present disclosure further provides a method for switching between a serviced RAN and a non-serviced RAN, which is applied to a serviced RAN network element. The method includes:

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

[0340] Step 1502: The service-oriented RAN network element performs handover from the non-service-oriented RAN to the service-oriented RAN according to the mapped service-oriented RAN information.

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

[0342] In one implementation, when a non-serving RAN is to be handed over to a serving RAN, a first network element maps non-serving RAN information to serving RAN information based on a mapping relationship between the non-serving RAN and the serving RAN. Then, the serving RAN network element parses the serving RAN information to complete the handover from the non-serving RAN to the serving RAN.

[0343] Optionally, when switching from a non-serviced RAN to a serviced RAN, the mapped serviced RAN information includes terminal context information, session information, information between XN interfaces, etc. That is, RAN serviceability can be servicing only the N2 interface, or only the XN interface, or both the N2 interface and the XN interface, without specific limitation here. The XN interface refers to the interface between RAN nodes; the N2 interface refers to the interface between gNB (base station) and the AMF.

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

[0345] NRF network element with network storage function;

[0346] Service-oriented RAN network elements;

[0347] Non-service RAN network elements;

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

[0349] Non-service AMF network element;

[0350] Protocol Data Unit Session Anchor PSA network element.

[0351] In summary, the embodiments of the present disclosure store 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. Thus, the non-serviced RAN network element or the serviced RAN network element performs handover between the serviced RAN and the non-serviced RAN. This solves the handover problem between the serviced RAN and the non-serviced RAN, avoids communication interruption, and improves the user experience.

[0352] As shown in FIG16 , an embodiment of the present disclosure further provides a first network element, including a memory 1620 , a transceiver 1610 , and a processor 1600 :

[0353] 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:

[0354] According to the mapping relationship between the serving RAN and the non-serving RAN, the serving RAN information is mapped to the non-serving RAN information, and the non-serving RAN network element performs handover from the serving RAN to the non-serving RAN based on the mapped non-serving RAN information;

[0355] or,

[0356] According to the mapping relationship between the non-serving RAN and the serving RAN, the non-serving RAN information is mapped to the serving RAN information, and the serving RAN network element performs handover from the non-serving RAN to the serving RAN based on the mapped serving RAN information.

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

[0358] NRF network element with network storage function;

[0359] Service-oriented RAN network elements;

[0360] Non-service RAN network elements;

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

[0362] Non-service AMF network element;

[0363] Protocol Data Unit Session Anchor PSA network element.

[0364] 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:

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

[0366] 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.

[0367] 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:

[0368] 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 the non-serving RAN information to the serving RAN information;

[0369] 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.

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

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

[0372] 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:

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

[0374] As an optional embodiment, when 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:

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

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

[0377] 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.

[0378] 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:

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

[0380] Send a third mapping query response to the non-serving AMF network element, where the third mapping query response carries the mapped non-serving RAN information.

[0381] 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:

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

[0383] 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.

[0384] In FIG16 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 1600 and memory represented by memory 1620. The bus architecture may also link together various other circuits such as peripheral devices, 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, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. 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.

[0385] 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.

[0386] In the embodiment of the present disclosure, 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. Thus, the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN. This solves the switching problem between the serviced RAN and the non-serviced RAN, avoids the problem of communication interruption, and improves user experience.

[0387] It should be noted here that the above-mentioned first network element provided in the embodiment of the present disclosure 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.

[0388] As shown in FIG17 , an embodiment of the present disclosure further provides a non-service RAN network element, including a memory 1720 , a transceiver 1710 , and a processor 1700 :

[0389] 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:

[0390] Acquiring mapped non-serving RAN information; wherein the first network element maps the serving RAN information to the non-serving RAN information;

[0391] Handover from the serving RAN to the non-serving RAN is performed according to the mapped non-serving RAN information.

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

[0393] NRF network element with network storage function;

[0394] Service-oriented RAN network elements;

[0395] Non-service RAN network elements;

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

[0397] Non-service AMF network element;

[0398] Protocol Data Unit Session Anchor PSA network element.

[0399] In FIG17 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 1700 and memory represented by memory 1720. The bus architecture may also link together various other circuits such as peripheral devices, 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, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. 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.

[0400] 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.

[0401] In the embodiment of the present disclosure, 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. Thus, the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN. This solves the switching problem between the serviced RAN and the non-serviced RAN, avoids the problem of communication interruption, and improves user experience.

[0402] It should be noted that the non-service RAN network element provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effects. 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.

[0403] As shown in FIG18 , an embodiment of the present disclosure further provides a service-oriented RAN network element, including a memory 1820 , a transceiver 1810 , and a processor 1800 .

[0404] 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:

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

[0406] Handover from the non-service RAN to the service RAN is performed according to the mapped service RAN information.

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

[0408] NRF network element with network storage function;

[0409] Service-oriented RAN network elements;

[0410] Non-service RAN network elements;

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

[0412] Non-service AMF network element;

[0413] Protocol Data Unit Session Anchor PSA network element.

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

[0415] 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.

[0416] In the embodiment of the present disclosure, 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. Thus, the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN. This solves the switching problem between the serviced RAN and the non-serviced RAN, avoids the problem of communication interruption, and improves user experience.

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

[0418] As shown in FIG19 , an embodiment of the present disclosure further provides a device for switching between a service-oriented RAN and a non-service-oriented RAN, including:

[0419] A first mapping unit 1901 is configured to map the serving RAN information to the non-serving RAN information according to a mapping relationship between the serving RAN and the non-serving RAN, so that the non-serving RAN network element performs handover from the serving RAN to the non-serving RAN according to the mapped non-serving RAN information;

[0420] and / or,

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

[0422] As an optional embodiment, the first network element is any one of the following: a network storage function NRF network element; a service-oriented RAN network element; a non-service-oriented RAN network element; a service-oriented access and mobility management function AMF network element; a non-service-oriented AMF network element; or a protocol data unit session anchor PSA network element.

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

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

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

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

[0427] A second receiving unit is 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 the NRF network element or the PSA network element to map the non-serving RAN information to the serving RAN information;

[0428] 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.

[0429] As an optional embodiment, when the first network element is the non-serving RAN network element, the apparatus further includes:

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

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

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

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

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

[0435] As an optional embodiment, when the first network element is the non-serving AMF network element, the apparatus further includes:

[0436] 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.

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

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

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

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

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

[0442] An eighth sending unit is configured 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.

[0443] As shown in FIG20 , an embodiment of the present disclosure further provides a device for switching between a service-oriented RAN and a non-service-oriented RAN, including:

[0444] The first acquiring unit 2001 is configured to acquire mapped non-serving RAN information; wherein the first network element maps the serving RAN information to the non-serving RAN information;

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

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

[0447] NRF network element with network storage function;

[0448] Service-oriented RAN network elements;

[0449] Non-service RAN network elements;

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

[0451] Non-service AMF network element;

[0452] Protocol Data Unit Session Anchor PSA network element.

[0453] As shown in FIG21 , an embodiment of the present disclosure further provides a device for switching between a service-oriented RAN and a non-service-oriented RAN, including:

[0454] The second acquiring 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;

[0455] The second switching unit 2102 is configured to perform switching from the non-serving RAN to the serving RAN according to the mapped serving RAN information.

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

[0457] NRF network element with network storage function;

[0458] Service-oriented RAN network elements;

[0459] Non-service RAN network elements;

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

[0461] Non-service AMF network element;

[0462] Protocol Data Unit Session Anchor PSA network element.

[0463] In the embodiment of the present disclosure, 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. Thus, the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN. This solves the switching problem between the serviced RAN and the non-serviced RAN, avoids the problem of communication interruption, and improves user experience.

[0464] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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.

[0465] It should be noted that the division of units in the embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0466] 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 disclosure 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 for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0467] The present disclosure also provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable 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 a floppy disk, a hard disk, a magnetic tape, a magneto-optical (MO)), etc.), optical storage (such as a laser disc (Compact Disk, CD), a digital versatile disc (Digital Versatile Disc, DVD), a Blu-ray Disc (Blu-ray Disc, BD), a high-definition versatile disc (High-Definition Versatile Disc, HVD), etc.), and semiconductor memory (such as ROM, erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable read-only memory (Electrically Erasable Programmable read only memory, EEPROM), non-volatile memory (NAND FLASH), solid-state disk (SSD)), etc.

[0468] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0469] The present disclosure 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 disclosure. 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 produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0470] 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 a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0471] 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, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

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

Claims

1. A method for switching between a service-oriented RAN and a non-service-oriented RAN, applied to a first network element, the method comprising: 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, wherein: 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, wherein: 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, wherein: In the case where the first network element is the NRF network element or the PSA network element, the method further includes: 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 a 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, applied to a non-service-oriented RAN network element, the method comprising: 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, wherein: 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, applied to a service-oriented RAN network element, the method comprising: 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, wherein: 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, comprising a memory, a transceiver, and a 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 mapped non-serviced RAN information; 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 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, wherein: 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, wherein: 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, wherein: 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; Send a second mapping query response to the non-serving RAN network element, wherein the second mapping query response carries Service-oriented RAN information obtained with mapping.

19. The network element according to claim 16, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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: Receive a fourth mapping query request sent by the service-oriented AMF network element, the fourth mapping query request Used to request the NRF network element to map non-service RAN information to service 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, comprising a memory, a transceiver, and a 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: Obtain the mapped non-service RAN information; wherein, The first network element maps the service-oriented RAN information into non-service-oriented 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, wherein: 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, comprising a memory, a transceiver, and a 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: Obtain the mapped service-oriented RAN information; wherein, The first network element maps the non-service RAN information into the service 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, wherein: 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, comprising: 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. The switching device according to claim 29, wherein: 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.

31. The switching device according to claim 30, wherein: In the case where the first network element is the NRF network element or the PSA network element, the device further includes: 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; 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.

32. The switching device according to claim 30, wherein: In the case where the first network element is the NRF network element or the PSA network element, the device further includes: 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; 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.

33. The switching device according to claim 30, wherein: In the case where the first network element is the non-service RAN network element, the device further includes: The third receiving unit is configured to receive service-oriented RAN information sent by a service-oriented RAN network element.

34. The switching device according to claim 30, wherein: In the case where the first network element is the service-oriented RAN network element, the device further includes: The fourth receiving unit is configured to receive non-serving RAN information sent by a non-serving RAN network element.

35. The switching device according to claim 30, wherein: In the case where the first network element is the service-oriented AMF network element, the device further includes: 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.

36. The switching device according to claim 30, wherein: In the case where the first network element is the non-serviced AMF network element, the device further includes: 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.

37. The switching device according to claim 30, wherein: In the case where the first network element is the NRF network element, the device further includes: 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; 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.

38. The switching device according to claim 30, wherein: In the case where the first network element is the NRF network element, the device further includes: An eighth receiving unit is used to receive a fourth mapping query request sent by the service-oriented AMF network element. The fourth mapping query request is used to request the NRF network element to map the non-service RAN information to the service RAN information; 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.

39. A switching device between a service-oriented RAN and a non-service-oriented RAN, comprising: 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.

40. The switching device according to claim 39, wherein: 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.

41. A switching device between a service-oriented RAN and a non-service-oriented RAN, comprising: 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.

42. The switching device according to claim 41, wherein: 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.

43. A processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is used to cause the processor to execute the method described in any one of claims 1 to 10, or the computer program is used to cause the processor to execute the method described in claim 11 or 12, or the computer program is used to cause the processor to execute the method described in claim 13 or 14.

Images