CN112470500B - Apparatus and method for system interworking - Google Patents

Abstract

Provided are a system interworking device and method capable of providing good communication performance and high reliability. A method for system interworking of a user equipment (UE), comprising receiving an indication from a network node, wherein the indication includes an indication of whether a UE capability identification (ID) allocated or used in a current system will be in another system use, and carry out the instructions.

Description

Apparatus and method for system interworking

technical field

The present disclosure relates to the field of communication systems, and more particularly, to devices and methods for system interworking.

Background technique

Universal Terrestrial Radio Access Network (UTRAN) is the radio access network of Universal Mobile Telecommunications System (UMTS), where UTRAN consists of Radio Network Controller (RNC) and nodes B (i.e. radio base station) composition. The Node B communicates wirelessly with the mobile terminal, and the RNC controls the Node B. The RNC is further connected to a core network (Core Network, CN). Evolved UTRAN (Evolved UTRAN, E-UTRAN) is the evolution of UTRAN to high data rate, low delay and packet optimized radio access network. In addition, the E-UTRAN is composed of an interconnected evolved Node B (evolved Node B, eNodeB) further connected to an Evolved Packet Core (EPC) network. E-UTRAN is also called Long Term Evolution (Long Term Evolution, LTE), and is standardized in the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP).

In order to allow a wide range of user equipment (UE) implementations, different UE capabilities are specified. The UE capabilities are divided into parameters which are sent from the user equipment at connection establishment and during an ongoing connection if/when the UE capabilities change. UE capabilities can then be used by the network to select configurations supported by the UE.

In the existing system, when registering or updating, the capability of the terminal is reported to the access network, and then the access network sends the capability of the terminal to the core network for storage. When the terminal initiates a connection establishment request, the access network requests the capability information of the terminal from the core network, and then provides configuration to the terminal according to the capability information of the terminal.

As the terminal supports more and more features, the capability information of the terminal will become larger and larger, which will bring huge signaling overhead. In addition, the core network needs to save the capability information registered by all terminals, which also brings greater challenges to the core network. In the current system interworking, there may be different networks for the UE Capability Management Function (UCMF) deployed in the Fifth Generation System (Fifth Generation System, 5GS) and the Evolved Packet System (Evolved Packet System, EPS) In this framework, the UE cannot determine whether the UE capability identifier (Identity, ID) is used in the source system and is also used in the target system.

Therefore, there is a need for an apparatus and method for system interworking to handle UE capability ID during interworking with different systems.

Contents of the invention

The purpose of the present disclosure is to propose an apparatus and method for system interworking to handle UE capability identification (ID) during interworking with different systems that can provide good communication performance and high reliability.

In a first aspect of the present disclosure, a user equipment (UE) for system interworking includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to control the transceiver to receive an indication from a network node, wherein the indication includes indicating whether the UE capability identification (ID) allocated or used in the current system will be used in another system, and the A processor is configured to execute the instructions.

In a second aspect of the present disclosure, a method for system interworking of a UE includes receiving an indication from a network node, wherein the indication includes indicating whether a UE capability ID allocated or used in the current system will be used in another system , and execute the instructions described.

In a third aspect of the present disclosure, a network node for system intercommunication includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to control the transceiver to send an indication to the UE, where the indication includes indicating whether the UE capability ID allocated or used in the current system will be used in another system.

In a fourth aspect of the present disclosure, a method for system interworking of a network node includes sending an indication to a UE, wherein the indication includes indicating whether a UE capability ID allocated or used in the current system will be in another system use.

In a fifth aspect of the present disclosure, a system for system interworking includes a first network node. How to handle the UE capability identification (ID) is determined based on the behavior of the first network node.

In a sixth aspect of the present disclosure, a method for system interworking includes determining how to handle a UE capability identification (ID) based on behavior of a first network node.

In a seventh aspect of the present disclosure, a non-transitory machine-readable storage medium stores instructions, and the instructions, when executed by a computer, cause the computer to execute the above method.

In an eighth aspect of the present disclosure, a terminal device includes a processor and a memory for storing a computer program. The processor is configured to execute a computer program stored in the memory to perform the above method.

In a ninth aspect of the present disclosure, a network node includes a processor and a memory for storing a computer program. The processor is used to execute the computer program stored in the memory to perform the above method.

Description of drawings

In order to more clearly explain the embodiments of the present disclosure or related technologies, the following drawings that will be described in the embodiments are briefly introduced. Obviously, the drawings are only some embodiments of the present disclosure, and those skilled in the art can obtain other drawings based on these drawings without any preconditions.

Fig. 1 is a block diagram of a user equipment and a network node for system interworking according to an embodiment of the present disclosure.

Fig. 2 is a flow chart illustrating a method for system interworking of a user equipment according to an embodiment of the present disclosure.

Fig. 3 is a flowchart illustrating a method for system interworking of a network node according to an embodiment of the present disclosure.

FIG. 4 is a schematic diagram of an exemplary illustration of a network architecture according to an embodiment of the disclosure.

FIG. 5 is a schematic diagram of an exemplary illustration of an Evolved Packet System (EPS) Radio Access Capability Signaling optimization (Radio Access Capability Signaling optimization, RACS) architecture according to an embodiment of the present disclosure.

FIG. 6 is a schematic diagram of an exemplary illustration of 5GS to EPS handover using the N26 interface according to an embodiment of the present disclosure.

Figure 7 is a schematic diagram of an exemplary illustration of operations between a Next Generation Radio Access Network (NG-RAN) and an Access and Mobility Management Function (AMF) according to an embodiment of the disclosure.

Figure 8 is a schematic diagram of an exemplary illustration of operations between a Next Generation Radio Access Network (NG-RAN) and an Access and Mobility Management Function (AMF) according to an embodiment of the disclosure.

Figure 9 is a schematic diagram of an exemplary illustration of operations between a Next Generation Radio Access Network (NG-RAN) and an Access and Mobility Management Function (AMF) according to an embodiment of the disclosure.

Figure 10 is a schematic diagram of an exemplary illustration of operations between a Next Generation Radio Access Network (NG-RAN) and an Access and Mobility Management Function (AMF) according to an embodiment of the present disclosure.

Figure 11 is a schematic diagram of an exemplary illustration of operations between a Next Generation Radio Access Network (NG-RAN) and an Access and Mobility Management Function (AMF) according to an embodiment of the present disclosure.

12 is a schematic diagram of an exemplary illustration of 5GS to EPS idle mode mobility using the N26 interface according to an embodiment of the disclosure.

FIG. 13 is a schematic diagram of an exemplary illustration of a mobility procedure from 5GS to EPS without an N26 interface according to an embodiment of the present disclosure.

14 is a block diagram of a system for wireless communication according to an embodiment of the disclosure.

Detailed ways

Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings, using technical contents, structural features, realized objects and effects. In particular, the terms in the embodiments of the present disclosure are only used for the purpose of describing specific embodiments, rather than limiting the present disclosure.

Fig. 1 shows that in some embodiments, a user equipment (UE) 10 and a network node 20 for system interworking according to an embodiment of the present disclosure are provided. UE 10 may include processor 11 , memory 12 and transceiver 13 . The network node 20 may comprise a processor 21 , a memory 22 and a transceiver 23 . The processor 11 or 21 may be used to implement suggested functions, procedures and/or methods described in this specification. Multiple layers of the radio interface protocol may be implemented in processor 11 or 21 . The memory 12 or 22 is operatively coupled with the processor 11 or 21 and stores various information to operate the processor 11 or 21 . The transceiver 13 or 23 is operatively coupled with the processor 11 or 21, and the transceiver 13 or 23 transmits and/or receives radio signals.

Processor 11 or 21 may include an Application Specific Integrated Circuit (ASIC), other chipsets, logic circuits and/or data processing devices. Memory 12 or 22 may include read only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. Transceiver 13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (eg, procedures, functions, and so on) that perform the functions described herein. These modules may be stored in the memory 12 or 22 and executed by the processor 11 or 21 . Memory 12 or 22 may be implemented within processor 11 or 21, or external to processor 11 or 21, where these may be communicatively coupled to processor 11 or 21 by various means known in the art.

According to side-link technology developed under 3rd Generation Partnership Project (3GPP) Releases 14, 15, 16 and later, communication between UEs involves vehicle-to-everything (V2X) communication, including vehicle-to-vehicle (V2V ), vehicle-to-pedestrian (V2P), and vehicle-to-infrastructure/network (V2I/N). The UEs communicate directly with each other through a sidelink interface such as the PC5 interface.

In some embodiments, the processor 11 is configured to control the transceiver 13 to receive an indication from the network node 20, wherein the indication includes indicating whether the UE capability ID allocated or used in the current system will be used in another system, And the processor 11 is configured to execute the instructions.

In some embodiments, the current system is one of fifth generation system (5GS) and evolved packet system (EPS), and the other system is the other of 5GS and EPS. The processor 11 is used to perform a registration procedure in the 5GS, and the processor 11 is used to perform an attach procedure in the EPS. The UE capability ID is a capability ID assigned by a Public Land Mobile Network (PLMN).

In some embodiments, the indication also includes whether an interface exists or is co-located between a UE Capability Management Function (UCMF) and a UE Capability Management Element (UCME) of the network node 20 . In some embodiments, the indication is provided in a Registration Accept message, a UE Configuration Update message or a downlink Non-Access Stratum (NAS) message.

In some embodiments, the processor 11 is configured to determine whether to include the UE capability ID in the tracking area update process according to the indication, or the processor 11 is configured to determine to include the UE capability ID in the tracking area update process.

In some embodiments, the processor 11 is configured to determine whether to include the UE capability ID in the attach request process according to the indication, the processor 11 is configured to determine to include the UE capability ID in the attach request process, or the processor 11 uses It is determined not to include the UE capability ID in the attach request procedure.

In some embodiments, the processor 21 is configured to control the transceiver 23 to send an indication to the UE 10, wherein the indication includes indicating whether the UE capability ID allocated or used in the current system will be used in another system.

In some embodiments, the current system is one of fifth generation system (5GS) and evolved packet system (EPS), and the other system is the other of 5GS and EPS. In some embodiments, the Access and Mobility Management Function (AMF) of the network node 20 instructs the UE and the Next Generation Radio Access Network (NG-RAN) of the network node 20 how to handle the UE Capability ID.

In some embodiments, the AMF or UE Capability Management Function (UCMF) of the network node 20 indicates to the UE whether a UE Capability ID allocated or used in the current system will be used in another system. The UE capability ID is a capability ID assigned by a Public Land Mobile Network (PLMN).

In some embodiments, the indication further includes AMF or UCMF, indicating to the UE 10 whether there is an interface between the UCMF and a UE Capability Management Element (UCME) of the network node 20 or whether it is co-located. In some embodiments, the indication is provided in a Registration Accept message, a UE Configuration Update message or a downlink Non-Access Stratum (NAS) message.

In some embodiments, the AMF indicates the information to the NG-RAN using a Non-UE Specific NG Application Protocol (NGAP) message. The AMF or UCMF indicates the information to the NG-RAN using UE specific NGAP messages. The AMF or UCMF indicates the information to the NG-RAN, and the NG-RAN indicates the information to the UE.

In some embodiments, if the NG-RAN knows that the target eNB and the target Mobility Management Entity (MME) support Radio Access Capability Signaling Optimization (RACS) based on local configuration or indication from AMF or UCMF; or, if The NG-RAN knows that the target eNB and/or the target MME is capable of handling the UE Capability ID; or, if the NG-RAN knows that the target eNB and/or the target MME supports RACS and receives a An indication of whether the UE capability ID of the UE will be used in another system; or, if the NG-RAN has received an indication from AMF or UCMF, that the UE radio access capability is not included in the source-to-target transparent container; NG-RAN UE radio access capabilities are not included in the source-to-destination transparent container.

In some embodiments, the NG-RAN is used to send the UE Capability ID to the target Evolved Universal Terrestrial Radio Access Network (E-UTRAN) in a source-to-target transparent container. NG-RAN is used to indicate whether the AMF includes UE radio access capabilities in the source-to-destination transparent container.

In some embodiments, the AMF determines whether to include the UE capability ID in the MME UE context based on the following information: whether the target MME and/or E-UTRAN supports RACS and/or whether UCMF and UCME have a mutual communication interface or co-location; AMF Determine whether to include UE Capability ID in MME UE context based on indication from NG-RAN and/or based on whether target MME and/or E-UTRAN support RACS and/or whether UCMF and UCME have inter-communication interface or co-location; Alternatively, the AMF determines whether to include the UE Capability ID in the MME UE context, not based on NG-RAN behavior and/or based on whether the target MME and/or E-UTRAN supports RACS and/or whether UCMF and UCME have an interface for mutual communication or Colocated.

In some embodiments, if the target MME and/or E-UTRAN supports RACS and/or UCMF and UCME have inter-communication interface or co-location, AMF includes UE capability ID in MME UE context.

In some embodiments, the target MME includes the UE capability ID in the handover request step. Specifically, the target MME includes the UE capability ID in the handover request step based on the RACS-based E-UTRAN capability, and if the E-UTRAN supports RACS, the target MME includes the UE capability ID.

In some embodiments, if the target MME of the network node 20 receives a UE Capability ID from the UE 10, but the target MME has no associated UE radio access capability, the target MME behaves as if the target MME includes the UE in the context request step The capability ID is to operate with the AMF of the network node 20 and the target MME retrieves the UE radio access capabilities from the UCME of the network node 20 to provide the UE capability ID.

In some embodiments, the target MME informs the AMF to provide the associated UE radio access capabilities in the context request step, and the AMF provides the associated UE radio access capabilities to the target MME.

In some embodiments, the target MME of the network node 20 sends a context request message to the AMF of the network node 20, and the AMF provides the target MME with the UE context to include the UE capability ID.

In some embodiments, the target MME includes a request indication in the context request step, if not, the AMF is based on whether the target MME and/or the E-UTRAN of the network node 20 supports RACS and/or whether the UCMF and UCME of the network node 20 have An intercommunicating interface or co-location to provide UE Capability ID.

In some embodiments, if the target MME of the network node has no associated UE radio access capability for the UE capability ID, the target MME retrieves the UE radio access capability from the UCME of the network node 20 and provides the UE capability ID to the UCME. If no UE capability ID is received from the UE 10, the target MME retrieves the UE radio access capabilities from the UCME and provides the UE capability ID to the UCME.

In some embodiments, the determination of how to handle the UE Capability ID is based on the behavior of the AMF. In some embodiments, determining what to do with the UE Capability ID includes determining whether a UE Capability ID allocated or used in the current system, which is the Fifth Generation System (5GS) and the Evolved Packet System (EPS ), will be used in another system. ), and the other system is the other of 5GS and EPS. In some embodiments, the behavior of the AMF includes the AMF instructing the NG-RAN how to handle the UE capability ID, the AMF instructing the user equipment how to handle the UE capability ID, and/or the AMF not instructing the NG-RAN how to handle the UE capability ID, and the NG-RAN Determine how to handle the UE capability ID according to local configuration information.

Fig. 2 shows a method 200 for system intercommunication of a user equipment according to an embodiment of the present disclosure. The method 200 includes: block 202, receiving an indication from a network node, wherein the indication includes indicating whether the UE capability identification (ID) allocated or used in the current system will be used in another system; and block 204, performing the instruct.

In some embodiments, the current system is one of fifth generation system (5GS) and evolved packet system (EPS), and the other system is the other of 5GS and EPS.

In some embodiments, the method further comprises performing a registration procedure in the 5GS and an attach procedure in the EPS. The UE capability ID is a capability ID assigned by a Public Land Mobile Network (PLMN).

In some embodiments, the indication further includes whether an interface exists or is co-located between a UE Capability Management Function (UCMF) and a UE Capability Management Element (UCME) of the network node. In some embodiments, the indication is provided in a Registration Accept message, a UE Configuration Update message or a downlink Non-Access Stratum (NAS) message.

In some embodiments, the method further comprises determining whether to include the UE capability ID in the tracking area update process or determining to include the UE capability ID in the tracking area update process according to the indication. In some embodiments, the method further comprises determining whether to include the UE capability ID in the attach request procedure, determining to include the UE capability ID in the attach request procedure, or determining not to include the UE capability ID in the attach request procedure according to the indication. in progress.

Fig. 3 shows a method 300 for system interworking of a network node according to an embodiment of the present disclosure. The method 300 includes: block 302, sending an indication to a user equipment, wherein the indication includes indicating whether a UE capability ID allocated or used in a current system will be used in another system.

In some embodiments, the current system is one of fifth generation system (5GS) and evolved packet system (EPS), and the other system is the other of 5GS and EPS. In some embodiments, the Access and Mobility Management Function (AMF) of the network node 20 instructs the UE and the Next Generation Radio Access Network (NG-RAN) of the network node 20 how to handle the UE Capability ID.

In some embodiments, the AMF or UE Capability Management Function (UCMF) of the network node 20 indicates to the UE whether a UE Capability ID allocated or used in the current system will be used in another system. The UE capability ID is a capability ID assigned by a Public Land Mobile Network (PLMN). In some embodiments, the indication further includes AMF or UCMF indicating to the UE 10 whether there is an interface or whether there is co-location between the UCMF and a UE Capability Management Element (UCME) of the network node 20 . In some embodiments, the indication is provided in a Registration Accept message, a UE Configuration Update message or a downlink Non-Access Stratum (MAS) message. In some embodiments, the AMF indicates the information to the NG-RAN using a Non-UE Specific NG Application Protocol (NGAP) message. The AMF or UCMF indicates the information to the NG-RAN using UE specific NGAP messages. The AMF or UCMF indicates the information to the NG-RAN, and the NG-RAN indicates the information to the UE.

In some embodiments, if the NG-RAN knows that the target eNB and the target Mobility Management Entity (MME) support Radio Access Capability Signaling Optimization (RACS) based on local configuration or indication from AMF or UCMF; or, if The NG-RAN knows that the target eNB and/or the target MME is capable of handling the UE Capability ID; or, if the NG-RAN knows that the target eNB and/or the target MME supports RACS and receives a An indication of whether the UE capability ID of the UE will be used in another system; or, if the NG-RAN has received an indication from AMF or UCMF, that the UE radio access capability is not included in the source-to-target transparent container; NG-RAN UE radio access capabilities are not included in the source-to-destination transparent container.

In some embodiments, the NG-RAN is used to send the UE Capability ID to the target Evolved Universal Terrestrial Radio Access Network (E-UTRAN) in a source-to-target transparent container. NG-RAN is used to indicate whether the AMF includes UE radio access capabilities in the source-to-destination transparent container.

In some embodiments, the AMF determines whether to include the UE capability ID in the MME UE context based on the following information: whether the target MME and/or E-UTRAN supports RACS and/or whether UCMF and UCME have a mutual communication interface or co-location; AMF Determine whether to include UE Capability ID in MME UE context based on indication from NG-RAN and/or based on whether target MME and/or E-UTRAN support RACS and/or whether UCMF and UCME have inter-communication interface or co-location; Alternatively, the AMF determines whether to include the UE Capability ID in the MME UE context, not based on NG-RAN behavior and/or based on whether the target MME and/or E-UTRAN supports RACS and/or whether UCMF and UCME have an interface for mutual communication or Colocated.

In some embodiments, if the target MME and/or E-UTRAN supports RACS and/or UCMF and UCME have inter-communication interface or co-location, AMF includes UE capability ID in MME UE context.

In some embodiments, the target MME includes the UE capability ID in the handover request step. Specifically, the target MME includes the UE capability ID in the handover request step based on the RACS-based E-UTRAN capability, and if the E-UTRAN supports RACS, the target MME includes the UE capability ID.

In some embodiments, if the target MME of the network node 20 receives a UE Capability ID from the UE 10, but the target MME has no associated UE radio access capability, the target MME behaves as if the target MME includes the UE in the context request step The capability ID is to operate with the AMF of the network node 20 and the target MME retrieves the UE radio access capabilities from the UCME of the network node 20 to provide the UE capability ID.

In some embodiments, the target MME notifies the AMF to provide the associated UE radio access capability in the context request step, and the AMF provides the associated UE radio access capability to the target MME. In some embodiments, the target MME of the network node 20 sends a context request message to the AMF of the network node 20, and the AMF provides the target MME with the UE context to include the UE capability ID.

In some embodiments, the target MME includes a request indication in the context request step, if not, the AMF is based on whether the target MME and/or the E-UTRAN of the network node 20 supports RACS and/or whether the UCMF and UCME of the network node 20 have An intercommunicating interface or co-location to provide UE Capability ID.

In some embodiments, if the target MME of the network node has no associated UE radio access capability for the UE capability ID, the target MME retrieves the UE radio access capability from the UCME of the network node 20 and provides the UE capability ID to the UCME. If no UE capability ID is received from the UE 10, the target MME retrieves the UE radio access capabilities from the UCME and provides the UE capability ID to the UCME.

FIG. 4 is a schematic diagram of an exemplary illustration of a network architecture according to an embodiment of the disclosure. Fig. 4 shows that in some embodiments, in the UE capability optimization mechanism, a UE capability ID is introduced to present a set of UE radio access capabilities. The mapping relationship between UE capability ID and radio access capability is managed in UCMF, which is a new network entity in 5GS. The network architecture is shown in Figure 4.

5 is a schematic diagram of an exemplary illustration of an Evolved Packet System (EPS) Radio Access Capability Signaling Optimization (RACS) architecture according to an embodiment of the disclosure. The same or similar mechanism as in Figure 4 is also introduced in the EPS. Figure 5 shows that, in some embodiments, in EPS, UCMF has the same functionality as in 5GS, connecting MME and AS, optionally via SCEF. There are different alternatives A, B and C for the UCMF-MME interface. In Alternative A, UCMF as specified for 5GS is used for EPS and MME is connected in the same way as AMF in 5GS, ie using SBI. In Alternative B, the UCMF functional entity (possibly named UCME in the EPS architecture) as specified for 5GS connects to the MME using EPS legacy type interfaces/protocols. In Alternative C, UCMF connects MME via RACS-IWF, using SBI UCMF to RACS-IWF, and EPS legacy type interface RACS-IWF to MME, as specified for 5GS. For Alternative A, 5GS and EPS use a unified UCMF, and UE capability IDs for 5GS and EPS are managed in UCMF. For Alternative B, the UCMF used in 5GS and another network entity (such as UCME in EPS) are different entities. These two entities may be deployed at different places and not have any interface to communicate UE capability ID information to each other, or may be co-located or have interfaces to communicate capability ID information to each other.

In some embodiments, when the UE performs interworking between 5GS and EPS, the UE needs to determine whether the capability ID allocated or used in the source system or source RAT can be used in the target system or target RAT. The UE then determines whether to indicate the capability ID in the first NAS message of the target system or RAT.

FIG. 6 is a schematic diagram of an exemplary illustration of 5GS to EPS handover using the N26 interface according to an embodiment of the present disclosure. FIG. 6 shows a solution for intersystem handover using the N26 interface provided in some embodiments. N26 is the interface between AMF and MME over which AMF and MME can forward the UE context during the handover procedure. This embodiment takes the process from 5GS to EPS as an example, and is also applicable to the process from EPS to 5GS. In 5GS, the UE performs a registration procedure, and in EPS, the UE performs an attach procedure. 5GS to EPS handover in single registration mode with N26 interface includes operations as shown in FIG. 6 . In operation 0 (ie step 0), during the UE registration procedure, the AMF instructs the UE and the NG-RAN how to handle UE capabilities. Details are as follows. The indicated information may be that the AMF or UCMF indicates to the UE that the capability ID allocated or used in the source system is used or not used in the target system, such as the EPS in this embodiment. The assigned capability ID is the capability ID assigned by the PLMN. The indicated information may be that AMF or UCMF indicates to UE whether there is an interface or co-location between UCMF and UCME. The messages and procedures shown in Figures 7 to 11 may be AMF or UCMF indicating information to UE in Registration Accept message, or UE Configuration Update message, or any other NAS message from AMF to UE. The message and procedure may be that the AMF indicates the information to the NG-RAN using a non-UE-specific NGAP message, for example, in the NG Setup Response (NG SETUP RESPONSE) message during the NG Setup procedure, as shown in Figure 7 The call flow below. The AMF or UCMF indicates said information to the NG-RAN using a UE-specific NGAP message, such as an Initial Context Setup Request (INITIAL CONTEXTSETUP REQUEST) or a UE Context Modification Request ( UE CONTEXT MODIFICATION REQUEST) message.

Figure 6 shows that in some embodiments, the AMF or UCMF indicates the information to the NG-RAN, and the NG-RAN indicates the information to the UE. In operation 1, the NG-RAN decides that the UE can be handed over to E-UTRA. NG-RAN sends handover request (target eNB ID, direct forwarding path availability, source to target transparent container, inter-system handover indication) message to AMF. If the NG-RAN knows that the target eNB/MME supports RACS based on e.g. local configuration or indication from AMF or UCMF; or, if the NG-RAN knows that the target eNB/MME is capable of handling UE Capability ID; or, if the NG-RAN knows the target eNB /MME supports RACS and receives an indication from the AMF or UCMF that an assigned capability ID or a used capability ID in the source system is used or not used in the target system; or, if the NG-RAN has Received in indication from AMF or UCMF that UE radio capabilities are not included in source to target transparent container; NG-RAN does not include UE radio access capabilities in source to target transparent container. Optionally, the NG-RAN may include the capability ID to the target E-UTRAN in the source-to-target transparent container. Furthermore, the NG-RAN may indicate to the AMF whether to include UE radio capabilities in the source-to-destination transparent container.

Figure 6 shows that in some embodiments, in operation 2, the AMF determines from the "Target eNB Identifier" IE that the type of handover is handover to E-UTRAN. In operation 2, the AMF sends a Forward Relocation Request with the following modifications and clarifications. The AMF determines whether to include the UE capability ID in the MME UE context based on the following information. If 1) and/or 2) are yes, the AMF includes the UE capability ID in the MME UE context. 1) Whether the target MME and/or E-UTRAN supports RACS. 2) Whether UCMF and UCME have an interface for mutual communication or are co-located. Operations 4 and 5 are shown in Figure 6. In operation 6, a handover request with the following modifications is provided. In this step, the MME may include the UE Capability ID. In addition, the RACS-based E-UTRAN capability of MME includes UE capability ID in this step; if E-UTRAN supports RACS, MME includes UE capability ID. Operations 7 to 17 are shown in Figure 6. In operation 18, the UE initiates a tracking area update procedure. The UE determines whether to include the capability ID in this step based on the information received in step 0 (ie operation 0). If the UE receives an indication in step 0 that a capability ID allocated in the source system or a used capability ID is used in the target system or that there is an interface or co-location between UCMF and UCME, the UE includes in this step the capability ID .

12 is a schematic diagram of an exemplary illustration of 5GS to EPS idle mode mobility using the N26 interface according to an embodiment of the disclosure. Figure 12 shows that, in some embodiments, a solution is provided when the UE is in idle mode mobility using the N26 interface. In this embodiment, the MME may receive the UE capability ID from the UE or the AMF. This embodiment takes the process from 5GS to EPS as an example, and is also applicable to the process from EPS to 5GS. In 5GS, the UE performs a registration procedure, and in EPS, the UE performs an attach procedure. In operation 0 (ie, step 0), optionally, as described in operation 0 (step 0) of the embodiment shown in FIG. 6 , the UE receives information from the AMF or UCMF.

Figure 12 shows that in some embodiments, in operations 1 to 3 (ie steps 1 to 3), the UE initiates a tracking area update procedure. The UE determines whether to include the capability ID in the step based on the information received in step 0 (ie operation 0). If the UE receives an indication in step 0 that the capability ID allocated in the source system or the used capability ID is used in the target system, or that there is an interface or co-location between UCMF and UCME, the UE includes in said step capability ID. Instead, the UE will always include the Capability ID in this step.

Figure 12 shows that, in some embodiments, in operations 4 to 6 (i.e. steps 4 to 6), if the MME receives a UE Capability ID from the UE, but the MME does not have an associated UE radio access capability, the MME It can be expressed as follows. 1) The MME includes the UE capability ID in the context request in step 4 to the AMF. Optionally, the MME notifies the AMF to provide associated capabilities. The AMF provides associated capabilities to the MME. 2) MME retrieves UE radio access capabilities from UCME and provides UE capability ID.

Fig. 12 shows that in some embodiments, from an alternative embodiment of operations 4 to 6, the MME sends a context request message to the AMF, and the AMF provides the UE context, including UE capability ID, to the MME. Optionally, the MME may include a request indication in step 4, if not, the AMF provides the ID based on either or both of the following: 1) Whether the target MME and/or E-UTRAN supports RACS; 2) UCMF and UCME Are there inter-communicating interfaces or co-location.

FIG. 13 is a schematic diagram of an exemplary illustration of a mobility procedure from 5GS to EPS without an N26 interface according to an embodiment of the present disclosure. Figure 13 shows that in some embodiments a solution is provided when UE mobility without N26 interface is provided. In this embodiment, the MME may receive the UE capability ID from the UE. This embodiment takes the process from 5GS to EPS as an example, and is also applicable to the process from EPS to 5GS. In 5GS, the UE performs a registration procedure, and in EPS, the UE performs an attach procedure.

FIG. 13 shows that in some embodiments, in operation 0 (ie, step 0), optionally, as described in step 0 (ie, operation 0) of the embodiment shown in FIG. UCMF information. Operations 1 to 4 (ie steps 1 to 4) are shown in FIG. 13 . In operations 5 to 7 (ie steps 5 to 7), the UE initiates an attach request procedure. 1 to 3 have three alternatives. In alternative 1, the UE determines whether to include the capability ID in the step based on the information received in step 0. If the UE receives an indication in step 0 that the capability ID allocated in the source system or the used capability ID is used in the target system, or that there is an interface or co-location between UCMF and UCME, the UE includes in this step the capability ID. In alternative 2, the UE always includes the Capability ID in this step. In alternative 3, the UE does not include the capability ID in this step. In some embodiments, if the MME has no associated UE radio access capability for the UE capability ID, the MME retrieves the UE radio access capability from the UCME, provides the UE capability ID to the UCME. If no UE capability ID is received from the UE, the MME may retrieve and provide the UE capability ID from the UCME to the UCME.

To sum up, the embodiments of the present disclosure provide an apparatus and method for UE processing capability or UE capability ID during interworking with different systems. The network indicates to the UE whether the assigned capability ID can be used for another system or another RAT. The method for the UE to determine the reporting capability, such as whether to report the capability ID allocated in the current system or RAT. The network makes decisions based on network architecture and/or operator policies, etc. This embodiment also provides the behavior of the source RAN during the interworking period, the behavior of the source core network (CN) node during the interworking period, and the behavior of the target CN node during the interworking period. This solution can be applied to inter-RAT mobility, for example, UE moves between NR-RAN to EUTRAN, 3GPP RAT to non-3GPP RAT. This solution can also be applied to inter-PLMN handover.

14 is a block diagram of an example system 700 for wireless communication according to an embodiment of the disclosure. Embodiments described herein may be implemented in a system using any suitably configured hardware and/or software. 14 shows a system 700 that includes radio frequency (RF) circuitry 710, baseband circuitry 720, application circuitry 730, memory/storage 740, display 750, camera 760, sensors 770, and input/output (I/O) interfaces 780, which are coupled to each other at least as shown.

Application circuitry 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Processors may include any combination of general and special purpose processors, such as graphics processors and application processors. The processor may be coupled to the memory/storage and used to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

Baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Processors may include baseband processors. The baseband circuitry can handle various radio control functions, enabling communication with one or more radio networks via radio frequency circuitry. Radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, and the like. In some embodiments, baseband circuitry may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), Wireless Personal Area Networks (WPAN) communication. Embodiments in which baseband circuitry is used to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

In various embodiments, baseband circuitry 720 may include circuitry that operates with signals that are not strictly considered to be at baseband frequencies. For example, in some embodiments, baseband circuitry may include circuitry that operates with signals having an intermediate frequency that is between the baseband frequency and the radio frequency.

RF circuitry 710 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuitry may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network.

In various embodiments, RF circuitry 710 may include circuitry that operates with signals that are not strictly considered radio frequencies. For example, in some embodiments, RF circuitry may include circuitry that operates with signals having an intermediate frequency that is between baseband frequency and radio frequency.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to user equipment, eNB, or gNB may be fully or partially embodied in one or more of RF circuitry, baseband circuitry, and/or application circuitry Among them. As used herein, "circuitry" may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared , dedicated or group), combinational logic circuits, and/or other suitable hardware components that provide the described functionality, or are part of, or include them. In some embodiments, electronic device circuitry may be implemented in one or more software or firmware modules, or functionality associated with the circuitry may be implemented by one or more software or firmware modules.

In some embodiments, some or all of the constituent components of baseband circuitry, application circuitry, and/or memory/storage may be implemented together on a system-on-chip (SOC). Memory/storage 740 may be used to load and store data and/or instructions such as the system. The memory/storage of an embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM), and/or non-volatile memory, such as flash memory. In various embodiments, I/O interface 780 may include one or more user interfaces designed to enable a user to interact with the system and/or peripheral component interfaces designed to enable Peripheral components are able to interact with the system. A user interface may include, but is not limited to, a physical keyboard or keypad, touch pad, speaker, microphone, and the like. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, Universal Serial Bus (USB) ports, audio jacks, and power interfaces. In various embodiments, sensors 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit may also be part of, or interact with, baseband circuitry and/or RF circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites. In various embodiments, display 750 may include displays such as liquid crystal displays and touch screen displays. In various embodiments, system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, tablet computing device, netbook, ultrabook, smartphone, or the like. In various embodiments, the system may have more or fewer components and/or a different architecture. Where appropriate, the methods described herein can be implemented as computer programs. A computer program may be stored on a storage medium, such as a non-transitory storage medium.

In an embodiment of the present disclosure, an apparatus and method for system interworking are provided to handle UE capability ID during interworking with different systems that can provide good communication performance and high reliability. Embodiments of the present disclosure are combinations of techniques/processes that may be employed in 3GPP specifications to create the final product.

Those of ordinary skill in the art understand that each unit, algorithm and step described and disclosed in the embodiments of the present disclosure is implemented using electronic hardware or a combination of computer software and electronic hardware. Whether the functions are implemented in hardware or in software depends on the application conditions and the design requirements of the technology program. Those skilled in the art may implement the functions of each specific application in different ways, and such implementation should not exceed the scope of the present disclosure. Those skilled in the art can understand that he/she can refer to the working process of the systems, devices and units in the above embodiments, because the working processes of the above systems, devices and units are basically the same. For ease of description and simplicity, these working processes will not be described in detail. It should be understood that the systems, devices and methods disclosed in the embodiments of the present disclosure may be implemented in other ways. The above-described embodiments are exemplary only. The division of cells is based only on logical functions, while other divisions exist in implementation. Multiple units or components may be combined or integrated in another system. It is also possible to omit or skip certain features. On the other hand, shown or discussed mutual couplings, direct couplings or communicative couplings operate through some ports, devices or units, either indirectly or through electrical, mechanical or other forms of communication.

Units that are separate components for explanation may or may not be physically separate. The units used for the display may or may not be physical units, ie located at one place or distributed over several network units. Some or all of the units are used depending on the purpose of the embodiment. Furthermore, each functional unit in each embodiment may be integrated in one processing unit, physically independent, or integrated in one processing unit having two or more units. If a software functional unit is implemented and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical solutions proposed in this disclosure may be substantially or partially implemented in the form of software products. Or, a part of the technical solution that facilitates the conventional technology can be realized in the form of a software product. The software product in the computer is stored in a storage medium and includes a plurality of commands for a computing device such as a personal computer, server or network device to execute all or some of the steps disclosed by the embodiments of the present disclosure. Storage media include USB disks, removable hard disks, read only memory (ROM), random access memory (RAM), floppy disks, or other types of media capable of storing program codes.

While the present disclosure has been described in connection with what are considered to be the most practical and preferred embodiments, it is to be understood that the present disclosure is not limited to the disclosed embodiments, but is intended to be covered in the broadest interpretation without departing from the appended claims various arrangements made under the circumstances.

Claims (93)

1. A user equipment UE for system intercommunication, comprising: memory; transceivers; and a processor coupled to the memory and the transceiver, Wherein, the processor is used for: controlling the transceiver to receive an indication from a network node, wherein the indication includes indicating whether the UE capability identification ID allocated or used in the current system will be used in another system; and carry out said directions; Wherein, the access and mobility management function AMF of the network node instructs the UE and the next generation radio access network NG-RAN of the network node how to handle the UE capability ID; the AMF or UCMF indicates information to the NG-RAN, and the NG-RAN indicates the information to the UE; If the NG-RAN knows based on local configuration or the indication from the AMF or the UCMF that the target eNB and/or the target mobility management entity MME supports radio access capability signaling optimized RACS, or if the NG-RAN knows that the target eNB and/or the target MME can handle the UE capability ID, or if the NG-RAN knows that the target eNB and/or the target MME supports the RACS and receives an indication from the AMF or the UCMF whether the UE Capability ID allocated or used in the current system is to be used in the other system, or if the NG-RAN has received an If the AMF or the UCMF indicates that the UE radio access capability is not included in the source-to-target transparent container, the NG-RAN does not include the UE radio access capability in the source-to-target transparent container. 2. The UE according to claim 1, wherein the current system is one of a fifth generation system (5GS) and an evolved packet system (EPS), and the other system is the other of the 5GS and the EPS. 3. The UE of claim 2, wherein the processor is configured to perform a registration procedure in the 5GS and the processor is configured to perform an attach procedure in the EPS. 4. The UE according to any one of claims 1 to 3, wherein the UE capability ID is a capability ID allocated by a public land mobile network (PLMN). 5. The UE according to any one of claims 1 to 3, wherein the indication further includes whether there is an interface or whether there is a co-location between the UE Capability Management Function UCMF of the network node and the UE Capability Management Unit UCME . 6. The UE according to any one of claims 1 to 3, wherein the indication is provided in a registration accept message, a UE configuration update message or a downlink Non-Access Stratum (NAS) message. 7. The UE according to any one of claims 1 to 3, the processor is configured to determine whether to include the UE capability ID in the tracking area update process according to the indication, or the processor is configured to determine whether to include The UE Capability ID is included in the Tracking Area Update procedure. 8. The UE according to any one of claims 1 to 3, the processor is configured to determine whether to include the UE capability ID in the attach request process according to the indication, the processor is configured to determine to include the The UE capability ID is included in the attach request procedure, or the processor is configured to determine not to include the UE capability ID in the attach request procedure. 9. A method for system interworking of a user equipment UE capable of operating with a current system and another system, the method comprising: receiving an indication from a network node, wherein the indication includes indicating whether a UE capability identification ID allocated or used in the current system will be used in the another system; and carry out said directions; Wherein, the access and mobility management function AMF of the network node instructs the UE and the next generation radio access network NG-RAN of the network node how to handle the UE capability ID; the AMF or UCMF indicates information to the NG-RAN, and the NG-RAN indicates the information to the UE; If the NG-RAN knows based on local configuration or the indication from the AMF or the UCMF that the target eNB and/or the target mobility management entity MME supports radio access capability signaling optimized RACS, or if the NG-RAN knows that the target eNB and/or the target MME can handle the UE capability ID, or if the NG-RAN knows that the target eNB and/or the target MME supports the RACS and receives an indication from the AMF or the UCMF whether the UE Capability ID allocated or used in the current system is to be used in the other system, or if the NG-RAN has received an If the AMF or the UCMF indicates that the UE radio access capability is not included in the source-to-target transparent container, the NG-RAN does not include the UE radio access capability in the source-to-target transparent container. 10. The method of claim 9, wherein the current system is one of a fifth generation system (5GS) and an evolved packet system (EPS), and the other system is the other of the 5GS and the EPS . 11. The method of claim 10, further comprising performing a registration procedure in the 5GS, and performing an attach procedure in the EPS. 12. The method according to any one of claims 9 to 11, wherein the UE capability ID is a Public Land Mobile Network (PLMN) UE capability ID. 13. The method according to any one of claims 9 to 11, wherein the indication further comprises whether an interface exists or is co-located between a UE Capability Management Function UCMF and a UE Capability Management Unit UCME of the network node. 14. The method according to any one of claims 9 to 11, wherein the indication is provided in a Registration Accept message, a UE Configuration Update message or a Downlink Non-Access Stratum (NAS) message. 15. The method according to any one of claims 9 to 11, further comprising determining from the indication whether to include the UE capability ID in a tracking area update procedure, or to include the UE capability ID in the tracking area update procedure. During the tracking area update described above. 16. The method according to any one of claims 9 to 11, further comprising determining whether to include the UE capability ID in the attach request process according to the indication, determining to include the UE capability ID in the attach request process, or determine not to include the UE capability ID in the attach request process. 17. A network node for system intercommunication, comprising: memory; transceivers; and a processor coupled to the memory and the transceiver, Wherein, the processor is used for: controlling the transceiver to send an indication to the user equipment UE, where the indication includes indicating whether the UE capability identifier ID allocated or used in the current system will be used in another system; Wherein, the access and mobility management function AMF of the network node instructs the UE and the next generation radio access network NG-RAN of the network node how to handle the UE capability ID; the AMF or UCMF indicates information to the NG-RAN, and the NG-RAN indicates the information to the UE; If the NG-RAN knows based on local configuration or the indication from the AMF or the UCMF that the target eNB and/or the target mobility management entity MME supports radio access capability signaling optimized RACS, or if the NG-RAN knows that the target eNB and/or the target MME can handle the UE capability ID, or if the NG-RAN knows that the target eNB and/or the target MME supports the RACS and receives an indication from the AMF or the UCMF whether the UE Capability ID allocated or used in the current system is to be used in the other system, or if the NG-RAN has received an If the AMF or the UCMF indicates that the UE radio access capability is not included in the source-to-target transparent container, the NG-RAN does not include the UE radio access capability in the source-to-target transparent container. 18. The network node of claim 17, wherein the current system is one of a fifth generation system (5GS) and an evolved packet system (EPS), and the other system is the other of the 5GS and the EPS one. 19. The network node according to claim 17 or 18, wherein the AMF or UE capability management function UCMF of the network node indicates whether the UE capability ID allocated or used by the UE in the current system is will be used in the other system. 20. The network node according to any one of claims 17 or 18, wherein the UE capability ID is a capability ID assigned by a public land mobile network (PLMN). 21. The network node according to claim 19, wherein the indication further comprises the AMF or the UCMF indicating to the UE whether there is an interface between the UCMF and a UE capability management unit (UCME) of the network node Or whether to co-locate. 22. The network node according to any one of claims 17 or 18, wherein the indication is provided in a Registration Accept message, a UE Configuration Update message or a Downlink Non-Access Stratum (NAS) message. 23. The network node according to claim 17 or 18, wherein the AMF indicates information to the NG-RAN using a Non-UE Specific NG Application Protocol (NGAP) message. 24. The network node according to claim 17 or 18, wherein the AMF or UCMF indicates information to the NG-RAN using a UE-specific NGAP message. 25. The network node of claim 17, wherein the NG-RAN is configured to send the UE capability ID in the source-to-target transparent container to a target Evolved Universal Terrestrial Radio Access Network (E-UTRAN). 26. The network node of claim 17, wherein the NG-RAN is to indicate whether the AMF includes UE radio access capabilities in the source-to-target transparent container. 27. The network node according to claim 17 or 18, wherein the AMF determines whether to include the UE capability ID in the MMEUE context based on: whether the target MME and/or E-UTRAN support RACS and/or UCMF whether there is a mutual communication interface or co-location with UCME; the AMF is based on the indication from the NG-RAN and/or based on whether the target MME and/or the E-UTRAN support the RACS and/or Whether the UCMF and the UCME have the interface or co-location for mutual communication, determine whether the UE capability ID is included in the UE context of the MME; or, the AMF determines whether it is in the MME UE context Including UE capability ID, instead of based on NG-RAN behavior and/or based on whether the target MME and/or the E-UTRAN supports the RACS and/or whether the UCMF and the UCME have the mutual communication interface or colocation. 28. The network node according to claim 27, wherein, if the target MME and/or the E-UTRAN supports the RACS and/or the UCMF and the UCME have a mutual communication interface or are co-located, Then the AMF includes UE capability ID in the MME UE context. 29. The network node according to claim 28, wherein the target MME includes the UE capability ID in the handover request step. 30. The network node according to claim 29, wherein the target MME includes the UE capability ID in the handover request step based on the E-UTRAN capability of the RACS, if the E-UTRAN supports the RACS, the target MME includes the UE capability ID. 31. The network node of claim 17, wherein if a target MME of the network node receives the UE capability ID from the UE, but the target MME has no associated UE radio access capability, The target MME then behaves as if the target MME included the UE capability ID in the context request step to operate with the network node's AMF, and the target MME retrieves UE radio access from the network node's UCME Capability to provide the UE Capability ID. 32. The network node according to claim 31 , wherein the target MME informs the AMF to provide associated UE radio access capabilities in the context request step, and the AMF provides the target MME with the The associated UE radio access capabilities. 33. The network node according to claim 17, wherein the target MME of the network node sends a context request message to the AMF of the network node, the AMF provides UE context to the target MME to include the UE capabilities ID. 34. The network node according to claim 33, wherein the target MME includes a request indication in the context request step, if not, the AMF is based on the target MME and/or the network node's E-UTRAN Whether RACS is supported and/or whether the UCMF and UCME of the network node have a mutual communication interface or are co-located to provide the UE capability ID. 35. The network node of claim 17, wherein if the target MME of the network node has no associated UE radio access capability for the UE capability ID, the target MME Retrieving the UE radio access capabilities and providing the UE capability ID to the UCME. 36. The network node according to claim 35, wherein if the UE capability ID is not received from the UE, the target MME retrieves the UE radio access capability from the UCME and sends The UCME provides the UE capability ID. 37. A method for system intercommunication of a network node, comprising: sending an indication to the user equipment UE, wherein the indication includes indicating whether the UE capability ID allocated or used in the current system will be used in another system; Wherein, the access and mobility management function AMF of the network node instructs the UE and the next generation radio access network NG-RAN of the network node how to handle the UE capability ID; the AMF or the UCMF indicates information to the NG-RAN, and the NG-RAN indicates the information to the UE; If the NG-RAN knows based on local configuration or the indication from the AMF or the UCMF that the target eNB and/or the target mobility management entity MME supports radio access capability signaling optimized RACS, or if the NG-RAN knows that the target eNB and/or the target MME can handle the UE capability ID, or if the NG-RAN knows that the target eNB and/or the target MME supports the RACS and receives an indication from the AMF or the UCMF whether the UE Capability ID allocated or used in the current system is to be used in the other system, or if the NG-RAN has received an If the AMF or the UCMF indicates that the UE radio access capability is not included in the source-to-target transparent container, the NG-RAN does not include the UE radio access capability in the source-to-target transparent container. 38. The method of claim 37, wherein the current system is one of a fifth generation system (5GS) and an evolved packet system (EPS), and the other system is the other of the 5GS and the EPS . 39. The method according to claim 37 or 38, wherein the AMF or the UE capability management function (UCMF) of the network node indicates to the UE whether the UE capability ID allocated or used in the current system is will be used in the other system. 40. The method according to any one of claims 37 or 38, wherein the UE capability ID is a Public Land Mobile Network (PLMN) UE capability ID. 41. The method according to claim 39, wherein the indication further comprises the AMF or the UCMF indicating to the UE whether an interface exists between the UCMF and the UE capability management unit (UCME) of the network node Or co-located. 42. The method according to any one of claims 37 or 38, wherein the indication is provided in a Registration Accept message, a UE Configuration Update message or a Downlink Non-Access Stratum (NAS) message. 43. The method of claim 37, wherein the AMF indicates information to the NG-RAN using a Non-UE Specific NG Application Protocol (NGAP) message. 44. The method of claim 39, wherein the AMF or the UCMF indicates information to the NG-RAN using a UE-specific NGAP message. 45. The method of claim 37, wherein the NG-RAN is configured to send the UE capability ID in the source-to-target transparent container to a target Evolved Universal Terrestrial Radio Access Network (E-UTRAN). 46. The method of claim 45, wherein the NG-RAN is to indicate to the AMF whether to include UE radio access capabilities in the source-to-target transparent container. 47. The method according to claim 39, wherein the AMF determines whether to include the UE capability ID in the MME UE context based on: whether the target MME and/or E-UTRAN supports RACS and/or UCMF and UCME Whether there is an interface for mutual communication or co-location; the AMF is based on the indication from the NG-RAN and/or based on whether the target MME and/or the E-UTRAN support the RACS and/or the Whether the UCMF and the UCME have the interface or co-location for mutual communication, determine whether to include the UE capability ID in the MME UE context; or, AMF determines whether to include the UE capability in the MME UE context ID, rather than based on NG-RAN behavior and/or based on whether the target MME and/or the E-UTRAN supports the RACS and/or whether the UCMF and the UCME have the interface or common place. 48. The method according to claim 47, wherein if the target MME and/or the E-UTRAN supports the RACS and/or the UCMF and the UCME have the interface or co-location for mutual communication , the AMF includes UE capability ID in the MME UE context. 49. The method of claim 48, wherein the target MME includes the UE capability ID in the handover request step. 50. The method according to claim 49, wherein the target MME includes the UE capability ID in the handover request step based on the E-UTRAN capability of the RACS, if the E-UTRAN supports the RACS , the target MME includes the UE capability ID. 51. The method of claim 37, wherein if a target MME of the network node receives the UE capability ID from the UE, but the target MME has no associated UE radio access capability, then The target MME behaves as if the target MME includes the UE capability ID in a context request step to operate with the network node's AMF, and the target MME retrieves UE radio access from the network node's UCME Capabilities to provide the UE Capability ID. 52. The method of claim 51, wherein the target MME informs the AMF to provide associated UE radio access capabilities in the context request step, and the AMF provides the target MME with the Associated UE radio access capabilities. 53. The method according to claim 37, wherein the target MME of the network node sends a context request message to the AMF of the network node, the AMF provides UE context to the target MME to include the UE capability ID . 54. The method according to claim 53, wherein the target MME includes a request indication in the context request step, if not, the AMF is based on whether the target MME and/or the E-UTRAN of the network node Whether UCMF and UCME supporting RACS and/or said network node have intercommunicating interfaces or are co-located to provide said UE capability ID. 55. The method of claim 37, wherein if the target MME of the network node has no associated UE radio access capability for the UE capability ID, the target MME retrieves from the UCME of the network node The UE radio access capability, and provides the UE capability ID to the UCME. 56. The method of claim 55, wherein if the UE capability ID is not received from the UE, the target MME retrieves the UE radio access capability from the UCME and sends UCME provides the UE capability ID. 57. A system for system interworking, comprising: The first network node, wherein how to process the UE capability identifier ID is determined based on the behavior of the first network node; a second network node capable of communicating with said first network node, wherein said first network node is an Access and Mobility Management Function AMF, said second network node is a Next Generation Radio Access Network NG-RAN, so The behavior of the AMF includes the AMF instructing the NG-RAN how to process the UE capability ID, the AMF instructing the user equipment how to process the UE capability ID, and/or the AMF not instructing the NG-RAN how to processing the UE capability ID, and the NG-RAN determines how to process the UE capability ID according to local configuration information; If the NG-RAN knows based on local configuration or the indication from the AMF or the UCMF that the target eNB and/or the target mobility management entity MME supports radio access capability signaling optimized RACS, or if the NG-RAN knows that the target eNB and/or the target MME can handle the UE capability ID, or if the NG-RAN knows that the target eNB and/or the target MME supports the RACS and receives an indication from the AMF or the UCMF whether the UE Capability ID allocated or used in the current system is to be used in the other system, or if the NG-RAN has received an If the AMF or the UCMF indicates that the UE radio access capability is not included in the source-to-target transparent container, the NG-RAN does not include the UE radio access capability in the source-to-target transparent container. 58. The system of claim 57, wherein determining how to handle the UE capability ID comprises determining whether the UE capability ID allocated or used in a current system is used in another system, the current system being the first One of the fifth generation system 5GS and the evolved packet system EPS, and the other system is the other of the 5GS and the EPS. 59. The system according to claim 57 or 58, wherein the UE capability ID is a capability ID assigned by a public land mobile network (PLMN). 60. The system of claim 57, wherein the AMF or User Equipment Capability Management Function (UCMF) indicates information to the NG-RAN using a non-UE specific NG Application Protocol (NGAP) message. 61. The system of claim 57, wherein the AMF or UCMF indicates information to the NG-RAN using a UE-specific NGAP message. 62. The system of claim 57, wherein the NG-RAN is to indicate to the AMF whether to include UE radio access capabilities in the source-to-target transparent container. 63. The system of claim 57, wherein the first network node is an NG-RAN, the second network node is a Target Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and the NG-RAN is used for sending said UE capability ID to said E-UTRAN in a source-to-target transparent container. 64. The system according to claim 57, wherein the AMF determines whether to include the UE capability ID in the MME UE context based on: whether the target MME and/or E-UTRAN supports RACS and/or UCMF and UCME Whether there is an interface for mutual communication or co-location; the AMF is based on the indication from the NG-RAN and/or based on whether the target MME and/or the E-UTRAN support the RACS and/or the Whether the UCMF and the UCME have the interface or co-location for mutual communication, determine whether to include the UE capability ID in the MME UE context; or, AMF determines whether to include the UE capability in the MME UE context ID, rather than based on NG-RAN behavior and/or based on whether the target MME and/or the E-UTRAN supports the RACS and/or whether the UCMF and the UCME have the interface or common place. 65. The system according to claim 64, wherein if the target MME and/or the E-UTRAN supports the RACS and/or the UCMF and the UCME have the interface or co-location for mutual communication , the AMF includes the UE capability ID in the MME UE context. 66. The system of claim 65, wherein the target MME includes the UE capability ID in the handover request step. 67. The system of claim 66, wherein the target MME includes the UE capability ID in the handover request step based on the E-UTRAN capability of the RACS, if the E-UTRAN supports the RACS , the target MME includes the UE capability ID. 68. The system of claim 57, wherein if the target MME of the network node receives the UE capability ID from a UE, but the target MME has no associated UE radio access capability, then the the target MME behaves by said target MME including said UE capability ID in a context request step to operate with said network node's AMF, and said target MME retrieves UE radio access capabilities from said network node's UCME, to provide the UE capability ID. 69. The system of claim 68, wherein the target MME informs the AMF to provide associated UE radio access capabilities in the context request step, and the AMF provides the target MME with the Associated UE radio access capabilities. 70. The system according to claim 57, wherein the target MME of the network node sends a context request message to the AMF of the network node, the AMF provides UE context to the target MME to include the UE capability ID . 71. The system according to claim 70, wherein the target MME includes a request indication in the context request step, if not, the AMF is based on whether the target MME and/or the E-UTRAN of the network node Whether UCMF and UCME supporting RACS and/or said network node have intercommunicating interfaces or are co-located to provide said UE capability ID. 72. The system of claim 57, wherein if the target MME of the network node does not have an associated UE radio access capability for the UE capability ID, the target MME retrieves from the UCME of the network node The UE radio access capability, and provides the UE capability ID to the UCME. 73. The system of claim 72, wherein if the UE capability ID is not received from the UE, the target MME retrieves the UE radio access capability from the UCME and provides the UCME with The UE capability ID. 74. A method for system interworking comprising: determining how to process the UE capability ID based on the behavior of the first network node; Wherein, the first network node is an access and mobility management function AMF, the second network node is a next generation radio access network NG-RAN, and the behavior of the AMF includes that the AMF instructs the NG-RAN how to handle The UE capability ID, the AMF instructs the user equipment how to process the UE capability ID, and/or the AMF does not instruct the NG-RAN how to process the UE capability ID, and the NG-RAN according to local configuration information determining how to handle the UE Capability ID; If the NG-RAN knows based on local configuration or the indication from the AMF or the UCMF that the target eNB and/or the target mobility management entity MME supports radio access capability signaling optimized RACS, or if the NG-RAN knows that the target eNB and/or the target MME can handle the UE capability ID, or if the NG-RAN knows that the target eNB and/or the target MME supports the RACS and receives an indication from the AMF or the UCMF whether the UE Capability ID allocated or used in the current system is to be used in the other system, or if the NG-RAN has received an If the AMF or the UCMF indicates that the UE radio access capability is not included in the source-to-target transparent container, the NG-RAN does not include the UE radio access capability in the source-to-target transparent container. 75. The method of claim 74, wherein determining what to do with the UE capability ID comprises determining whether the UE capability ID allocated or used in a current system is used in another system, the current system being the first One of the fifth generation system 5GS and the evolved packet system EPS, and the other system is the other of the 5GS and the EPS. 76. The method according to claim 74 or 75, wherein the UE capability ID is a capability ID assigned by a Public Land Mobile Network (PLMN). 77. The method of claim 74, wherein the AMF or User Equipment Capability Management Function (UCMF) indicates information to the NG-RAN using a Non-UE Specific NG Application Protocol (NGAP) message. 78. The method of claim 74, wherein the AMF or UCMF indicates information to the NG-RAN using a UE-specific NGAP message. 79. The method of claim 74, wherein the NG-RAN is to indicate to the AMF whether to include UE radio access capabilities in the source-to-target transparent container. 80. The method of claim 74, wherein the first network node is an NG-RAN, the second network node is a Target Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and the NG-RAN is used for sending said UE capability ID to said E-UTRAN in a source-to-target transparent container. 81. The method according to claim 74, wherein the AMF determines whether to include the UE capability ID in the MME UE context based on whether the target MME and/or E-UTRAN supports RACS and/or UCMF and UCME Whether there is an interface for mutual communication or co-location; the AMF is based on the indication from the NG-RAN and/or based on whether the target MME and/or the E-UTRAN support the RACS and/or the Whether the UCMF and the UCME have the interface or co-location for mutual communication, determine whether to include the UE capability ID in the MME UE context; or, AMF determines whether to include the UE capability in the MME UE context ID, rather than based on NG-RAN behavior and/or based on whether the target MME and/or the E-UTRAN supports the RACS and/or whether the UCMF and the UCME have the interface or common place. 82. The method according to claim 81, wherein if the target MME and/or the E-UTRAN supports the RACS and/or the UCMF and the UCME have the interface or co-location for mutual communication , the AMF includes UE capability ID in the MME UE context. 83. The method of claim 82, wherein the target MME includes the UE capability ID in the handover request step. 84. The method according to claim 83, wherein the target MME includes the UE capability ID in the handover request step based on the E-UTRAN capability of the RACS, if the E-UTRAN supports the RACS , the target MME includes the UE capability ID. 85. The method of claim 82, wherein if the target MME of the network node receives the UE capability ID from a UE, but the target MME has no associated UE radio access capability, then the the target MME behaves for said target MME to include said UE capability ID in a context request step to operate with said network node's AMF, and said target MME retrieves UE radio access capabilities from said network node's UCME, to provide the UE capability ID. 86. The method of claim 85, wherein the target MME informs the AMF to provide associated UE radio access capabilities in the context request step, and the AMF provides the target MME with the Associated UE radio access capabilities. 87. The method according to claim 74, wherein the target MME of the network node sends a context request message to the AMF of the network node, the AMF provides UE context to the target MME to include the UE capability ID . 88. The method according to claim 87, wherein the target MME includes a request indication in the context request step, if not, the AMF is based on whether the target MME and/or the E-UTRAN of the network node Whether UCMF and UCME supporting RACS and/or said network node have intercommunicating interfaces or are co-located to provide said UE capability ID. 89. The method of claim 74, wherein if the target MME of the network node does not have an associated UE radio access capability for the UE capability ID, the target MME retrieves from the UCME of the network node The UE radio access capability, and provides the UE capability ID to the UCME. 90. The method of claim 89, wherein if the UE capability ID is not received from the UE, the target MME retrieves the UE radio access capability from the UCME and provides the UCME with The UE capability ID. 91. A non-transitory machine readable storage medium having stored thereon instructions which, when executed by a computer, cause the computer to perform any one of claims 9 to 16, 37 to 56 and 74 to 90 the method described. 92. A terminal device, comprising: a processor and a memory for storing a computer program, the processor is used to execute the computer program stored in the memory, to perform the operation described in any one of claims 9 to 16. described method. 93. A network node comprising: a processor and a memory for storing a computer program, said processor being operable to execute said computer program stored in said memory to perform any of claims 37 to 56 and 74 to 90 any one of the methods described.

Images