Method and apparatus for performing onboarding

Abstract

The present application provides a method for performing onboarding. The method includes: a first core network device obtains first information, the first information indicates that a terminal device performs onboarding, the first core network device is a core network device serving the terminal device after the terminal device performs handover, and the first core network device supports an onboarding function. The first core network device performs onboarding for the terminal device based on the first information. According to the solution of the present application, after the terminal device performs handover, the core network device serving the terminal device is a first core network device, and the first core network device supports the onboarding function. After the terminal device performs handover, the core network device serving the terminal device may not support the onboarding function. Therefore, according to the solution of the present application, the first core network device can continue to perform onboarding for the terminal device.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and more specifically, to a method and apparatus for performing onboarding.

Background Art

[0002] After a terminal device accesses an onboarding network, a device in the onboarding network may perform onboarding on the terminal device according to an onboarding policy. If a device in the onboarding network cannot provide services to the terminal device, or if the onboarding network needs to replace the device providing services to the terminal device due to factors such as load balancing and wireless resource status, the terminal device needs to perform a handover, and another device in the onboarding network provides services to the terminal device. However, other devices in the onboarding network may not be able to perform onboarding on the terminal device. Therefore, a method that enables the onboarding network to perform onboarding on the terminal device even after the terminal device performs a handover is an urgent problem to be solved.

Summary of the Invention

[0003] This application provides a method and apparatus for performing onboarding.

[0004] According to a first aspect, a method for performing onboarding is provided. The method includes the following.

[0005] The first core network device obtains first information, where the first information indicates that the terminal device performs onboarding. The first core network device is a core network device that provides services to the terminal device after the terminal device performs handover, and the first core network device supports the onboarding function. The first core network device performs onboarding for the terminal device based on the first information.

[0006] According to the solution of the present application, after the terminal device performs handover, the core network device that provides services to the terminal device is the first core network device, and the first core network device supports the onboarding function. After the terminal device performs handover, the core network device that provides services to the terminal device may not support the onboarding function. Therefore, according to the solution of the present application, the first core network device can continue to perform onboarding for the terminal device.

[0007] Referring to the first aspect, in some implementations of the first aspect, the first core network device obtaining the first information includes the following.

[0008] The first core network device obtains first information from the second core network device, where the second core network device is the core network device that provided services to the terminal device before the terminal device performed handover, or the first core network device obtains first information from the first access network device, where the first access network device is the access network device that provides services to the terminal device after the terminal device performs handover, or the first core network device obtains first information from the terminal device, or the first core network device obtains first information from the third core network device, where the third core network device is the core network device first selected when the terminal device performs handover, and the third core network device does not support the onboarding function.

[0009] Referring to the first aspect, in some implementations of the first aspect, the first information includes one or more of the following: data network name information, network slice information, and information regarding a first value. The first value indicates the period during which the terminal device is registered with the network, or the first value indicates the remaining period during which the terminal device is permitted to register with the network.

[0010] In a possible implementation, after registering with the onboarding network, the terminal device establishes a specific session by using a specific data network name and / or a specific network slice, and it should be understood that the session is restricted to the execution of onboarding.

[0011] Therefore, according to the solution of the present application, the data network name information, the network slice information, and the information regarding the first value can all implicitly instruct the terminal device to perform onboarding.

[0012] Referring to the first aspect, in some implementations of the first aspect, when the first information includes information regarding a first value, the method further includes the following.

[0013] The first core network device starts a first timer, and the start value of the first timer is the first value.

[0014] When the value of the first timer increases to a first threshold, the first core network device executes a deregistration procedure for the terminal device. At this time, the value of the first timer indicates the period during which the terminal device is registered on the network. Or when the value of the first timer decreases to a second threshold, the first core network device executes a deregistration procedure for the terminal device. At this time, the value of the first timer indicates the remaining period during which the terminal device is permitted to register on the network.

[0015] According to the solution of the present application, the first core network device starts the first timer by using the first value as the start value. When the first timer expires, the first core network device executes a deregistration procedure for the terminal device to prevent the terminal device from always being registered on the onboarding network and improve the utilization of network resources.

[0016] Referring to the first aspect, in some implementations of the first aspect, the method further includes the following.

[0017] The first core network device starts a second timer. When the value of the second timer increases to the first threshold or decreases to the second threshold, the first core network device executes a deregistration procedure for the terminal device.

[0018] According to the solution of the present application, the first core network device starts the second timer. When the second timer expires, the first core network device executes a deregistration procedure for the terminal device to prevent the terminal device from always being registered on the onboarding network and improve the utilization of network resources.

[0019] It should be understood that the first timer and the second timer are specific deregistration timers.

[0020] Referring to the first aspect, in some implementations of the first aspect, information regarding the first threshold and / or information regarding the second threshold is preset. Alternatively, the method further includes the first core network device obtaining second information from the second core network device, where the second information indicates the first threshold and / or the second threshold.

[0021] Referring to the first aspect, in some implementations of the first aspect, the first core network device is an access and mobility management function device.

[0022] Referring to the first aspect, in some implementations of the first aspect, the second core network device is an access and mobility management function device.

[0023] Referring to the first aspect, it should be understood that in some implementations of the first aspect, the first core network device may alternatively be a session management function device.

[0024] Referring to the first aspect, it should be understood that in some implementations of the first aspect, the second core network device may alternatively be a session management function device.

[0025] Referring to the first aspect, in some implementations of the first aspect, when the first core network device and the second core network device are session management function devices, the first core network device starts a first timer. The starting value of the first timer may be a first value. When the value of the first timer increases to a first threshold, the first core network device executes a session release procedure for the terminal device. At this time, the value of the first timer indicates the duration of the session established by the terminal device. Alternatively, when the value of the first timer decreases to a second threshold, the first core network device executes a session release procedure for the terminal device. At this time, the value of the first timer indicates the remaining period during which the terminal device is permitted to establish a session.

[0026] Referring to the first aspect, in some implementations of the first aspect, the method further includes the following.

[0027] When the first core network device and the second core network device are session management function devices, the first core network device starts a second timer. When the value of the second timer increases to a first threshold or decreases to a second threshold, the first core network device executes a session release procedure for the terminal device.

[0028] According to the solution of the present application, the first core network device may start a second timer. When the second timer expires, a session release procedure for the terminal device is executed to prevent the terminal device from always maintaining a session in the network and improve the utilization of network resources.

[0029] It should be understood that when both the first core network device and the second core network device are session management function devices, the first timer and the second timer are specific session release timers.

[0030] Referring to the first aspect, in some implementations of the first aspect, when the first core network device and the second core network device are session management function devices, the first value indicates the duration of a session established by the terminal device, or the first value indicates the remaining time for which the terminal device is permitted to establish a session, and the first threshold indicates the longest time for a session that the terminal device can establish. In a possible implementation, the second threshold may be zero.

[0031] According to a second aspect, a method for performing onboarding is provided. The method further includes the following.

[0032] The second core network device selects the first core network device based on third information, where the third information indicates that the terminal device is performing onboarding and the first core network device supports an onboarding function. The second core network device is the core network device that provided services to the terminal device before the terminal device performed a handover, and the first core network device is the core network device that provides services to the terminal device after the terminal device performs a handover. The second core network device transmits the first information to the first core network device, where the first information indicates that the terminal device is performing onboarding, so that the first core network device performs onboarding for the terminal device based on the first information.

[0033] According to the solution of the present application, when the terminal device performs a handover, the second core network device knows that the terminal device is performing onboarding and further selects the first core network device that supports the onboarding function. When the terminal device performs a handover, the core network device selected by the second core network device may not support the onboarding function. Therefore, according to the solution of the present application, the first core network device can continue to perform onboarding for the terminal device.

[0034] Referring to the second aspect, in some implementations of the second aspect, the third information includes one or more of the following: registration type information, data network name information, network slice information, and information regarding a first value. The first value indicates the period during which the terminal device is registered with the network, or alternatively, the first value indicates the remaining period during which the terminal device is permitted to register with the network.

[0035] Alternatively, the method includes the following.

[0036] The second core network device obtains the third information from the second access network device or the terminal device, where the second access network device is the access network device that provided services to the terminal device before the terminal device performed a handover.

[0037] Referring to the second aspect, in some implementations of the second aspect, the first information includes one or more of the following: data network name information, network slice information, and information regarding a first value.

[0038] The first value indicates the period during which the terminal device is registered with the network, or alternatively, the first value indicates the remaining period during which the terminal device is permitted to register with the network.

[0039] Referring to the second aspect, in some implementations of the second aspect, the first core network device is an access and mobility management function device.

[0040] Referring to the second aspect, in some implementations of the second aspect, the second core network device is an access and mobility management function device.

[0041] Referring to the second aspect, it should be understood that in some implementations of the second aspect, the first core network device may alternatively be a session management function device.

[0042] Referring to the second aspect, in some implementations of the second aspect, it should be understood that the second core network device may alternatively be a session management function device.

[0043] Referring to the second aspect, in some implementations of the second aspect, when the first core network device and the second core network device are session management function devices, the first value indicates the duration of the session established by the terminal device, or the first value indicates the remaining period during which the terminal device is permitted to establish a session.

[0044] According to a third aspect, a method for performing onboarding is provided. The method includes the following.

[0045] The first access network device obtains fourth information from the terminal device, where the fourth information indicates that the terminal device is to perform onboarding. The first access network device selects a first core network device based on the fourth information, and the first core network device supports an onboarding function.

[0046] The first access network device is an access network device that provides services to the terminal device after the terminal device performs a handover.

[0047] According to the solution of the present application, when the terminal device performs a handover, the first access network device knows that the terminal device is to perform onboarding and further selects a first core network device that supports the onboarding function. When the terminal device performs a handover, the core network device selected by the first access network device may not support the onboarding function. Therefore, according to the solution of the present application, the first core network device can continue to perform onboarding for the terminal device.

[0048] Referring to the third aspect, in some implementations of the third aspect, the method further includes a first access network device sending first information to a first core network device, where the first information indicates that a terminal device performs onboarding.

[0049] Referring to the third aspect, in some implementations of the third aspect, the first core network device is an access and mobility management function device.

[0050] Referring to the third aspect, it should be understood that in some implementations of the third aspect, the first core network device may alternatively be a session management function device.

[0051] According to a fourth aspect, a method for performing onboarding is provided. The method includes the following.

[0052] A third core network device obtains fifth information, where the fifth information indicates that a terminal device performs onboarding. The third core network device is the first core network device first selected when the terminal device performs a handover, and the third core network device does not support the onboarding function. The third core network device determines a first core network device based on the fifth information, and the first core network device supports the onboarding function.

[0053] According to the solution of the present application, when a terminal device performs a handover, the third core network device selected by the first access network device may not support the onboarding function. In this case, the third core network device knows that the terminal device performs onboarding and further determines a first core network device that supports the onboarding function.

[0054] Referring to the fourth aspect, in some implementations of the fourth aspect, the third core network device obtaining the fifth information includes the third core network device obtaining the fifth information from the second core network device, and the second core network device is a core network device that provides services to the terminal device before the terminal device performs a handover.

[0055] According to the fourth aspect, in some implementations of the fourth aspect, the fifth information includes one or more of the following: data network name information, network slice information, and information regarding a first value.

[0056] The first value indicates the period during which the terminal device is registered with the network, or the first value indicates the remaining period during which the terminal device is permitted to register with the network.

[0057] Referring to the fourth aspect, in some implementations of the fourth aspect, the third core network device obtaining the fifth information includes the third core network device obtaining the fifth information from the terminal device.

[0058] Referring to the fourth aspect, in some implementations of the fourth aspect, determining the first core network device includes the following.

[0059] The third core network device determines the first core network device based on the preconfigured capability information of at least one core network device.

[0060] Referring to the fourth aspect, in some implementations of the fourth aspect, the method further includes the following.

[0061] The third core network device sends a first request message to the fourth core network device, and the first request message is used to request to obtain information about the core network device that supports the onboarding function. The third core network device receives a first response message from the fourth core network device, and the first response message includes information about the first core network device.

[0062] Determining the first core network device includes the following.

[0063] The third core network device determines the first core network device based on the first response message.

[0064] Referring to the fourth aspect, in some implementations of the fourth aspect, the information about the first core network device includes the identification information of the first core network device and / or the address information of the first core network device.

[0065] Referring to the fourth aspect, in some implementations of the fourth aspect, the method further includes the third core network device sending first information to the first core network device, and the first information indicates that the terminal device performs onboarding.

[0066] Referring to the fourth aspect, in some implementations of the fourth aspect, the first information includes one or more of the following: data network name information, network slice information, and information about a first value.

[0067] The first value indicates the period during which the terminal device is registered with the network, or the first value indicates the remaining period during which the terminal device is permitted to register with the network.

[0068] Referring to the fourth aspect, in some implementations of the fourth aspect, the first core network device is an access and mobility management function device.

[0069] Referring to the fourth aspect, in some implementations of the fourth aspect, the second core network device is an access and mobility management function device.

[0070] Referring to the fourth aspect, in some implementations of the fourth aspect, the third core network device is an access and mobility management function device.

[0071] Referring to the fourth aspect, in some implementations of the fourth aspect, the fourth core network device is a network storage function device.

[0072] Referring to the fourth aspect, it should be understood that in some implementations of the fourth aspect, the first core network device may alternatively be a session management function device.

[0073] Referring to the fourth aspect, it should be understood that in some implementations of the fourth aspect, the second core network device may alternatively be a session management function device.

[0074] Referring to the fourth aspect, it should be understood that in some implementations of the fourth aspect, the third core network device may alternatively be a session management function device.

[0075] Referring to the fourth aspect, in some implementations of the fourth aspect, when the first core network device, the second core network device, and the third core network device are session management function devices, the first value indicates the duration of the session established by the terminal device, or alternatively, the first value indicates the remaining period during which the terminal device is permitted to establish a session.

[0076] According to a fifth aspect, a communication device is provided. The communication device includes a unit configured to execute the method in the first aspect or an implementation of the first aspect.

[0077] According to a sixth aspect, a communication device is provided. The communication device includes a unit configured to execute the method in the second aspect or an implementation of the second aspect.

[0078] According to a seventh aspect, a first access network device is provided. The first access network device is a transceiver unit configured to obtain fourth information from a terminal device, where the fourth information indicates that the terminal device is performing onboarding, and the transceiver unit, is a processing unit configured to select a first core network device based on the fourth information, where the first core network device supports an onboarding function, and the processing unit including. The first access network device is an access network device that provides services to the terminal device after the terminal device performs a handover.

[0079] Referring to the seventh aspect, in some implementations of the seventh aspect, the transceiver unit is further configured to transmit first information to the first core network device, where the first information indicates that the terminal device is performing onboarding.

[0080] Referring to the seventh aspect, in some implementations of the seventh aspect, the first core network device is an access and mobility management function device.

[0081] Referring to the seventh aspect, it should be understood that in some implementations of the seventh aspect, the first core network device may alternatively be a session management function device.

[0082] According to an eighth aspect, a third core network device is provided. The third core network device A transceiver unit configured to obtain fifth information, where the fifth information indicates that the terminal device performs onboarding, and the third core network device is the core network device first selected when the terminal device performs handover, and the third core network device does not support the onboarding function, the transceiver unit, A processing unit configured to determine a first core network device based on the fifth information, where the first core network device supports the onboarding function, the processing unit including.

[0083] Referring to the eighth aspect, in some implementations of the eighth aspect, the fact that the transceiver unit is configured to obtain large and information includes the following.

[0084] The transceiver unit is configured to obtain the fifth information from a second core network device, where the second core network device is the core network device that provides services to the terminal device before the terminal device performs handover.

[0085] Referring to the eighth aspect, in some implementations of the eighth aspect, the fifth information includes one or more of the following: data network name information, network slice information, and information regarding a first value.

[0086] The first indicates the period during which the terminal device is registered with the network, or the first value indicates the remaining period during which the terminal device is permitted to register with the network.

[0087] Referring to the eighth aspect, in some implementations of the eighth aspect, the fact that the transceiver unit is configured to obtain the fifth information includes the fact that the transceiver unit is configured to obtain the fifth information from the terminal device.

[0088] Referring to the eighth aspect, in some implementations of the eighth aspect, determining the first core network device includes the following.

[0089] The processing unit is further configured to determine the first core network device based on pre - set capability information of at least one core network device.

[0090] Referring to the eighth aspect, in some implementations of the eighth aspect, the transceiver unit is further configured to send a first request message to the fourth core network device, and the first request message is used to request to obtain information about the core network device that supports the on - boarding function. The transceiver unit is further configured to receive a first response message from the fourth core network device, and the first response message includes information about the first core network device.

[0091] Determining the first core network device includes the following.

[0092] The processing unit is further configured to determine the first core network device based on the first response message.

[0093] Referring to the eighth aspect, in some implementations of the eighth aspect, the transceiver unit is further configured to send first information to the first core network device, and the first information indicates that the terminal device is performing on - boarding.

[0094] Referring to the eighth aspect, in some implementations of the eighth aspect, the information about the first core network device includes the identification information of the first core network device and / or the address information of the first core network device.

[0095] Referring to the eighth aspect, in some implementations of the eighth aspect, the first information includes one or more of the following: data network name information, network slice information, and information about the first value.

[0096] The first value indicates the period during which the terminal device is registered with the network, or alternatively, the first value indicates the remaining period during which the terminal device is permitted to register with the network.

[0097] Referring to the eighth aspect, in some implementations of the eighth aspect, the first core network device is an access and mobility management function device.

[0098] Referring to the eighth aspect, in some implementations of the eighth aspect, the second core network device is an access and mobility management function device.

[0099] Referring to the eighth aspect, in some implementations of the eighth aspect, the third core network device is an access and mobility management function device.

[0100] Referring to the eighth aspect, in some implementations of the eighth aspect, the fourth core network device is a network storage function device.

[0101] Referring to the eighth aspect, it should be understood that in some implementations of the eighth aspect, the first core network device may alternatively be a session management function device.

[0102] Referring to the eighth aspect, it should be understood that in some implementations of the eighth aspect, the second core network device may alternatively be a session management function device.

[0103] Referring to the eighth aspect, it should be understood that in some implementations of the eighth aspect, the third core network device may alternatively be a session management function device.

[0104] Referring to the eighth aspect, in some implementations of the eighth aspect, when the first core network device, the second core network device, and the third core network device are session management function devices, it should be understood that the first value indicates the duration of the session established by the terminal device, or the first value indicates the remaining period during which the terminal device is permitted to establish a session.

[0105] According to the ninth aspect, a communication device including at least one processor is provided. The memory is configured to store a computer program. When the communication device operates, the processor executes the computer program or instructions stored in the memory, whereby the communication device executes a method according to any possible implementation of the first aspect to the fourth aspect. The memory may be located in the processor, or may be implemented by using a chip independent of the processor. This is not particularly limited in this application.

[0106] According to the tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program. When the computer program is executed by a computer, the computer can execute a method according to any possible implementation of the first aspect to the fourth aspect.

[0107] According to the eleventh aspect, a chip is provided. A processing circuit is arranged on the chip, and the processing circuit is configured to execute a method according to any possible implementation of the first aspect to the fourth aspect.

[0108] According to the twelfth aspect, a computer program product is provided. The computer program product includes a computer program (which may also be referred to as code or instructions). When the computer program is executed, the computer can execute a method according to any possible implementation of the first aspect to the fourth aspect.

Brief Description of the Drawings

[0109]

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 4

Figure 5

Figure 6

Figure 7

Embodiments for Carrying Out the Invention

[0110] The following describes the technical solution of the present application with reference to the accompanying drawings. Obviously, the described embodiments are part of but not all of the embodiments of the present application. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without creative efforts should fall within the protection scope of the present application.

[0111] The technical solution in the embodiments of the present application may be applicable to various communication systems, such as narrowband internet of things (NB-IoT) systems, global system for mobile communications (GSM), code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) systems, general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems or new radio (NR) systems, satellite communication systems, and future 6th generation (6G) systems.

[0112] The technical solution provided in the present application may be applicable to the system architecture shown in FIG. 1. The following describes the network elements that may be included in the system architecture shown in FIG. 1.

[0113] 1. User equipment (UE)

[0114] The UE may also be referred to as a terminal device, an access terminal, a terminal device unit (subscriber unit), a terminal device station, a mobile console, a mobile station (MS), a remote station, a mobile device, a user terminal, a terminal, a wireless communication device, a terminal device agent, or a terminal device apparatus. The terminal device may include various handheld devices, in-vehicle devices, Internet of Things (IoT) devices, wearable devices, computing devices, or other processing devices connected to a wireless modem having a wireless communication function. The terminal device may further include a user unit, a cellular phone, a smartphone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem, a handheld device (handset), a laptop computer, a machine type communications (MTC) terminal, or a station (ST) in a wireless local area network (WLAN). The terminal device may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, and a terminal device in a next-generation communication system, such as a 5G network, or a terminal device in a future evolved PLMN network.

[0115] 2. Access Network Device

[0116] An access network device is a device that provides a wireless communication function for a terminal device. For example, the access network device may be an access point (AP) in a WLAN, a base transceiver station (BTS) in GSM or CDMA, a Node B (NB) in WCDMA, a gNB in a new radio (NR) system, an evolved Node B (eNB or eNodeB) in LTE, or a radio access network (RAN) device in a 5G network.

[0117] 3. User Plane Network Element

[0118] The user plane network element is configured to perform packet routing and forwarding, quality of service (QoS) processing of user plane data, and so on.

[0119] In a 5G communication system, the user plane network element may be a user plane function (UPF) network element. In future communication systems, the user plane network element may still be a UPF network element, or may have other names. This is not limited in this application.

[0120] 4. Data Network

[0121] The data network is a network for data transmission.

[0122] In a 5G communication system, the data network may be a data network (DN). In future communication systems, the data network may still be a DN, or may have other names. This is not limited in this application.

[0123] 5. Access Management Network Element

[0124] The access management network element is mainly used for mobility management, access management, etc., and may be configured to perform functions other than session management in the functions of a mobility management entity (MME), such as legal interception and access permission / authentication.

[0125] In a 5G communication system, the access management network element may be an access and mobility management function (AMF) network element or an access and mobility management function device. In future communication systems, the access and mobility management network element may still be an AMF network element, or may have other names. This is not limited in this application. The access and mobility management function device may be a core network device.

[0126] 6. Session Management Network Element

[0127] The session management network element is mainly configured to manage sessions, assign and manage the Internet protocol (IP) addresses of terminal devices, select endpoints that can manage user plane function interfaces and policy control and charging function interfaces, notify downlink data, etc.

[0128] In a 5G communication system, the session management network element may be a session management function (SMF) network element or a session management function device. In future communication systems, the session management network element may still be an SMF network element, or may have another name. This is not restricted in this application. The session management function device may be a core network device.

[0129] 7. Policy control network element

[0130] The policy control network element is configured to guide a unified policy framework for network operations and provide policy rule information for control plane function network elements (for example, an AMF network element or an SMF network element), etc.

[0131] In a 4G communication system, the policy control network element may be a policy and charging rules function (PCRF) network element. In a 5G communication system, the policy control network element may be a policy control function (PCF) network element or a policy control function device. In future communication systems, the policy control network element may still be a PCF network element, or may have another name. This is not restricted in this application. The policy control function device may be a core network device.

[0132] 8. Unified data repository (UDR) network element

[0133] The UDR network element is configured to provide subscription data for the UDM network element or obtain subscription data from the UDM network element, provide policy data for the PCF network element or obtain policy data from the PCF network element, etc. In future communication systems, the UDR network element may often be referred to as an integrated data repository function device, or may have other names. This is not limited in this application. The integrated data repository function device may be a core network device.

[0134] 9. Data Management Network Element

[0135] The data management network element is configured to provide a terminal device identifier, perform access authentication, registration, and mobility management, etc.

[0136] In a 5G communication system, the data management network element may be a unified data management (UDM) network element or an integrated data management device. In future communication systems, the integrated data management network element may still be a UDM network element, or may have other names. This is not limited in this application. The integrated data management device may be a core network device.

[0137] 10. Network Exposure Function Network Element

[0138] The network exposure function network element is mainly configured to securely expose services and capabilities provided by 3GPP network functions, including exposing services and capabilities internally and exposing services and capabilities to third parties.

[0139] In a 5G communication system, the network exposure function network element may be a network exposure function (NEF) network element or a network exposure function device. In future communication systems, the network exposure function network element may still be an NEF network element, or may have other names. This is not restricted in this application. The network exposure function device may be a core network device.

[0140] 11. Application function (AF) network element

[0141] The AF network element is configured to perform information exchange between an external server and the 3GPP network.

[0142] It can be understood that the network element or function may be a network element within a hardware device, a software function executed by dedicated hardware, or a virtualized function instantiated on a platform (such as a cloud platform).

[0143] 12. Network repository function (NRF) network element

[0144] The NRF network element may also be referred to as a network storage function device, a network repository function device, or a network repository function network element. The functional network element may support a service discovery function. A network element discovery request may be received from a network element function or a service communication proxy (SCP), and information on the discovered network element function may be fed back. Further, the network element function is also involved in maintaining information on available network functions and the services supported by the network functions. The so-called discovery procedure is a process in which the requesting network element function (NF) assists the NRF in addressing a specific NF or a specific service. The NRF provides the IP address, FQDN, or URI of the corresponding NF instance or the corresponding NF service instance. The NRF may further implement an inter-PLMN discovery procedure by providing a network identifier (e.g., a public land mobile network identifier, PLMN ID). In order to perform the addressing and discovery of network element functions, each network element needs to be registered with the NRF. Some network element functions may be registered with the NRF when the network element function is first executed. The network storage function device may be a core network device.

[0145] The functions of the interfaces are described as follows.

[0146] 1. N1 represents the interface between the AMF and the UE, is access agnostic, and is configured to transfer QoS control rules to the UE, etc.

[0147] 2. N2 represents the interface between the AMF and the RAN, and is configured to transfer radio bearer control information from the core network side to the RAN, etc.

[0148] 3. N4 represents the interface between the SMF network element and the UPF, and is configured to transfer information between the control plane and the user plane, including the delivery of transfer rules from the control plane to the user plane, QoS control rules, traffic statistics rules, etc., and the reporting of user plane information.

[0149] 4. N5 represents the interface between the AF and the PCF, and is configured to deliver application service requests and report network events.

[0150] 5. N7 represents the interface between the PCF and the SMF, and is configured to deliver PDU session granularity control policies and service data flow granularity control policies.

[0151] 6. N8 represents the interface between the AMF and the UDM, and is used for the AMF to obtain subscription data and authentication data related to access and mobility management from the UDM, and for the AMF to register information related to the current mobility management of the UE with the UDM, etc.

[0152] 7. N10 represents the interface between the SMF and the UDM, and is used for the SMF to obtain session management-related subscription data from the UDM, and for the SMF to register information related to the current session of the UE with the UDM, etc.

[0153] 8. N11 represents the interface between the SMF and the AMF, and is configured to transfer PDU session tunnel information between the RAN and the UPF, transfer control messages sent to the UE, transfer radio resource control information to be sent to the RAN, etc.

[0154] 9. N15 represents the interface between the PCF and the AMF, and is configured to deliver UE policies and access control-related policies.

[0155] 10. N35 represents the interface between the UDM and the UDR and is used for the UDM to obtain user subscription data information from the UDR.

[0156] 11. N36 represents the interface between the PCF and the UDR and is used for the PCF to obtain policy-related subscription data and application data-related information from the UDR.

[0157] 12. N52 represents the interface between the UDM and the NEF and is used for the NEF to expose network capabilities to third-party application functions. For example, a third-party application function subscribes to reachability events of all users within a specific group from the UDM via the NEF.

[0158] The following describes some terms in this application.

[0159] 1. Non-Public Network (NPN)

[0160] The NPN is a network different from the public network and provides services for specific users. The NPN can be classified into two types, namely, Standalone NPN (SNPN) and Public Network Integrated NPN (PNI-NPN).

[0161] The core network of the SNPN is independent of the Public Land Mobile Network (PLMN). The PNI-NPN can be understood as a PLMN, but the PLMN provides NPN services by supplying special slices and / or network data.

[0162] 2. Onboarding

[0163] As shown in FIG. 2, when the UE does not obtain subscription data (e.g., authentication credential "credential") for accessing the non-public network, the UE needs to access the onboarding network by using default credential or PLMN credential. After the UE successfully accesses (or registers with) the onboarding network, the service provisioning server (PVS) provides the UE with subscription data (e.g., credential) for accessing the NPN through the onboarding network.

[0164] The following describes scenarios to which the solution provided in this application is applied.

[0165] To access the NPN, the UE may first access the onboarding network to obtain subscription data for accessing the NPN. After the UE accesses the onboarding network, the AMF performs onboarding for the UE. The AMF supports the onboarding function. The AMF is hereinafter referred to as S-SMF. If the S-AMF cannot continue to perform onboarding for the UE, or if the AMF providing services to the UE needs to be replaced due to factors such as load balancing and radio resource status in the onboarding network, a handover needs to be performed. The solution provided in this application is used to select a new AMF (wherein the new AMF is hereinafter referred to as T-AMF) when a handover is performed and continue to perform onboarding for the UE.

[0166] The reason why the S-AMF cannot continue to perform onboarding for the UE may be any one of the following.

[0167] 1. The UE exits the service area of the S-AMF.

[0168] 2. The S-AMF is damaged or malfunctioning and cannot operate properly.

[0169] 3. The load on the S-AMF is excessively heavy, and the S-AMF is no longer suitable for performing onboarding for the UE for load balancing.

[0170] 4. The radio resources of the access network device (hereinafter referred to as S-RAN) provided by the S-AMF are insufficient. Considering the radio resource state, the access network device is no longer suitable for providing services to the UE. Therefore, the access network device needs to be replaced. Hereinafter, the replaced access network device is called T-RAN. The AMF (hereinafter called T-AMF) that provides services to T-RAN is different from the S-AMF. Therefore, the AMF needs to be replaced.

[0171] The following describes the solution of the present application in detail by using an example where the UE exits the service area of the S-AMF. In a possible implementation, it should be understood that the access network device that provides services to the UE also changes, and the access network device changes from the second access network device to the first access network device.

[0172] Figures 3A and 3B show the solution according to the present application. In this case, the UE is in the radio resource control (RRC) connected state.

[0173] S301: When the S-RAN (an example of a second access network device) determines that the T-RAN (an example of a first access network device) is more suitable for providing services to the UE, the S-RAN sends a second request message to the S-AMF (an example of a second core network device), and the second request message is used to request to hand over the RAN that provides services to the UE from the S-RAN to the T-RAN. Correspondingly, the S-AMF receives the second request message.

[0174] In a possible implementation, the second request message includes an identifier of the T-RAN and a source to target transparent container.

[0175] The identifier of the T-RAN is used to identify the T-RAN. The source to target transparent container is generated by the S-RAN, and the container includes information that needs to be used by the T-RAN.

[0176] S302: If the S-AMF cannot provide services to the UE, the S-AMF obtains third information, selects the T-AMF (an example of a first core network) based on the third information, and the T-AMF supports onboarding.

[0177] The third information indicates to the UE to perform onboarding. It should be understood that the third information indicates to the UE to perform onboarding means that the purpose for the UE to access the network is onboarding.

[0178] That is, the S-AMF determines based on the third information that an AMF that supports the onboarding function needs to be selected for the UE, and then selects the T-AMF.

[0179] The following describes some methods for the S-AMF to obtain the third information.

[0180] Method 1:

[0181] The S-AMF obtains the third information from the UE.

[0182] In a possible implementation, the UE may send an AN message to the S-RAN, and the AN message may include a NAS registration request message. The third information may be carried in the NAS registration request message. For example, the third information may be registration type information, and the registration type information may indicate to the UE to perform onboarding. In a possible implementation, the registration type may be one or more of the following registration types: Onboarding registration type, Standalone non-public network onboarding (SNPN Onboarding) registration type, Mobility registration update with onboarding registration type, Mobility registration update with SNPN onboarding registration type, and Mobility registration update registration type.

[0183] The S-RAN may send the NAS registration request message to the S-AMF.

[0184] The S-AMF obtains the third information from the NAS registration request message.

[0185] Method 2:

[0186] In a possible implementation, the S-AMF obtains the third information locally. The third information is the following: UE's registration type information, data network name (DNN) information, network slice selection assistance information (NSSAI), and information regarding the first value includes one or more of the following.

[0187] The UE's registration type information indicates to the UE to perform onboarding. In a possible implementation, the UE's registration type may be one or more of the following registration types: Onboarding registration type, Standalone non-public network onboarding registration type (SNPN Onboarding), Mobility Registration Update with Onboarding registration type, Mobility Registration Update with SNPN Onboarding registration type, and Mobility Registration Update registration type.

[0188] In a possible implementation, the first value indicates the period during which the UE is registered with the onboarding network or the remaining period during which the UE is permitted to register with the onboarding network. For example, the first value may be the current value of a timer. The type of the timer may be a positive timer or a countdown timer. This is not limited in this application.

[0189] That is, the UE's registration type information may also explicitly or implicitly instruct the UE to perform onboarding, and the data network name, slice information, and the first value may all implicitly indicate to the UE to perform onboarding.

[0190] In a possible implementation, after registering with the onboarding network, it should be understood that the UE may establish a specific session by using a specific DNN and / or a specific NSSAI. The session is limited to performing only onboarding. In a possible implementation, the session may be a packet data unit (PDU) session.

[0191] In a possible implementation, it should be understood that the data network name, network slice information, and the first value may be UE context information.

[0192] S303: The S-AMF sends the first information to the T-AMF, and correspondingly, the T-AMF receives the first information, and the first information indicates to the UE to perform onboarding.

[0193] In a possible implementation, the first information may be carried in a third request message, and the third request message is used to set up the UE context.

[0194] In a possible implementation, the third request message may include the identification information of the T-RAN, information about the source to target transparent container, and UE context information, and the UE context information includes an identifier of the UE, for example, the subscription permanent identifier (SUPI) of the UE.

[0195] In a possible implementation, the first information may be explicit instruction information, that is, the S-AMF directly instructs the UE to perform onboarding.

[0196] In other possible implementations, the first information may be implicit instruction information. In this case, the first information is as follows: Information about the data network name, network slice information, and the first value includes one or more of the above.

[0197] In other possible implementations, the first information may include both explicit instruction information and implicit instruction information.

[0198] S304: The T-AMF performs onboarding for the UE based on the first information.

[0199] Based on the first piece of information, the T-AMF determines that the UE is a UE for which onboarding is to be performed, and performs onboarding for the UE.

[0200] In other words, the T-AMF may replace the S-AMF to continue performing onboarding for the UE.

[0201] Furthermore, in the process of the T-AMF performing onboarding for the UE, in order to avoid the problem that network resources are occupied because the UE is always camped on or registered with the onboarding network, the T-AMF may further perform operations in the following manner.

[0202] Method 1:

[0203] When the first piece of information includes information regarding a first value, the T-AMF may start a first timer and set the start value of the first timer to the first value.

[0204] When the first value indicates the period during which the UE is registered with the network, the first timer may be a positive timer. When the value of the first timer increases to a first threshold, the T-AMF executes a deregistration procedure for the UE. In a possible implementation, the first threshold indicates the longest time during which the UE can be registered (or camped on) with the onboarding network. In other possible implementations, the first threshold may be longer than, equal to, or shorter than the period during which the UE changes from the RRC connected mode to the RRC idle mode or the RRC inactive mode.

[0205] When the first value indicates the remaining period during which the UE is permitted to register with the network, the first timer may be a countdown timer. When the value of the first timer decreases to a second threshold, the T-AMF executes a deregistration procedure for the UE.

[0206] In a possible implementation, the second threshold may be zero.

[0207] Method 2:

[0208] T-AMF may start a second timer.

[0209] If the second timer is a positive timer, T-AMF may set the start value of the second timer to zero or a second threshold. When the value of the second timer increases to the first threshold, T-AMF executes the UE deregistration procedure.

[0210] If the second timer is a countdown timer, T-AMF may set the start value of the second timer to the first threshold. When the value of the second timer decreases to the second threshold or zero, T-AMF executes the UE deregistration procedure.

[0211] It should be understood that the information regarding the first threshold and the information regarding the second threshold may be pre-configured in T-AMF. Alternatively, T-AMF may obtain second information from S-AMF, and the second information indicates the first threshold and / or the second threshold.

[0212] It should be understood that the purpose of executing the deregistration procedure by T-AMF is to deregister the UE from the onboarding network, and since the UE is not camped on or registered with the onboarding network, it does not always occupy network resources.

[0213] S305: T-AMF determines T-RAN based on the identification information of T-RAN, sends a handover request message to T-RAN, and correspondingly, T-RAN receives the handover request message.

[0214] In a possible implementation, the handover request message includes information regarding a transparent container from source to target.

[0215] S306: The T-RAN sends a second response message to the T-AMF. The second response message is used to respond to the handover request message, and the T-AMF receives the second response message.

[0216] In a possible implementation, the second response message includes information about the transparent container from the target to the source. The information about the transparent container from the target to the source includes UE container information. The UE container information includes access stratum information and non-access stratum information.

[0217] S307: The T-AMF sends a third response message to the S-AMF. The third response message is used to respond to the third request message, and correspondingly, the S-AMF receives the third response message.

[0218] In a possible implementation, the third response message includes information about the transparent container from the target to the source.

[0219] S308: The S-AMF sends a first handover command to the S-RAN, and correspondingly, the S-RAN receives the first handover command.

[0220] In a possible implementation, the first handover command includes information about the transparent container from the target to the source.

[0221] S309: The S-RAN sends a second handover command to the UE, and correspondingly, the UE receives the second handover command.

[0222] In a possible implementation, the second handover command includes UE container information. It should be understood that in a possible implementation, the UE container information includes the identification information of the T-RAN.

[0223] S310: The UE executes a handover according to the second handover command. When the UE successfully handovers to the T-RAN, the UE sends the first indication information to the T-RAN, and correspondingly, the T-RAN receives the first indication information.

[0224] In a possible implementation, the first indication information indicates that the UE has successfully executed the handover.

[0225] S311: The T-RAN sends the second indication information to the T-AMF, and correspondingly, the T-AMF receives the second indication information.

[0226] In a possible implementation, the second indication information indicates that the T-RAN has successfully executed the handover.

[0227] S312: The T-AMF sends an N2 information notification message to the S-AMF, and correspondingly, the S-AMF receives the N2 information notification message.

[0228] Optionally, the method further includes S313: The S-AMF sends an N2 information notification response message to the T-AMF, and correspondingly, the T-AMF receives the N2 information notification response message.

[0229] S314: The S-AMF starts a third timer based on the N2 information notification message. After the third timer expires, the S-AMF sends a UE context release command to the S-RAN, and correspondingly, the S-RAN receives the UE context release command.

[0230] For example, when the value of the third timer increases to a third threshold or decreases to a fourth threshold, the S-AMF sends a UE context release command to the S-RAN.

[0231] S315: When the S-RAN releases the UE context according to the UE context release command, the S-RAN sends a UE context release completion message to the S-AMF.

[0232] S316: The UE starts the mobility registration procedure.

[0233] The procedure includes the following steps.

[0234] The UE sends an AN message to the T-RAN. The AN message includes AN parameters and an NAS registration request message. Correspondingly, the T-RAN receives the AN message. The NAS registration request message includes registration type information, which indicates that the registration type of the UE is a mobility registration update.

[0235] The T-RAN sends the NAS registration request message to the T-AMF. Correspondingly, the T-AMF receives the NAS registration request message.

[0236] Then, the T-AMF executes the UE authentication procedure. After successful authentication, the T-AMF sends a registration success message to the UE.

[0237] The UE sends a registration completion message to the T-AMF.

[0238] In a possible implementation, the T-AMF may start the first timer or the second timer at step S304 or at any point after step S304.

[0239] According to the solution of the present application, when the terminal device is in the RRC connected mode and the S-AMF cannot perform onboarding for the terminal device, the S-AMF may select a T-AMF that supports the onboarding function. When the S-AMF performs onboarding for the terminal device, the AMF selected by the S-AMF may not support the onboarding function. Therefore, according to the solution of the present application, the T-AMF can continue to perform onboarding for the terminal device. Further, when performing onboarding for the terminal device, the T-AMF may start a specific timer to prevent the terminal device from always camping on the onboarding network. Thereby, the utilization of network resources is improved.

[0240] Figure 4 shows another solution according to the present application. In this case, the UE is in the RRC idle mode.

[0241] S401: The UE sends the fourth information to the T-RAN, and the fourth information indicates to the UE to perform onboarding. Correspondingly, the T-RAN receives the fourth information.

[0242] In a possible implementation, the fourth information may be carried in an access network (AN) message.

[0243] In a possible implementation, the fourth information may implicitly indicate to the UE to perform onboarding. For example, a field may be added to the 5G system temporary mobile subscription identifier (5G-S-TMSI), or some fields in the 5G-S-TMSI may be set to specific values to implicitly indicate to the UE to perform onboarding.

[0244] In other possible implementations, the fourth information may explicitly indicate to the UE to perform onboarding.

[0245] The AN message may further include an NAS registration request message, the NAS registration request message includes registration type information, and the registration type information indicates that the registration type of the UE is a mobility registration update. In a possible implementation, the NAS registration request message further includes a temporary identifier assigned to the UE by the S-AMF, for example, a 5G globally unique temporary identity (5G-GUTI).

[0246] S402: The T-RAN selects a T-AMF based on the fourth piece of information, and the T-AMF supports the onboarding function.

[0247] It should be understood that the T-RAN determines, based on the fourth piece of information, that the UE is a UE that performs onboarding, and selects a T-AMF that supports the onboarding function for the UE.

[0248] S403: The T-RAN sends an NAS registration request message to the T-AMF, and correspondingly, the T-AMF receives the NAS registration request message.

[0249] In a possible implementation, the T-RAN may further send the first piece of information to the T-AMF. For example, the first piece of information may be carried in an N2 message. The first piece of information indicates to the UE that onboarding is to be performed.

[0250] S404: The T-AMF sends a fourth request message to the S-AMF, the fourth request message is used to request UE context information, and correspondingly, the S-AMF receives the fourth request message.

[0251] S405: The S-AMF sends a fourth response message to the T-AMF, the fourth response message is used to respond to the fourth request message, the fourth response message includes UE context information, and correspondingly, the T-AMF receives the fourth response message.

[0252] Optionally, the S-AMF sends the first piece of information to the T-AMF, and the first piece of information indicates to the UE to perform onboarding. For example, the first piece of information is carried in the fourth response message for transmission.

[0253] In a possible implementation, the first piece of information may be explicit instruction information, that is, the S-AMF directly instructs the UE to perform onboarding.

[0254] In other possible implementations, the first piece of information may be implicit instruction information. In this case, the first piece of information is as follows: Data network name information, network slice information, and information regarding a first value including one or more of them.

[0255] In other possible implementations, the first piece of information may include both explicit instruction information and implicit instruction information.

[0256] S406: The T-AMF performs onboarding on the UE based on the first piece of information.

[0257] This process is the same as the process in S304. For details, refer to the description of S304. In a possible implementation, the T-AMF may start the first timer or the second timer at step S406 or at any point in time after step S406.

[0258] S407: Next, an authentication procedure is performed on the UE, and after authentication is successful, the T-AMF sends a registration success message to the UE.

[0259] In a possible implementation, the registration success message further includes a temporary identifier assigned to the UE by the T-AMF. For example, the temporary identifier may be a 5G-GUTI. The temporary identifier indicates that the UE is a UE performing onboarding.

[0260] Furthermore, the T-AMF sends a registration status update message to the S-AMF. The registration status update message indicates that the UE has successfully registered with the T-AMF.

[0261] S408: The UE sends a registration completion message to the T-AMF.

[0262] According to the solution of the present application, when the terminal device is in the RRC idle mode and the S-AMF cannot perform onboarding on the terminal device, the T-RAN may select a T-AMF that supports the onboarding function. When the S-AMF cannot perform onboarding on the terminal device, the AMF selected by the T-RAN may not support the onboarding function. Therefore, according to the solution of the present application, the T-AMF may not be able to continue to perform onboarding on the terminal device. Furthermore, when performing onboarding on the terminal device, the T-AMF may start a specific timer to prevent the terminal device from always camping on the onboarding network. Thereby, the utilization of network resources is improved.

[0263] FIG. 5 shows another solution according to the present application. In this case, the UE is in the RRC idle mode.

[0264] S501: The UE sends an AN message to the T-RAN. The AN message includes AN parameters and an NAS registration request message.

[0265] For example, the AN parameters may include a 5G-S-TMSI and / or a globally unique AMF identifier (GUAMI).

[0266] The NAS registration request message includes registration type information, and the registration type information indicates that the registration type of the UE is a mobility registration update. Optionally, the NAS registration request message may further include a temporary identifier of the UE. The temporary identifier of the UE is assigned to the UE by the S-AMF.

[0267] In a possible implementation, the method further includes: S502: The UE sends the fifth piece of information to the T-RAN, the fifth piece of information is carried in the NAS registration request message, the fifth piece of information indicates that the terminal device performs onboarding, and correspondingly, the T-RAN receives the fifth piece of information.

[0268] The following describes a method of carrying the fifth piece of information in the NAS registration request message.

[0269] Method 1:

[0270] A field is added to the UE's temporary identifier (e.g., 5G-GUTI) to indicate to the terminal device that it performs onboarding.

[0271] Method 2:

[0272] Some fields within the UE's temporary identifier (e.g., 5G-GUTI) are set to specific values to indicate to the terminal device that it performs onboarding.

[0273] Method 3:

[0274] The NAS registration request message includes instruction information indicating to the terminal device that it performs onboarding.

[0275] Method 4:

[0276] The registration type is newly added to the registration type information to indicate to the terminal device to perform onboarding. In this case, the registration type information may indicate that the registration type of the UE is onboarding and mobility registration update. In a possible implementation, the registration type may be one or more of the following registration types: Onboarding registration type, Standalone non-public network onboarding registration type (SNPN Onboarding), Mobility registration update with onboarding registration type, Mobility registration update with SNPN onboarding registration type, and Mobility registration update registration type.

[0277] It should be understood that the way the first information is carried in the NAS registration request message is not limited in this application.

[0278] S503: T-RAN selects the initial AMF (an example of the third core network device) and sends the NAS registration request message to the initial AMF.

[0279] If the method includes S502, since T-RAN does not parse the NAS registration request message, T-RAN does not know that the terminal device is performing onboarding. Therefore, when selecting the initial AMF, T-RAN may select an AMF that does not support the onboarding function.

[0280] S504: The initial AMF obtains the fifth information, and the fifth information indicates to the UE to perform onboarding.

[0281] The following describes how the initial AMF obtains the fifth information.

[0282] Method 1:

[0283] If the method includes S502, the initial AMF obtains the fifth piece of information from the NAS registration request message.

[0284] Method 2:

[0285] The initial AMF obtains the fifth piece of information from the S-AMF.

[0286] For example, the initial AMF sends a fourth request message to the S-AMF. The fourth request message is used to request UE context information. Correspondingly, the S-AMF receives the fourth request message.

[0287] In a possible implementation, the S-AMF carries the fifth piece of information in the fourth response message, and sends the fourth response message to the initial AMF. The fourth response message is used to respond to the fourth request message. The fourth response message includes UE context information. Correspondingly, the initial AMF receives the fourth response message.

[0288] In a possible implementation, the fifth piece of information may be explicit indication information, that is, the S-AMF directly instructs the initial AMF that the UE performs onboarding.

[0289] In other possible implementations, the fifth piece of information may be implicit indication information. In this case, the fifth piece of information is as follows: Data network name information, network slice information, and information regarding the first value includes one or more of the following.

[0290] In other possible implementations, the fifth piece of information may include both explicit indication information and implicit indication information.

[0291] In a possible implementation, after registering with the onboarding network, the UE may establish a specific session by using a specific DNN and / or a specific NSSAI. The session is restricted to performing only onboarding. In a possible implementation, the session may be a packet data unit (PDU) session.

[0292] If the initial AMF does not support the onboarding function, the method further includes S505: The initial AMF determines a T-AMF that supports the onboarding capability.

[0293] In addition, the initial AMF may further send rejection indication information to the S-AMF so as to indicate that the S-AMF registration procedure is not completed at the initial AMF.

[0294] It should be understood that after obtaining the fifth piece of information, the initial AMF may execute a determination. If the initial AMF supports the onboarding function, the initial AMF may perform onboarding for the UE. If the initial AMF does not support the onboarding function, the initial AMF may continue to determine the T-AMF.

[0295] The following describes how the initial AMF determines the T-AMF.

[0296] Method 1:

[0297] The initial AMF determines the T-AMF based on the pre-configured capability information of at least one AMF network element.

[0298] Method 2:

[0299] The initial AMF sends a first request message to a network repository function (NRF) network element (e.g., an example of a fourth core network device), and the first request message is used to request to obtain an AMF that supports the onboarding function.

[0300] In a possible implementation, the first request message includes information about a set of AMFs.

[0301] The NRF network element sends a first response message to the initial AMF, and the first response message includes information about the T-AMF. For example, the first response message includes identification information and / or address information of the T-AMF.

[0302] In a possible implementation, the NRF network element may determine the T-AMF from the set of AMFs included in the first request message.

[0303] The initial AMF determines the T-AMF based on the first response message.

[0304] S506: The T-AMF obtains first information, and the first information indicates to the UE to perform onboarding.

[0305] The following describes how the T-AMF obtains the first information.

[0306] Method 1:

[0307] The initial AMF sends the first information to the T-AMF, and correspondingly, the T-AMF receives the first information.

[0308] For example, the initial AMF may send an N1 message notification message to the T-AMF. The N1 message notification message includes one or more of a NAS message, UE identification information, and UE context information. When the method includes S502, the first information is the fifth information carried in the NAS message. Alternatively, the UE context information may include one or more of data network name information, network slice information, and information regarding a first value, and the data network name information, network slice information, and the first value may all implicitly indicate to the UE to perform onboarding.

[0309] In a possible implementation, it should be understood that after registering with the onboarding network, the UE may establish a specific session by using a specific DNN and / or a specific NSSAI. The session is limited to performing only onboarding. In a possible implementation, the session may be a packet data unit (PDU) session.

[0310] Method 2:

[0311] The S-AMF sends the first information to the T-AMF, and correspondingly, the T-AMF receives the first information.

[0312] For example, the T-AMF may send a fourth request message to the S-AMF, and the fourth request message is used to request UE context information. The S-AMF may carry the first information in the fourth response message and may send the fourth response message to the T-AMF. The fourth response message includes UE context information.

[0313] In a possible implementation, the first information may be explicit instruction information, that is, the S-AMF directly instructs the UE to perform onboarding.

[0314] In other possible implementations, the first information may be implicit instruction information. In this case, the first information is as follows: Data network name information, network slice information, and information regarding a first value includes one or more of the following.

[0315] In a possible implementation, after registering with the onboarding network, it should be understood that the UE may establish a specific session by using a specific DNN and / or a specific NSSAI. The session is limited to performing only onboarding. In a possible implementation, the session may be a packet data unit (PDU) session.

[0316] In other possible implementations, the first information may include both explicit indication information and implicit indication information.

[0317] S507: The T-AMF performs onboarding for the UE based on the first information.

[0318] This process is the same as the process in S304. For details, refer to the description of S304.

[0319] S508: Next, an authentication procedure is performed for the UE, and after authentication is successful, the T-AMF sends a registration success message to the UE.

[0320] In a possible implementation, the registration success message further includes a temporary identifier assigned to the UE by the T-AMF. For example, the temporary identifier may be a 5G-GUTI. The temporary identifier indicates the UE that performs onboarding.

[0321] Furthermore, the T-AMF sends a registration status update message to the S-AMF. The registration status update message indicates that the UE has successfully registered with the T-AMF.

[0322] S509: The UE sends a registration completion message to the T-AMF.

[0323] According to the solution of the present application, when the terminal device is in the RRC idle mode and the S-AMF cannot perform onboarding for the terminal device, the T-RAN may select an initial T-AMF according to the existing mechanism. If the initial AMF does not support the onboarding function, the initial AMF further determines the T-AMF. When the S-AMF cannot perform onboarding for the terminal device, the AMF selected by the T-RAN may not support the onboarding function. Therefore, according to the solution of the present application, the T-AMF may not be able to continue to perform onboarding for the terminal device. Further, when performing onboarding for the terminal device, the T-AMF may start a specific timer to prevent the terminal device from always camping on the onboarding network. Thereby, the network resource utilization is improved.

[0324] According to the above method, FIG. 6 shows a communication device according to an embodiment of the present application. The communication device includes a transceiver unit 601 and a processing unit 602. The transceiver unit 601 may be configured to implement the receiving function and the transmitting function in the embodiment of the method. Other functions in the embodiment of the method may be implemented by using the processing unit 602. The transceiver unit may be implemented by using an input interface and an output interface in the data processing chip. The transmission and reception in the embodiment of the method respectively correspond to the output and input in the chip. The transceiver unit 601 may be further divided into a receiving unit and a transmitting unit. The receiving unit may be configured to implement the receiving function in the embodiment of the method, and the transmitting unit may be configured to implement the transmitting function in the embodiment of the method. The receiving unit may be implemented by using an output interface in the data processing chip, and the transmitting unit may be implemented by using an input interface of the data processing chip. In addition, the transceiver unit and the processing unit may be implemented by using the same chip. This is not limited in the present application. The transceiver unit 601 in this embodiment of the present application may alternatively be implemented by a transceiver (including a transmitter and a receiver) or transceiver-related circuit components, and the processing unit 602 may alternatively be implemented by a processor or processor-related circuit components (or called a processing circuit).

[0325] For example, when the communication device is an S-AMF, the transceiver unit 601 and the processing unit 602 can support the actions completed by the S-AMF in the above example of the method. For example, the transceiver unit 601 can receive the second request message in the embodiment of the above method and complete other processes in the technical solution described herein. The processing unit 602 can select the T-AMF based on the third information and complete other processes in the technical solution described herein.

[0326] For example, when the communication device is a T-AMF, the transceiver unit 601 and the processing unit 602 can support the actions completed by the T-AMF in the above example of the method. For example, the transceiver unit 601 can receive the first information in the above embodiment of the method and complete other processes in the technical solution described herein. The processing unit 602 can perform onboarding for the UE based on the first information and complete other processes in the technical solution described herein.

[0327] For example, when the communication device is an initial AMF, the transceiver unit 601 and the processing unit 602 can support the actions completed by the initial AMF in the above example of the method. For example, the transceiver unit 601 can receive the NAS registration request message in the above embodiment of the method and complete other processes in the technical solution described herein. The processing unit 602 can determine the T-AMF and complete other processes in the technical solution described herein.

[0328] For example, when the communication device is an S-RAN, the transceiver unit 601 and the processing unit 602 can support the actions completed by the S-RAN in the above example of the method. For example, the transceiver unit 601 can transmit the second request message in the above embodiment of the method and complete other processes in the technical solution described herein. The processing unit 602 can release the UE context and complete other processes in the technical solution described herein.

[0329] For example, when the communication device is a T-RAN, the transceiver unit 601 and the processing unit 602 can support the actions completed by the T-RAN in the above example of the method. For example, the transceiver unit 601 can receive the fourth information in the above embodiment of the method and complete other processes in the technical solution described herein. The processing unit 602 can select the T-AMF based on the fourth information and complete other processes in the technical solution described herein.

[0330] Embodiments of the present application further provide a communication device including a processor 701, a communication interface 702, and a memory 703 as shown in FIG. 7. The processor 701, the communication interface 702, and the memory 703 may be connected to each other via a bus 707. The bus 707 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus 707 may be classified into an address bus, a data bus, and a control bus. For ease of representation, only one thick line is used to represent the bus in FIG. 7, but this does not mean that there is only one bus or only one type of bus. The processor 701 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The memory 703 may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory.The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM) used as an external cache.

[0331] The processor 701 is configured to implement the data processing operations of the communication device. The communication interface 702 is configured to implement the receiving and transmitting operations of the communication device.

[0332] For example, when the communication device is an S-AMF, the processor 701, the communication interface 702, and the memory 703 can support the actions completed by the S-AMF in the above example of the method. For example, the communication interface 702 can receive the second request message in the above embodiment of the method and complete other processes in the technical solution described herein. The processor 701 can select the T-AMF based on the third information and complete other processes in the technical solution described herein.

[0333] For example, when the communication device is a T-AMF, the processor 701, the communication interface 702, and the memory 703 can support the actions completed by the T-AMF in the above example of the method. For example, the communication interface 702 can First information receive it and complete other processes in the technical solution described herein. The processor 701 can Execute onboarding for the UE based on the first information do this and complete other processes in the technical solution described herein.

[0334] For example, when the communication device is the initial AMF, the processor 701, the communication interface 702, and the memory 703 can support the actions completed by the initial AMF in the above example of the method. For example, the communication interface 702 can receive the NAS registration request message in the above embodiment of the method and complete other processes in the technical solution described herein. The processor 701 can determine the T-AMF and complete other processes in the technical solution described herein.

[0335] For example, when the communication device is the S-RAN, the processor 701, the communication interface 702, and the memory 703 can support the actions completed by the S-RAN in the above example of the method. For example, the communication interface 702 can transmit the second request message in the above embodiment of the method and complete other processes in the technical solution described herein. The processor 701 can release the UE context and complete other processes in the technical solution described herein.

[0336] For example, when the communication device is the T-RAN, the processor 701, the communication interface 702, and the memory 703 can support the actions completed by the T-RAN in the above example of the method. For example, the communication interface 702 can receive the fourth information in the above embodiment of the method and complete other processes in the technical solution described herein. The processor 701 can select the T-AMF based on the fourth information and complete other processes in the technical solution described herein.

[0337] Those skilled in the art can recognize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps may be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether a function is executed by hardware or software depends on the specific application of the technical solution and design constraints. Those skilled in the art may use various methods to implement the described functions for each specific application, but the implementation should not be considered to exceed the scope of this application.

[0338] For the sake of convenience and concise description, those skilled in the art should clearly understand that, regarding the detailed operation processes of the above systems, devices, and units, reference should be made to the corresponding processes in the embodiments of the above methods. Details will not be described again here.

[0339] It should be understood that in some embodiments provided in this application, the disclosed systems, devices, and methods may be implemented in other ways. For example, the described embodiments of the device are merely examples. For example, the division into units is only a logical function division, and in actual implementation, other divisions may be used. For example, multiple units and components may be combined or integrated into other systems, or some features may be ignored or not executed. Furthermore, the disclosed mutual coupling, direct coupling, or communication connection may be implemented through some interfaces. The indirect coupling or communication connection between devices or units may be implemented in electronic, mechanical, or other forms.

[0340] The units described as separate units may or may not be physically separated. The parts shown as units may or may not be physical units. They may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected based on actual requirements to achieve the purpose of the implementation solution.

[0341] Furthermore, the functional units in the embodiments of the present application may be integrated into one processing unit, each unit may exist physically independently, or two or more units may be integrated into one unit.

[0342] When the function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of the technical solution, may also be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions that enable a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the steps of the method described in the embodiments of the present application. The above storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0343] The above description is merely a specific implementation of the present application and is not intended to limit the protection scope of the present application. Any modification or substitution that can be easily conceived by those skilled in the art within the technical scope disclosed in the present application should fall within the protection scope of the present application. Therefore, the protection scope of the present application should follow the protection scope of the claims.

[0344] This application claims priority to Chinese Patent Application No. 202110768279.8, filed with the China National Intellectual Property Administration on July 7, 2021, with the invention title "METHOD FOR PERFORMING ONBOARDING AND APPARATUS", and the previous Chinese patent application is incorporated herein by reference in its entirety.

Claims

1. A method for performing onboarding, comprising: obtaining first information by a first core network device, wherein the first information indicates that a terminal device is to perform onboarding, and the first core network device is a core network device selected to replace a second core network device that provides services to the terminal device when there is a handover request, and the first core network device supports an onboarding function; and performing onboarding on the terminal device based on the first information by the first core network device. A method having the above steps.

2. The obtaining of the first information by the first core network device includes: obtaining the first information from the second core network device by the first core network device; or obtaining the first information from a first access network device by the first core network device, wherein the first access network device is an access network device requested to provide services to the terminal device after the handover is performed; or obtaining the first information from the terminal device by the first core network device; or obtaining the first information from a third core network device by the first core network device, wherein the third core network device is the core network device first selected when there is a handover request, and the third core network device does not support an onboarding function. The method according to claim 1, having the above steps.

3. The method according to claim 1, wherein the first information includes one or more of the following: data network name information, network slice information, and information regarding a first value, wherein the first value indicates a period during which the terminal device is registered with the network or the remaining period during which the terminal device is permitted to register with the network. The method according to claim 1, having the above steps.

4. When the first information includes the information regarding the first value, the method further includes: ​ Starting a first timer by the first core network device, wherein a start value of the first timer is the first value When a value of the first timer increases to a first threshold, executing, by the first core network device, a deregistration procedure of the terminal device, wherein the value of the first timer indicates a period during which the terminal device is registered to the network, or When a value of the first timer decreases to a second threshold, executing, by the first core network device, a deregistration procedure of the terminal device, wherein the value of the first timer indicates a remaining period during which the terminal device is permitted to register to the network further comprising The method according to claim 3

5. The method comprises starting a second timer by the first core network device, and when the value of the second timer increases to the first threshold or decreases to the second threshold, executing, by the first core network device, a deregistration procedure of the terminal device further comprising The method according to claim 1

6. Information about the first threshold and / or information about the second threshold are preset, or the method further comprises obtaining, by the first core network device, second information from the second core network device, wherein the second information indicates the first threshold and / or the second threshold The method according to claim 4

7. The first core network device is an access and mobility management function device The method according to claim 1

8. The second core network device is an access and mobility management function device The method according to claim 1

9. A method for performing onboarding, comprising when there is a handover request, selecting, by a second core network device based on third information, a first core network device that replaces the second core network device to provide services to a terminal device, wherein the third information indicates that the terminal device performs onboarding, and the first core network device supports an onboarding function, the selecting Transmitting the first information to the first core network device by the second core network device, where the first information indicates that the terminal device performs onboarding, and the first core network device executes onboarding for the terminal device based on the first information, the transmitting A method having. **Claim 10** The third information is as follows: Including one or more of registration type information, data network name information, network slice information, and information regarding a first value, The first value indicates the period during which the terminal device is registered with the network, or the first value indicates the remaining period during which the terminal device is permitted to register with the network, The method according to claim 9. **Claim 11** The method further has Obtaining the third information from the second access network device or the terminal device by the second core network device, The second access network device is an access network device that provides services to the terminal device before the execution of the handover, The method according to claim 9. **Claim 12** The first information is as follows: Including one or more of data network name information, network slice information, and information regarding a first value, The first value indicates the period during which the terminal device is registered with the network, or the first value indicates the remaining period during which the terminal device is permitted to register with the network, The method according to claim 9. **Claim 13** The first core network device and / or the second core network device is an access and mobility management function device, The method according to claim 9. **Claim 14** A first core network device, A transceiver unit configured to obtain first information, the first information indicating that a terminal device performs onboarding, the first core network device being a core network device selected to replace a second core network device that provides services to the terminal device when there is a handover request, the first core network device supporting an onboarding function, the transceiver unit A processing unit configured to perform onboarding on the terminal device based on the first information A device having the same.

15. The fact that the transceiver unit is configured to obtain the first information means that The transceiver unit is configured to obtain the first information from the second core network device, or The transceiver unit is configured to obtain the first information from a first access network device, and the first access network device is an access network device requested to provide services to the terminal device after the execution of the handover, or The transceiver unit is configured to obtain the first information from the terminal device, or The transceiver unit is configured to obtain the first information from a third core network device, and the third core network device is the core network device first selected when there is a request for handover, and the third core network device does not support the onboarding function Having the same The device according to claim 14.

16. The first information includes one or more of the following: Data network name information, network slice information, and information regarding a first value, The first value indicates the period during which the terminal device is registered with the network, or the first value indicates the remaining period during which the terminal device is permitted to register with the network The device according to claim 14. ;

17. When the first information includes the information regarding the first value, the processing unit Starts a first timer such that the start value of the first timer is the first value, and When the value of the first timer increases to a first threshold, executes a deregistration procedure of the terminal device, and the value of the first timer indicates the period during which the terminal device is registered with the network, or When the value of the first timer decreases to a second threshold, executes a deregistration procedure of the terminal device, and the value of the first timer indicates the remaining period during which the terminal device is permitted to register with the network Is further configured The device according to claim 16.

18. The processing unit Start the second timer, When the value of the second timer increases to the first threshold or decreases to the second threshold, execute the deregistration procedure of the terminal device and is further configured as the device according to claim 14.

19. The information regarding the first threshold and / or the information regarding the second threshold is preset, or the transceiver unit is further configured to obtain second information from the second core network device, and the second information indicates the first threshold and / or the second threshold, the device according to claim 17.

20. The first core network device is an access and mobility management function device, the device according to claim 14.

21. The second core network device is an access and mobility management function device, the device according to claim 14.

22. A second core network device, a processing unit configured to select a first core network device that replaces the second core network device to provide services to a terminal device based on third information when there is a handover request, the third information indicating that the terminal device performs onboarding, and the first core network device supports an onboarding function, and the processing unit, a transceiver unit configured to transmit first information to the first core network device, the first information indicating that the terminal device performs onboarding, and the first core network device performs onboarding on the terminal device based on the first information, and the transceiver unit and having a device.

23. The third information is as follows: including one or more of registration type information, data network name information, network slice information, and information regarding a first value, the first value indicates the period during which the terminal device is registered with the network, or the first value indicates the remaining period during which the terminal device is permitted to register with the network, the device according to claim 22.

24. The transceiver unit is further configured to obtain the third information from a second access network device or the terminal device, The second access network device is an access network device that provides services to the terminal device before the execution of the handover. The device according to claim 22.

25. The first information includes one or more of the following: Data network name information, network slice information, and information regarding a first value, wherein the first value indicates a period during which the terminal device is registered with the network, or the first value indicates a remaining period during which the terminal device is permitted to register with the network. The device according to claim 22.

26. The first core network device and / or the second core network device is an access and mobility management function device. The device according to claim 22.

27. A communication device having a processor and a memory, wherein the processor executes a computer program or instructions stored in the memory so that the communication device executes the method according to any one of claims 1 to 8, or so that the communication device executes the method according to any one of claims 9 to 13. Communication device.

28. Having a computer program or instructions, when the computer program or the instructions are executed by a computer, the computer can execute the method according to any one of claims 1 to 8, or the computer can execute the method according to any one of claims 9 to 13. Computer-readable storage medium.

29. Having at least one processor, wherein the processor executes a computer program or instructions in a memory so that the method according to any one of claims 1 to 8 is implemented, or so that the method according to any one of claims 9 to 13 is implemented. Chip system.

Images