WO2022022347A1

WO2022022347A1 - Network access method, communication system, and communication apparatus

Info

Publication number: WO2022022347A1
Application number: PCT/CN2021/107499
Authority: WO
Inventors: 舒林
Original assignee: 华为技术有限公司
Priority date: 2020-07-31
Filing date: 2021-07-21
Publication date: 2022-02-03
Also published as: CN114071639A

Abstract

The present application provides a network access method, a communication system, and a communication apparatus. A mobility management network element in a first network receives access type information of a terminal device, so that the mobility management network element carries out access control on the terminal device according to the access type of the terminal device accessing the first network indicated in the access type information, for example, the type is a non-3GPP access, or accessing an SNPN by means of a PLMN, or the access type is a non-3GPP access, or accessing a PLMN by means of an SNPN.

Description

Method, communication system and communication device for accessing network

This application claims the priority of the Chinese patent application with the application number of 202010756365.2 and the application title of "Method for Accessing Network, Communication System and Communication Device" filed with the China Patent Office on July 31, 2020, the entire contents of which are incorporated by reference in this application.

technical field

The present application relates to the field of communication, and more particularly, to a method for accessing a network, a communication system and a communication device.

Background technique

The fifth generation (5G) network defined by the third generation partnership project (3GPP) supports multiple access types. A terminal device that supports multiple access types can select one of the access types to access the 5G core network (5G core, 5GCN) according to the configuration, or can select multiple access types to access the 5GCN at the same time. Based on its own network configuration and user subscription permission, operators can perform access control for different access types, allowing terminal equipment to access from a specific access type, and denying terminal equipment access from other access types.

3GPP supports the deployment of non-public networks (NPN). NPN is also called private network, which is different from traditional cellular network. NPN allows certain terminal devices with specific permissions to access. An independently deployed NPN is called an independent NPN (standalone non-public networks, SNPN). At present, the access types supported by 5GCN of SNPN include: 3GPP access and access to SNPN through public land mobile network (PLMN), the former is direct access and the latter is indirect access. In addition, SNPN may also support non-3GPP access (non-3GPP access) direct access.

Because of the introduction of SNPN, the access types supported by 5GCN of PLMN include: 3GPP access, access through SNPN, and non-3GPP access.

When a user equipment (UE) requests registration, the 5GCN needs to identify the access type currently used by the UE to perform access control on the UE. However, in the prior art, the UE and the 5GCN can distinguish between direct 3GPP access and direct non-3GPP access. However, two types of access via non-3GPP access cannot be distinguished: direct access via non-3GPP access and indirect access via SNPN to PLMN or PLMN to SNPN.

SUMMARY OF THE INVENTION

The present application provides a method, a communication system and a communication device for accessing a network, so that a mobility management network element in a first network can learn the access type of a terminal device accessing the first network, so as to perform access control on the terminal device .

A first aspect provides a method for accessing a network, comprising: a mobility management network element in a first network receiving access type information of a terminal device, the access type information instructing the terminal device to access the first network An access type of a network; the mobility management network element performs access control on the terminal device according to the access type information.

Optionally, the access type is accessing the first network through a second network, where the first network is a non-public network and the second network is a public network; or, the first network The network is a public network and the second network is a non-public network.

For example, the public network is PLMN and the non-public network is SNPN.

Optionally, the access type is non-3rd Generation Partnership Project 3GPP (non-3GPP) access.

According to the method for accessing a network provided by the present application, the mobility management network element can learn the access type of the terminal device accessing the first network according to the access type information, so as to perform access control on the terminal device. For example, if the first network is an SNPN, the mobility management network element can determine, according to the access type information, whether the terminal device directly accesses the SNPN through non-3GPP access or indirectly accesses the SNPN through PLMN, so that the corresponding type of access Enter to perform access control. For another example, if the first network is a PLMN, the mobility management network element can determine, according to the access type information, whether the terminal device directly accesses the PLMN through a non-3GPP or indirectly accesses the PLMN through an SNPN, so that the corresponding type of access can be accessed. Perform access control.

With reference to the first aspect, in a possible implementation manner of the first aspect, the mobility management network element in the first network receiving the access type information of the terminal device includes: the mobility management network element receiving information from the A registration request message of the terminal device, where the registration request message includes the access type information.

Based on the solution, the mobility management network element can determine the access type of the terminal device to access the first network according to the access type information in the registration request message of the terminal device.

With reference to the first aspect, in a possible implementation manner of the first aspect, the mobility management network element in the first network receiving the access type information of the terminal device includes: the mobility management network element receiving information from the The N2 interface message of the interworking network element in the first network, where the N2 interface message includes the access type information.

Based on this solution, the mobility management network element can determine the access type of the terminal device accessing the first network according to the access type information in the N2 interface message of the interworking network element in the first network.

With reference to the first aspect, in a possible implementation manner of the first aspect, the mobility management network element performs access control on the terminal device according to the access type information, including: when the terminal device does not In the case of being allowed to access the first network through the second network, the mobility management network element sends a registration rejection message to the terminal device, where the registration rejection message includes a cause value, and the cause value is used for Indicates that the terminal device is not allowed to access the first network through the second network.

Based on this solution, after receiving the cause value, the terminal device can learn that it cannot access the first network through the second network, so it will not subsequently initiate a registration request to the first network through the user plane of the registered second network. For example, the terminal device may disable (disable) the ability to access the first network through the second network.

With reference to the first aspect, in a possible implementation manner of the first aspect, the mobility management network element performs access control on the terminal device according to the access type information, including: when the terminal device does not In the case of being allowed to access the first network through the non-3GPP access, the mobility management network element sends a registration rejection message to the terminal device, where the registration rejection message includes a cause value, and the cause value is to indicate that the terminal device is not allowed to access the first network through the non-3GPP access.

Based on this solution, after receiving the cause value, the terminal device can learn that it cannot access the first network through non-3GPP access, so it will not initiate a registration request to the first network through non-3GPP access subsequently, such as the terminal device The ability to access the first network through non-3GPP access may be disabled.

In a second aspect, a method for accessing a network is provided, including: a terminal device sending access type information of the terminal device to a mobility management network element in a first network, where the access type information indicates the terminal device The access type for accessing the first network; the terminal device receives a registration rejection message from the mobility management network element, the registration rejection message includes a cause value, and the cause value is used to indicate that the terminal device does not is allowed to access the first network through the access type indicated by the access type information.

For example, the public network is PLMN and the non-public network is SNPN.

According to the method for accessing a network provided by the present application, the mobility management network element can know the access type of the terminal device accessing the first network according to the access type information provided by the terminal device, so as to control the access of the terminal device. For example, if the first network is an SNPN, the mobility management network element can determine whether the terminal device directly accesses the SNPN through non-3GPP access or indirectly accesses the SNPN through PLMN according to the access type information, so that the corresponding type of access can be accessed. Perform access control, such as denying the terminal device to access the first network through the access type indicated by the access type information.

With reference to the second aspect, in some implementations of the second aspect, the sending, by the terminal device, the access type information to the mobility management network element includes: the terminal device sends the information to the mobile management network element through the second network. The mobility management network element sends a registration request message, where the registration request message includes the access type information.

Based on this solution, the mobility management network element may determine, according to the access type information in the registration request message of the terminal device, that the access type of the terminal device accessing the first network is accessing the first network through the second network.

With reference to the second aspect, in some implementation manners of the second aspect, the sending, by the terminal device, the access type information to the mobility management network element includes: the terminal device using the non-3GPP access to The mobility management network element sends a registration request message, where the registration request message includes the access type information.

Based on this solution, the mobility management network element can determine, according to the access type information in the registration request message of the terminal device, that the access type of the terminal device accessing the first network is accessing the first network through non-3GPP access.

In a third aspect, a method for accessing a network is provided, including: an interworking network element in a first network receives a non-access stratum (NAS) message from a terminal device; the interworking network element determines the the access type of the terminal device to access the first network corresponding to the NAS message; the interworking network element sends access type information to the mobility management network element in the first network, the access type information Used to indicate the access type.

Based on this solution, the interworking network element in the first network can determine the access type of the terminal device accessing the first network according to the NAS message of the terminal device, and can send the access type to the mobility management network element, so that the mobility management The network element may determine the access type of the terminal device accessing the first network. Further, the mobility management network element can perform access control on the terminal device according to the access type.

With reference to the third aspect, in some implementations of the third aspect, the interworking network element determines the access type of the terminal device corresponding to the NAS message for accessing the first network, including: if the NAS The message comes from the user plane of the second network, and the interworking network element determines that the access type is to access the first network through the second network, wherein the first network is a non-public network, and the The second network is a public network; alternatively, the first network is a public network, and the second network is a non-public network.

With reference to the third aspect, in some implementations of the third aspect, the interworking network element determines the access type of the terminal device corresponding to the NAS message for accessing the first network, including: if the NAS The message comes from a signaling connection between the terminal device and the interworking network element, and the interworking network element determines that the access type is non-3rd Generation Mobile Partnership Project 3GPP access.

Based on the above solution, the interworking network element may determine the access type of the terminal device to access the first network according to whether the NAS message of the terminal device comes from the user plane or the signaling connection.

With reference to the third aspect, in some implementations of the third aspect, the NAS message is a registration request message.

In a fourth aspect, a communication system is provided, including: a mobility management network element and a terminal device in a first network; the terminal device is configured to send access type information to the mobility management network element, and the access type The type information indicates the access type of the terminal equipment to access the first network; the mobility management network element is configured to receive the access type information from the terminal equipment; according to the access type information, Perform access control on the terminal equipment.

According to the communication system provided by the present application, the mobility management network element in the first network can know the access type of the terminal device accessing the first network according to the access type information provided by the terminal device, so as to control the access of the terminal device. For example, if the first network is an SNPN, the mobility management network element can determine, according to the access type information, whether the terminal device accesses the SNPN through a non-3GPP access or accesses the SNPN through a PLMN, so that it can perform access to the corresponding type of access. access control.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the performing access control on the terminal device according to the access type information includes: sending a registration rejection message to the terminal device, the The registration rejection message includes a cause value for indicating that the terminal device is not allowed to access the first network through the access type.

With reference to the fourth aspect, in some implementations of the fourth aspect, the access type is accessing the first network through a second network, wherein the first network is a non-public network, and the first network is a non-public network. The second network is a public network; or, the first network is a public network, and the second network is a non-public network.

With reference to the fourth aspect, in some implementations of the fourth aspect, the access type is non-3rd Generation Mobile Partnership Project 3GPP access.

A fifth aspect provides a communication system, characterized by comprising: a mobility management network element in a first network and an interworking network element in the first network; the interworking network element is configured to move to the mobile network The management network element sends access type information, where the access type information indicates the access type of the terminal device to access the first network; the mobility management network element is configured to receive all information from the interworking network element. the access type information; and perform access control on the terminal device according to the access type information.

According to the communication system provided by the present application, the mobility management network element in the first network can learn the access type of the terminal device accessing the first network according to the access type information provided by the interworking network element, so as to control the access of the terminal device . For example, if the first network is an SNPN, the mobility management network element can determine, according to the access type information, whether the terminal device accesses the SNPN through a non-3GPP access or accesses the SNPN through a PLMN, so that it can perform access to the corresponding type of access. access control.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the interworking network element is further configured to: receive a non-access stratum NAS message from a terminal device; determine all information about the terminal device corresponding to the NAS message the access type.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the performing access control on the terminal device according to the access type information includes: sending a registration rejection message to the terminal device, the The registration rejection message includes a cause value for indicating that the terminal device is not allowed to access the first network through the access type.

With reference to the fifth aspect, in some implementations of the fifth aspect, the access type is accessing the first network through a second network, wherein the first network is a non-public network, and the first network The second network is a public network; or, the first network is a public network, and the second network is a non-public network.

With reference to the fifth aspect, in some implementations of the fifth aspect, the access type is non-3rd Generation Mobile Partnership Project 3GPP access.

In a sixth aspect, a communication apparatus is provided, including each module or unit for executing the method in the first aspect to the third aspect or any possible implementation manner of the first aspect to the third aspect.

In a seventh aspect, an apparatus is provided, including a processor. The processor is coupled to the memory and is operable to execute instructions in the memory to cause the apparatus to perform the method of the first aspect to the third aspect or any one of the possible implementations of the first aspect to the third aspect. Optionally, the apparatus further includes a memory. Optionally, the apparatus further includes an interface circuit, and the processor is coupled to the interface circuit.

In an eighth aspect, a processor is provided, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the method of the first aspect to the third aspect or any one of the possible implementations of the first aspect to the third aspect .

In a specific implementation process, the above-mentioned processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver, the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter, and the input circuit and output The circuit can be the same circuit that acts as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.

In a ninth aspect, a processing apparatus is provided, including a processor and a memory. The processor is used to read the instructions stored in the memory, and can receive signals through the receiver and transmit signals through the transmitter, so as to execute any one of the first to third aspects or any possible implementation manner of the first to third aspects method in .

Optionally, the processor is one or more, and the memory is one or more.

Alternatively, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

In the specific implementation process, the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting manner of the memory and the processor.

The processing device in the above ninth aspect may be a chip, and the processor may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software When implemented, the processor can be a general-purpose processor, which is realized by reading software codes stored in a memory, and the memory can be integrated in the processor or located outside the processor and exist independently.

In a tenth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code, or instructions), when the computer program is executed, causes the computer to execute the above-mentioned first to third aspects Or the method in any possible implementation manner of the first aspect to the third aspect.

In an eleventh aspect, a computer-readable medium is provided, the computer-readable medium stores a computer program (also referred to as code, or instruction), when it runs on a computer, causing the computer to execute the above-mentioned first to sixth aspects. The method in any one possible implementation manner of the three aspects or the first aspect to the third aspect.

A twelfth aspect provides a communication system, including one or more of the following: a mobility management network element in a first network, an interworking network element in the first network, and a terminal device.

Description of drawings

FIG. 1 is a schematic diagram of a communication system provided by the present application.

FIG. 2 is a schematic diagram of UE directly accessing SNPN through non-3GPP access and indirectly accessing SNPN through PLMN.

FIG. 3 is a schematic diagram of UE directly accessing PLMN through non-3GPP access and indirectly accessing PLMN through SNPN.

FIG. 4 is a schematic diagram of a protocol structure of the UE when the UE directly accesses the SNPN through non-3GPP access and indirectly accesses the SNPN through the PLMN.

FIG. 5 is a schematic diagram of a protocol structure of the UE when the UE directly accesses the PLMN through non-3GPP access and indirectly accesses the PLMN through the SNPN.

FIG. 6 is a schematic flowchart of a method for accessing a network provided by the present application.

FIG. 7 is a schematic flowchart of a specific example of a method for accessing a network provided by the application.

Fig. 8 is a schematic flowchart of a specific example of a method for accessing a network provided by the application.

Fig. 9 is a schematic flowchart of a specific example of a method for accessing a network provided by the application.

Fig. 10 is a schematic flowchart of a specific example of a method for accessing a network provided by the application.

Fig. 11 is a schematic block diagram of a communication device provided by the application.

FIG. 12 is a schematic block diagram of another communication device provided by the application.

Fig. 13 is a schematic block diagram of a terminal device provided by the application.

detailed description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (time division duplex) , TDD), fifth generation (5th generation, 5G) systems, new radio (new radio, NR) or other communication systems that may appear in the future.

The network elements or equipment mainly involved in this application include:

(1) Terminal equipment: may refer to user equipment (UE), access terminal, terminal in V2X communication, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal equipment, wireless communication equipment, user agent or user equipment. The terminal may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication function handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or terminals in future evolved public land mobile networks (PLMN) equipment, etc., which are not limited in this embodiment of the present application. The terminal may also include V2X equipment, such as a vehicle or an on board unit (OBU) in a vehicle.

(2) Mobility management network element: mainly performs access and mobility management control.

(3) Intercommunication network element: It can realize intercommunication between different networks. For example, the intercommunication between the non-public network and the core network of the public network can be realized. For another example, the intercommunication between the non-3GPP access network and the core network of the non-public network, or the intercommunication between the non-3GPP access network and the core network of the public network can be realized.

The present application provides a communication system, which will be described below with reference to FIG. 1 .

FIG. 1 is a schematic diagram of another communication system provided by the present application. The system 200 may include a mobility management network element 210 in the first network and an interworking network element 220 in the first network. Optionally, the system 200 may further include a terminal device 230 .

The interworking network element 220 is configured to send access type information to the mobility management network element 210, where the access type information indicates the access type of the terminal device 230 to access the first network;

The mobility management network element 210 is configured to receive the access type information from the interworking network element 220; and perform access control on the terminal device 230 according to the access type information.

Optionally, the interworking network element 220 is further configured to: receive a non-access stratum (NAS) message from the terminal device 230; determine the access type of the terminal device 230 corresponding to the NAS message .

Optionally, the performing access control on the terminal device 230 according to the access type information includes: sending a registration rejection message to the terminal device 230, where the registration rejection message includes a cause value, and the cause value is used to indicate The terminal device 230 is not allowed to access the first network through the access type.

Optionally, the access type is accessing the first network through a second network, where the first network is a non-public network and the second network is a public network; or, the first network is a public network, and the second network is a non-public network.

Optionally, the access type is that the terminal device 230 accesses through non-3GPP.

According to the communication system provided by the present application, the mobility management network element in the first network can learn the access type of the terminal device accessing the first network according to the access type information provided by the interworking network element, so as to control the access of the terminal device . For example, if the first network is an NPN, the mobility management network element can determine, according to the access type information, whether the terminal device accesses the NPN through a non-3GPP access or accesses the NPN through a public network, so that the corresponding type of access can be accessed. Perform access control.

It should be understood that other network elements other than the terminal device in the system 200 may be implemented by one device, or may be implemented jointly by multiple devices, which are not specifically limited in this embodiment of the present application. It can be understood that the functions of each network element can be implemented by hardware, software, or a combination of hardware and software.

It should also be understood that the mobility management network element and the interworking network element are only a name, and the name does not constitute a limitation on the device itself. In the 5G network and other future networks, the above network elements may also have other names. In addition, the system shown in FIG. 1 may further include other network elements that interact or communicate with the network elements in the figure.

The system shown in FIG. 1 may be implemented by a 5G system and other possible systems in the future, which are not specifically limited in this embodiment of the present application. When any of the above systems is implemented by a 5G system, the terminal equipment, mobility management network element, and interworking network element in the above system may correspond to the UE, AMF, and N3IWF in the 5G system, respectively.

Taking the 5G system as an example, the following describes the system architecture applied in this application with reference to FIG. 2 and FIG. 3 .

First, the network elements involved in FIG. 2 and FIG. 3 are briefly introduced.

(1) Radio access network (RAN): including but not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), wireless Access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP) in a wireless fidelity (WIFI) system ), etc., it can also be a fifth generation (5G) system, for example, a gNB or a transmission point (TRP or TP) in a new radio interface (NR), one or a group of base stations in a 5G system (including multiple antenna panels) The antenna panel, or, may also be a network node that constitutes a gNB or a transmission point, such as a baseband unit (building baseband unit, BBU) or a distributed unit (distributed unit, DU), etc.

(2) Access and mobility management function (AMF): connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management, etc. function.

(3) Session management function (SMF): It mainly performs functions such as session management, policy control function (PCF) issuing control policy execution, UPF selection, UE IP address allocation and other functions.

(4) User plane function (UPF): User plane related functions such as data packet routing and transmission, packet detection, service usage reporting, QoS processing, legal interception, uplink packet detection, and downlink packet storage.

(5) Data network (DN): An operator network that provides data transmission services for users, such as IP Multi-media Service (IMS), Internet, etc.

(6) N3 interface interworking function (N3inter-working function, N3IWF): It can realize the intercommunication between different networks. For example, the intercommunication between the non-public network and the core network of the public network can be realized. For another example, the intercommunication between the non-3GPP access network and the core network of the non-public network, or the intercommunication between the non-3GPP access network and the core network of the public network can be realized.

2 and 3 respectively show a schematic diagram of a system architecture. In Figures 2 and 3, NPN (SNPN is taken as an example in Figures 2 and 3) and PLMN have independent radio access network (RAN) and core network (core network, CN). The core networks of the SNPN and the PLMN are connected through the N3IWF, and the user plane and the control plane can communicate with each other through the N3IWF.

Referring to FIG. 2 , the UE may access the SNPN through the PLMN, which is an indirect access manner, and may also directly access the SNPN through non-3GPP access. However, the AMF in the SNPN does not know whether the UE accesses the NPN indirectly through the PLMN or directly accesses the SNPN through non-3GPP access, which is a problem to be solved by this application.

Referring to FIG. 3 , the UE may access the PLMN through an SNPN, which is an indirect access manner, and may also directly access the PLMN through a non-3GPP access. However, the AMF in the PLMN does not know whether the UE accesses the PLMN indirectly through the SNPN or directly accesses the PLMN through the non-3GPP access, which is another problem to be solved by this application.

It should be understood that each network element shown in FIG. 2 and FIG. 3 may be either hardware devices or chips, or software functions running on dedicated hardware, or virtualization instantiated on a platform (for example, a cloud platform). Features. It should also be understood that some network elements shown in FIG. 2 and FIG. 3 may be deployed in the same location (eg, on the same hardware device or software function), or may be deployed separately, which is not limited in this application. In addition, the interfaces between the network elements in the architectures shown in FIG. 3 and FIG. 4 are just an example, and in different communication systems or with the evolution of the system, the interfaces between the network elements may also be different from those shown in FIG. It is not limited herein.

FIG. 4 shows a schematic diagram of a protocol structure of the UE when the UE directly accesses the SNPN through non-3GPP access and indirectly accesses the SNPN through the PLMN.

Referring to FIG. 4 , the UE accessing the SNPN includes the SNPN non-access stratum NAS and the SNPN access stratum (AS), and the SNPN NAS is above the SNPN AS. SNPN AS includes two: SNPN 3GPP AS and SNPN non-3GPP (non-3GPP) AS. SNPN 3GPP AS supports 3GPP access, including NR, etc. SNPN 3GPP AS includes service data adaptation protocol (service data adaptation protocol, SDAP) layer and radio resource control (radio resource control, RRC) layer. SNPN 3GPP AS supports UE to directly access SNPN through 3GPP access. Since the UE supports indirect access to the SNPN through the PLMN, the SNPN NAS of the UE regards the PLMN NAS as a component of the SNPN non-3GPP AS, so the SNPN non-3GPP AS includes the PLMN NAS and the SNPN non-3GPP AS sublayer, The SNPN non-3GPP AS sublayer further includes management entities and non-3GPP access (eg WiFi). The PLMN NAS supports the UE to indirectly access the SNPN through the PLMN, and the SNPN non-3GPP AS sublayer supports the UE to directly access the SNPN through non-3GPP access.

FIG. 5 shows a schematic diagram of a protocol structure of the UE when the UE accesses the PLMN through non-3GPP access and SNPN.

Referring to Figure 5, the UE accessing the PLMN includes a PLMN NAS and a PLMN AS, and the PLMN NAS is on top of the PLMN AS. PLMN AS includes two: PLMN 3GPP AS and PLMN non-3GPP (non-3GPP) AS. PLMN 3GPP AS supports 3GPP access, including NR, etc. PLMN 3GPP AS includes SDAP layer and RRC layer. PLMN 3GPP AS supports UE to directly access PLMN through 3GPP access. Since the UE supports indirect access to the PLMN through the SNPN, the PLMN NAS of the UE regards the SNPN NAS as a component of the PLMN non-3GPP AS, so the PLMN non-3GPP AS includes the SNPN NAS and the PLMN non-3GPP AS sublayer, The PLMN non-3GPP AS sublayer further includes management entities and non-3GPP access (eg WiFi). The SNPN NAS supports the UE to access the PLMN indirectly through the SNPN, and the PLMN non-3GPPAS sublayer supports the UE to directly access the PLMN through the non-3GPP access.

The method for accessing the network provided by the present application will be described below.

FIG. 6 is a schematic flowchart of a method for accessing a network provided by the present application. The method can be applied to the system architecture shown in FIG. 2 or FIG. 3 . The method 500 is described below.

S510, the mobility management network element in the first network receives the access type information of the terminal device.

The access type information indicates the access type of the terminal device to access the first network.

Optionally, the access type may be accessing the first network through a second network, where the first network is a non-public network and the second network is a public network; or, the first network is a public network, and the second network is a public network is a non-public network.

Alternatively, the access type may be non-3GPP access.

In this paper, the public network can be PLMN; the non-public network can be SNPN or NPN (public network integrated NPN, PNI-NPN) integrated with the public network.

Accessing PLMN through SNPN (access PLMN via SNPN) can also be referred to as: accessing PLMN services through SNPN (access to PLMN services via an SNPN or to access PLMN services via an SNPN). Accessing PLMN services through SNPN means: UE is accessing PLMN services via an SNPN when the UE is connecting to the 5GCN of the PLMN using the 5GCN of the PLMN using the 3GPP access of the SNPN).

Accessing SNPN through PLMN (access SNPN via PLMN) can also be referred to as: accessing SNPN services through PLMN (access to SNPN services via a PLMN or to access SNPN services via a PLMN). Accessing SNPN services through PLMN means: UE is accessing SNPN services via a PLMN when the UE is connecting to the 5GCN of the SNPN using the 3GPP access of the PLMN).

Non-3GPP access (non-3GPP access) refers to: the UE accesses the core network of the PLMN or SNPN through the access layer connection with the N3IWF. The access layer connection between the UE and the N3IWF is an untrusted non-3GPP access (untrusted non-3GPP access), such as wireless fidelity (Wireless Fidelity, WiFi). This access type is different from the core network in which the UE accesses the PLMN or SNPN through the access layer connection between the UE and the radio access network RAN. The access layer connection between the UE and the radio access network RAN is 3GPP access (3GPP access). access), for example: NR in 5G systems.

In one manner, S510 may specifically be: the mobility management network element receives a registration request message from the terminal device.

Specifically, when the terminal device currently accesses the first network through the access type indicated by the access type information, it sends a registration request message to the mobility management network element, where the registration request message includes the access type information.

In another manner, S510 may specifically be: the mobility management network element receives the access type information from the interworking network element.

Specifically, the terminal device may send a NAS message to the interworking network element in the first network, and the interworking network element may determine the access type of the terminal device corresponding to the NAS message accessing the first network. Then, the interworking network element sends the access type information to the mobility management network element in the first network.

S520, the mobility management network element performs access control on the terminal device according to the access type information.

For example, if the terminal device is not allowed to access the first network through the access type indicated by the access type information, the mobility management network element may send a registration rejection message to the terminal device, where the registration rejection message includes a reason value, the reason The value is used to indicate that the terminal device is not allowed to access the first network through the access type indicated by the access type information. For another example, if the terminal device is allowed to access the first network through the access type indicated by the access type information, the mobility management network element may send a registration accept message to the terminal device, and the registration accept message indicates that the terminal device is allowed to pass through. The access type indicated by the access type information accesses the first network.

According to the method for accessing a network provided by the present application, the mobility management network element can learn the access type of the terminal device accessing the first network according to the access type information, so as to perform access control on the terminal device.

Several different examples of the method 500 are further described below in combination with the access type indicated by the access type information and the two implementation manners of step S510.

It should be noted that, for ease of understanding, the following description will take the naming of network elements in the 5G network as an example, and the public network as PLMN and the non-public network as SNPN as an example for description.

1. The first network is SNPN

Mode 1: The access type information is provided by the UE.

This will be described with reference to the flowchart shown in FIG. 7 .

Referring to FIG. 7, FIG. 7 is a schematic flowchart of a method for accessing a network provided by the present application. The method 600 can be applied to the network shown in FIG. 2 .

S601, the UE sends a registration request message #1 to the AMF in the SNPN through the PLMN. Correspondingly, the AMF receives the registration request message #1 sent by the UE.

Specifically, if the UE currently accesses the SNPN through the PLMN, the UE may send a registration request message #1 to the AMF in the SNPN. The registration request message #1 includes access type information #1, and the access type information #1 indicates that the access type is to access the SNPN through the PLMN, that is, access SNPN via PLMN.

It can be understood that the registration request message #1 is encapsulated as a NAS PDU, which can be sent to the N3IWF in the SNPN through the user plane (eg, UPF) of the PLMN, and further sent to the AMF by the N3IWF.

It should be understood that the registration request message #1 may also be transmitted to the N3IWF in the SNPN through the control plane of the PLMN, which is not limited in this application.

S602, the AMF performs access control on the UE according to the access type information #1.

For example, if the core network of the SNPN does not allow the UE to access the SNPN through the PLMN, that is, it does not allow access to the SNPN via the PLMN, the AMF executes:

S603a, the AMF sends a registration rejection message #1 (ie, an example of a registration rejection message) to the UE. Accordingly, the UE receives the registration rejection message #1 from the AMF.

The registration rejection message #1 includes a cause value for indicating that the UE is not allowed to access the SNPN via the PLMN, i.e., deny access to the SNPN via the PLMN. For example, the reason value is: access SNPN via PLMN not allowed.

After receiving the cause value, the UE can know that the SNPN cannot be accessed through the PLMN, so it will not initiate a registration request to the SNPN through the user plane of the registered PLMN. For example, the UE can disable the access to the SNPN through the PLMN. The ability to enter the SNPN.

For another example, if the UE is allowed to access the SNPN through the PLMN, that is, it is allowed to access the SNPN via the PLMN, the AMF can perform:

S603b, the AMF sends a registration acceptance message #1 (ie, an example of a registration acceptance message) to the UE. Accordingly, the UE receives the Registration Accept message #1 from the AMF.

The registration acceptance message #1 is used to indicate that the UE is allowed to access the SNPN through the PLMN, that is, to allow access to the SNPN via the PLMN.

S604, the UE sends a registration request message #2 to the AMF through the non-3GPP access. Correspondingly, the AMF receives the registration request message #2 sent by the UE.

If the UE currently directly accesses the SNPN through a non-3GPP access (eg, wifi), the UE may send a registration request message #2 to the AMF in the SNPN. The registration request message includes access type information #2, which is the access type information #2. Indicates that the access type is non-3GPP access (non-3GPP access).

The registration request message may be sent to the N3IWF in the SNPN through the access stratum Nwu connection between the UE and the N3IWF, and further sent to the AMF by the N3IWF.

S605, the AMF performs access control on the UE according to the access type information #2.

For example, if the UE is not allowed to directly access the SNPN through non-3GPP access, that is, it is not allowed to directly access the SNPN through non-3GPP access, the AMF executes:

S606a, the AMF sends a registration rejection message #2 (ie, another example of a registration rejection message) to the UE. Accordingly, the UE receives Registration Reject message #2 from the AMF.

The registration rejection message #2 may include a cause value, which is used to indicate that the UE is not allowed to directly access the SNPN through non-3GPP access, that is, rejects direct access to the SNPN through non-3GPP access. For example, the reason value is specifically: non-3GPP access not allowed (non-3GPP access not allowed).

After receiving the reason, the UE can know that it cannot directly access the SNPN through non-3GPP access, so it will not initiate a registration request to the SNPN through non-3GPP access. For example, the UE can prohibit direct access through non-3GPP access. The access capability of the incoming SNPN.

For another example, if the UE is allowed to directly access the SNPN through non-3GPP access, that is, allows direct access to the SNPN through non-3GPP access, the AMF may perform:

S606b, the AMF sends a registration acceptance message #2 (ie, another example of the registration acceptance message) to the UE. Accordingly, the UE receives the Registration Accept message #2 from the AMF.

The registration accept message #2 is used to indicate that the UE is allowed to directly access the SNPN through non-3GPP access, that is, it is allowed to directly access the SNPN through non-3GPP access.

According to the method for accessing the network provided by the present application, the UE can choose whether to directly access the SNPN through non-3GPP access, indirectly access the SNPN through PLMN, or access simultaneously, based on its own capabilities and configuration. When initiating a registration request to the core network of the SNPN through the selected access type, the UE can carry the corresponding access type information to the core network of the SNPN, so that the core network of the SNPN can identify the current The access type that the UE initiates the registration request, so that different access type control can be performed according to the network configuration and the user's subscription information, so as to meet the operator's access control requirements for different access types and improve the network operation efficiency.

It should be noted that, based on the capability and configuration of the UE, the UE may perform only one of steps S601 and S604, or may perform both. For example, if the UE supports accessing the SNPN through the PLMN, S601 may be performed, otherwise, S601 may not be performed. If the UE supports direct access to the SNPN through non-3GPP access, S604 may be performed, otherwise, S604 may not be performed. If the UE supports both access to the SNPN through the PLMN and direct access to the SNPN through non-3GPP access, S601 and S604 may be performed, or only one of the two may be performed.

Mode 2: The access type information is provided by the N3IWF in the SNPN.

This will be described with reference to the flowchart shown in FIG. 8 .

Referring to FIG. 8, FIG. 8 is a schematic flowchart of a method for accessing a network provided by the present application. The method 700 is described below.

S701, the UE sends a NAS message #1 to the N3IWF in the SNPN. Accordingly, the N3IWF receives NAS message #1 from the UE.

If the UE currently accesses the SNPN through the PLMN, the UE may send a NAS message #1 (ie, an example of a NAS message) to the N3IWF in the SNPN through the user plane (eg, UPF) in the PLMN. Exemplarily, the NAS message #1 may be a registration request message.

S702, the N3IWF determines the access type of the UE corresponding to the NAS message #1 accessing the first network.

If the N3IWF receives the NAS message #1 through the user plane, it can determine that the access type of the UE corresponding to the NAS message #1 accessing the first network is to access the SNPN through the PLMN, that is, access SNPN via PLMN.

S703, the N3IWF sends access type information #1 to the AMF in the SNPN. Accordingly, the AMF receives access type information #1 (ie, an example of access type information) from the N3IWF.

The access type information #1 is used to indicate the access type, that is, access the SNPN through the PLMN.

Optionally, the N3IWF may carry the access type information #1 through an interface message (eg, an N2 interface message) between the N3IWF and the AMF. For example, the interface message may be an initial UE message (initial UE message).

S704, the AMF performs access control on the UE according to the access type information #1.

For example, if the UE is not allowed to access the SNPN through the PLMN, that is, it is not allowed to access the SNPN via the PLMN, the AMF executes:

S705a, the AMF sends a registration rejection message #1 (ie, an example of a registration rejection message) to the UE. Accordingly, the UE receives the registration rejection message #1 from the AMF.

Step S705a is the same as S603a, for details, please refer to S603a.

For another example, if the UE is allowed to access the SNPN through the PLMN, that is, allows access to the SNPN via the PLMN, the AMF may perform:

S705b, the AMF sends a registration acceptance message #1 (ie, an example of a registration acceptance message) to the UE. Accordingly, the UE receives the Registration Accept message #1 from the AMF.

Step S705b is the same as S603b, for details, please refer to S603b.

S706, the UE sends the NAS message #2 to the N3IWF in the SNPN. Accordingly, the N3IWF receives NAS message #2 from the UE.

If the UE currently directly accesses the SNPN through non-3GPP (eg, wifi) access, the UE may send NAS message #2 (ie, another example of a NAS message) to the N3IWF through the signaling connection between the UE and the N3IWF in the SNPN. . Exemplarily, the NAS message #2 may be a registration request message.

S707, the N3IWF determines the access type of the UE corresponding to the NAS message #2 accessing the first network.

If the N3IWF receives the NAS message #2 through the signaling connection between the UE and the N3IWF, it may determine that the access type of the UE corresponding to the NAS message #2 accessing the first network is non-3GPP access.

S708, the N3IWF sends the access type information #2 (ie, another example of the access type information) to the AMF in the SNPN. Accordingly, the AMF receives the access type information from the N3IWF.

The access type information #2 is used to indicate the access type, that is, non-3GPP access.

Optionally, the N3IWF may carry the access type information #2 through an interface message (eg, an N2 interface message) between the N3IWF and the AMF. For example, the interface message may be an initial UE message (initial UE message).

S709, the AMF performs access control on the UE according to the access type information #2.

For example, if the UE is not allowed to directly access the SNPN through non-3GPP access, the AMF performs:

S710a, the mobile management network element sends a registration rejection message #2 (ie, another example of the registration rejection message) to the UE. Accordingly, the UE receives Registration Reject message #2 from the AMF.

Step S710a is the same as S606a, for details, please refer to S606a.

For another example, if the UE is allowed to directly access the SNPN through non-3GPP access, the AMF may perform:

S710b, the AMF sends a registration acceptance message #2 (ie, another example of the registration acceptance message) to the UE. Accordingly, the UE receives the Registration Accept message #2 from the AMF.

Step S710b is the same as S606b, for details, please refer to S606b.

According to the method for accessing the network provided by this application, the N3IWF determines the access type currently selected by the UE according to whether the received NAS message sent by the UE is from the user plane or the signaling connection, and then sends the determined access type to the SNPN. Access type information, so that the SNPN can identify the access type of the current UE initiating the registration request according to the access type information carried by the N3IWF, so that different access type control can be performed according to the network configuration and the user's subscription information. Access control requirements for different access types to improve network operation efficiency.

It should be noted that, based on the capability and configuration of the UE, the UE may perform only one of steps S701 and S706, or may perform both. For example, if the UE supports accessing the SNPN through the PLMN, S701 may be performed, otherwise, S701 may not be performed. If the UE supports direct access to the SNPN through non-3GPP access, S706 may be performed, otherwise, S706 may not be performed. If the UE supports both access to the SNPN through the PLMN and direct access to the SNPN through non-3GPP access, S701 and S706 may be performed, or only one of the two may be performed.

2. The first network is PLMN

Mode 1: The access type information is provided by the UE.

This will be described with reference to the flowchart shown in FIG. 9 .

Referring to FIG. 9, FIG. 9 is a schematic flowchart of a method for accessing a network provided by the present application. The method 900 can be applied to the network structure shown in FIG. 3 .

S901, the UE sends a registration request message #3 to the AMF in the PLMN through the SNPN. Correspondingly, the AMF receives the registration request message #3 sent by the UE.

Specifically, if the UE currently accesses the PLMN through the SNPN, the UE may send a registration request message #3 to the AMF in the PLMN. The registration request message #3 includes access type information #3, and the access type information #3 indicates that the access type is to access the PLMN through the SNPN, that is, access PLMN via SNPN.

It can be understood that the registration request message #3 is encapsulated as a NAS PDU, which can be sent to the N3IWF in the PLMN through the user plane (eg, UPF) of the SNPN, and further sent to the AMF by the N3IWF.

It should be understood that the registration request message #3 may also be transmitted to the N3IWF in the PLMN through the control plane of the SNPN, which is not limited in this application.

S902, the AMF performs access control on the UE according to the access type information #3.

For example, if the UE is not allowed to access the PLMN through the SNPN, that is, it is not allowed to access the PLMN via the SNPN, the AMF executes:

S903a, the AMF sends a registration rejection message #3 (ie, an example of a registration rejection message) to the UE. Accordingly, the UE receives Registration Reject message #3 from the AMF.

The registration rejection message #3 includes a cause value, which is used to indicate that the UE is not allowed to access the PLMN through the SNPN, that is, refusing to access the PLMN via the SNPN. For example, the reason value is specifically: access PLMN via SNPN not allowed (access PLMN via SNPN not allowed).

After receiving the reason, the UE can know that it cannot access the PLMN through the SNPN, so it will not initiate a registration request to the PLMN through the user plane of the registered SNPN. For example, the UE can prohibit access to the PLMN through the SNPN. access capability.

For another example, if the UE is allowed to access the PLMN through the SNPN, that is, it is allowed to access the PLMN via the SNPN, the AMF can perform:

S903b, the AMF sends a registration acceptance message #3 (ie, an example of a registration acceptance message) to the UE. Accordingly, the UE receives the Registration Accept message #3 from the AMF.

The registration acceptance message #3 is used to indicate that the UE is allowed to access the PLMN through the SNPN, that is, it is allowed to access the PLMN through the access PLMN via the SNPN.

S904, the UE sends a registration request message #4 to the AMF through the non-3GPP access. Correspondingly, the AMF receives the registration request message #4 sent by the UE.

If the UE currently directly accesses the PLMN through non-3GPP access, the UE may send a registration request message #4 to the AMF in the PLMN, the registration request message includes access type information #4, and the access type information #4 indicates that the access type is Non-3GPP access (non-3GPP access).

The registration request message may be sent to the N3IWF in the PLMN through the access stratum Nwu connection between the UE and the N3IWF, and further sent to the AMF by the N3IWF.

S905, the AMF performs access control on the UE according to the access type information #4.

For example, if the UE is not allowed to directly access the PLMN through non-3GPP access, that is, it is not allowed to directly access the PLMN through non-3GPP access, the AMF executes:

S906a, the AMF sends a registration rejection message #4 (ie, another example of a registration rejection message) to the UE. Accordingly, the UE receives Registration Reject message #4 from the AMF.

The registration rejection message #4 includes a cause value, which is used to indicate that the UE is not allowed to directly access the PLMN through non-3GPP access, ie rejects direct access to the PLMN through non-3GPP access. For example, the reason value is specifically: non-3GPP access not allowed (non-3GPP access not allowed).

After receiving the reason, the UE can know that it cannot directly access the PLMN through non-3GPP access, so it will not initiate a registration request to the PLMN through non-3GPP access subsequently. For example, the UE can prohibit direct access through non-3GPP access. access capability into the PLMN.

For another example, if the UE is allowed to directly access the PLMN through non-3GPP access, the AMF may perform:

S906b, the AMF sends a registration acceptance message #4 (ie, another example of the registration acceptance message) to the UE. Accordingly, the UE receives the Registration Accept message #4 from the AMF.

Registration Accept message #4 is used to indicate that the UE is allowed to directly access the PLMN through non-3GPP access.

According to the method for accessing the network provided by this application, the UE can choose whether to directly access the PLMN through non-3GPP access, indirectly access the PLMN through SNPN, or simultaneously access, based on its own capabilities and configuration. When initiating a registration request to the core network of the PLMN through the selected access type, the UE can carry the corresponding access type information to the core network of the PLMN, so that the core network of the PLMN can identify the current The access type that the UE initiates the registration request, so that different access type control can be performed according to the network configuration and the user's subscription information, so as to meet the operator's access control requirements for different access types and improve the network operation efficiency.

It should be noted that, based on the capability and configuration of the UE, the UE may perform only one of steps S901 and S904, or may perform both. For example, if the UE supports accessing the PLMN through the SNPN, S901 may be performed, otherwise, S901 may not be performed. If the UE supports direct access to the PLMN through non-3GPP access, S904 may be performed, otherwise, S904 may not be performed. If the UE supports both access to PLMN through SNPN and direct access to PLMN through non-3GPP access, S901 and S904 may be performed, or only one of the two may be performed.

Mode 2: The access type information is provided by the N3IWF in the PLMN.

This will be described with reference to the flowchart shown in FIG. 10 .

Referring to FIG. 10, FIG. 10 is a schematic flowchart of a method for accessing a network provided by the present application. The method 1000 is described below.

S1001, the UE sends a NAS message #3 to the N3IWF in the PLMN. Accordingly, the N3IWF receives NAS message #3 from the UE.

If the UE currently accesses the PLMN through the SNPN, the UE may send the NAS message #3 (ie, an example of the NAS message) to the N3IWF in the PLMN through the user in the SNPN. Exemplarily, the NAS message #3 may be a registration request message.

S1002, the N3IWF determines the access type of the UE corresponding to the NAS message #3 accessing the first network.

If the N3IWF receives the NAS message #3 through the user plane, it can determine that the access type of the UE corresponding to the NAS message #3 accessing the first network is to access the PLMN through the SNPN, that is, access PLMN via SNPN.

S1003, the N3IWF sends access type information #3 to the AMF in the PLMN. Accordingly, the AMF receives access type information #3 (ie, an example of access type information) from the N3IWF.

Wherein, the access type information #3 is used to indicate the access type, that is, to access the PLMN through the SNPN.

Optionally, the N3IWF may carry the access type information #3 through an interface message (eg, an N2 interface message) between the N3IWF and the AMF. For example, the interface message may be an initial UE message (initial UE message).

S1004, the AMF performs access control on the UE according to the access type information #3.

S1005a, the AMF sends a registration rejection message #3 (ie, an example of a registration rejection message) to the UE. Accordingly, the UE receives Registration Reject message #3 from the AMF.

Step S1005a is the same as S903a, for details, please refer to S903a.

S1005b, the AMF sends a registration acceptance message #3 (ie, an example of a registration acceptance message) to the UE. Accordingly, the UE receives the Registration Accept message #3 from the AMF.

Step S1005b is the same as S903b, for details, please refer to S903b.

S1006, the UE sends a NAS message #4 to the N3IWF in the PLMN. Accordingly, the N3IWF receives NAS message #4 from the UE.

If the UE currently directly accesses the PLMN through non-3GPP access, the UE may send NAS message #4 (ie, another example of a NAS message) to the N3IWF in the PLMN through the signaling connection between the UE and the N3IWF in the PLMN. Exemplarily, the NAS message #4 may be a registration request message.

S1007, the N3IWF determines the access type of the UE corresponding to the NAS message #4 accessing the first network.

If the N3IWF receives the NAS message #4 through the signaling connection between the UE and the N3IWF, it may determine that the access type of the UE corresponding to the NAS message #4 accessing the first network is non-3GPP access.

S1008, the N3IWF sends the access type information #4 (ie, another example of the access type information) to the AMF in the PLMN. Accordingly, the AMF receives the access type information from the N3IWF.

The access type information #4 is used to indicate the access type, that is, non-3GPP access.

Optionally, the N3IWF may carry the access type information #4 through an interface message (eg, an N2 interface message) between the N3IWF and the AMF. For example, the interface message may be an initial UE message (initial UE message).

S1009, the AMF performs access control on the UE according to the access type information #4.

For example, if the UE is not allowed to directly access the PLMN through non-3GPP access, the AMF performs:

S1010a, the mobile management network element sends a registration rejection message #4 (ie, another example of the registration rejection message) to the UE. Accordingly, the UE receives Registration Reject message #4 from the AMF.

Step S1010a is the same as S906a, for details, please refer to S906a.

S1010b, the AMF sends a registration acceptance message #4 (ie, another example of the registration acceptance message) to the UE. Accordingly, the UE receives the Registration Accept message #4 from the AMF.

Step S1010b is the same as S906b, for details, please refer to S906b.

According to the method for accessing the network provided by this application, the N3IWF can send the determined access type to the PLMN after determining the access type currently selected by the UE according to whether the received NAS message sent by the UE is from the user plane or the signaling connection. In this way, the PLMN can identify the access type of the current UE initiating the registration request according to the access type information carried by the N3IWF, so that it can perform different access type control according to the network configuration and the user's subscription information. Improve network operation efficiency according to the access control requirements of different access types.

It should be noted that, based on the capability and configuration of the UE, the UE may perform only one of steps S1001 and S1006, or both. For example, if the UE supports accessing the PLMN through the SNPN, S1001 may be performed, otherwise, S1001 may not be performed. If the UE supports direct access to the PLMN through non-3GPP access, S1006 may be performed, otherwise, S1006 may not be performed. If the UE supports both access to PLMN through SNPN and direct access to PLMN through non-3GPP access, S1001 and S1006 may be performed, or only one of the two may be performed.

It should be understood that various solutions in the embodiments of the present application may be used in a reasonable combination, and the explanations or descriptions of various terms appearing in the embodiments may be referred to or explained in each embodiment, which is not limited.

It should also be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and inherent logic. The various numerical numbers or serial numbers involved in the above processes are only for the convenience of description, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In the above, the methods provided by the embodiments of the present application are described in detail with reference to FIG. 6 to FIG. 10 . Hereinafter, the device provided by the embodiment of the present application will be described in detail with reference to FIG. 11 to FIG. 13 .

FIG. 11 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application. As shown in FIG. 11 , the communication apparatus 2000 may include a transceiver unit 2010 and a processing unit 2020 .

The transceiver unit 2010 may be used to send information to or receive information from other devices. The processing unit 2020 may be used to perform internal processing of the device.

In an implementation manner, the communication apparatus 2000 corresponds to a mobility management network element (eg, AMF in a PLMN or SNPN) in the first network in the foregoing method embodiment. The communication apparatus 2000 may be a mobility management network element in the first network or a chip configured in the mobility management network element in the first network, and may include an operation performed by the mobility management network element in the first network. unit.

Specifically, the transceiver unit 2010 is configured to receive access type information of the terminal device, where the access type information indicates the access type of the terminal device to access the first network; the processing unit 2020 is configured to receive the access type information according to the Access type information, and perform access control on the terminal device.

Optionally, the access type is non-3rd Generation Mobile Partnership Project 3GPP access.

Optionally, the receiving unit is specifically configured to: receive a registration request message from the terminal device, where the registration request message includes the access type information.

Optionally, the receiving unit is specifically configured to: receive an N2 interface message from an interworking network element in the first network, where the N2 interface message includes the access type information.

Optionally, the receiving unit is specifically configured to: in the case that the terminal device is not allowed to access the first network through the second network, send a registration rejection message to the terminal device, where the registration rejection message A cause value is included, and the cause value is used to indicate that the terminal device is not allowed to access the first network through the second network.

Optionally, the receiving unit is specifically configured to: in the case that the terminal device is not allowed to access the first network through the non-3GPP access, send a registration rejection message to the terminal device, the registration rejection The message includes a cause value for indicating that the terminal device is not allowed to access the first network through the non-3GPP access.

In another implementation manner, the communication apparatus 2000 corresponds to the terminal device (eg, UE) in the foregoing method embodiment. The communication apparatus 2000 may be a terminal device or a chip configured in the terminal device, which may include a unit for performing operations performed by the terminal device.

A transceiver unit 2010, configured to send access type information of the communication device 2000 to a mobility management network element in the first network, where the access type information indicates the access type of the communication device 2000 to access the first network The transceiver unit 2010 is further configured to receive a registration rejection message from the mobility management network element, where the registration rejection message includes a cause value, and the cause value is used to indicate that the communication device 2000 is not allowed to pass the connection The access type indicated by the access type information accesses the first network.

Optionally, the transceiver unit 2010 is specifically configured to: send a registration request message to the mobility management network element through the second network, where the registration request message includes the access type information.

Optionally, the transceiver unit 2010 is specifically configured to: send a registration request message to the mobility management network element through the non-3GPP access, where the registration request message includes the access type information.

In yet another implementation manner, the communication apparatus 2000 corresponds to an interworking network element (eg, an N3IWF in a PLMN or an SNPN) in the first network in the foregoing method embodiment. The communication apparatus 2000 may be an interworking network element in the first network or a chip configured in the interworking network element in the first network, and may include a unit for performing operations performed by the interworking network element in the first network.

Specifically, the transceiver unit 2010 is configured to receive a non-access stratum NAS message from a terminal device; the processing unit 2020 is configured to determine the access type of the terminal device corresponding to the NAS message to access the first network; The transceiver unit 2010 is further configured to send access type information to a mobility management network element in the first network, where the access type information is used to indicate the access type.

Optionally, the processing unit 2020 is specifically configured to: if the NAS message received by the receiving unit comes from the user plane of the second network, determine that the access type is accessing the first network through the second network, wherein , the first network is a non-public network, and the second network is a public network; or, the first network is a public network, and the second network is a non-public network.

Optionally, the processing unit 2020 is specifically configured to: if the NAS message received by the receiving unit comes from a signaling connection between the terminal device and the communication apparatus 2000, determine that the access type is non-third-generation mobile Partnership Program 3GPP Access.

Optionally, the NAS message is a registration request message.

It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.

It should also be understood that when the communication device 2000 corresponds to a mobility management network element in the first network or an interworking network element in the first network, the transceiver unit 2010 in the communication device 2000 may correspond to the communication device 3000 shown in FIG. 12 . The communication interface 3200 in the communication device 2000 may correspond to the processor 3100 in the communication device 3000 shown in FIG. 12 . When the communication device 2000 corresponds to a terminal device, the transceiver unit 2010 in the communication device 2000 may correspond to the transceiver 4010 in the terminal device 4000 shown in FIG. 13 , and the processing unit 2020 in the communication device 2000 may correspond to FIG. 13 The processor 4001 or the processing device 4004 in the terminal device 4000 shown in FIG.

FIG. 12 shows a schematic block diagram of another communication apparatus 3000 provided by the present application. Any network element involved in the above method embodiments, such as a mobility management network element in the first network or an interworking network element in the first network, etc., can be implemented by the communication device shown in FIG. 12 .

It should be understood that the communication apparatus 3000 may be an entity device, or a component of the entity device (eg, an integrated circuit, a chip, etc.), or a functional module in the entity device.

As shown in FIG. 12 , the communication apparatus 3000 includes: one or more processors 3100 . The processor 3100 may store execution instructions for executing the methods of the embodiments of the present application. Optionally, the processor 3100 may call the communication interface 3200 to implement the functions of receiving and sending. The communication interface 3200 may be a logical interface or a physical interface, which is not limited. For example, the communication interface 3200 may be a transceiver circuit, an interface circuit, a transceiver, or a transceiver circuit for implementing receiving and transmitting functions, or the like. The sending function and the receiving function of the communication interface 3200 may be separated or integrated. The above-mentioned transceiver circuit or interface circuit can be used for code/data reading and writing, or the above-mentioned transceiver circuit or interface circuit can be used for signal transmission or transmission.

Optionally, the communication apparatus 3000 may further include a memory 3300 . This embodiment of the present application does not specifically limit the specific deployment location of the memory 3300 , and the memory 3300 may be integrated in the processor 3100 or independent of the processor 3100 . In the case where the communication device 3000 does not include a memory, the communication device 3000 only needs to have a processing function, and the memory can be deployed in other locations (eg, a cloud system).

The processor 3100, the memory 3300 and the communication interface 3200 communicate with each other through an internal connection path to transmit control and/or data signals.

It will be appreciated that, although not shown, the communication device 3000 may also include other devices, such as input devices, output devices, batteries, and the like.

Optionally, in some embodiments, the memory 3300 may store execution instructions for executing the methods of the embodiments of the present application. The processor 3100 can execute the instructions stored in the memory 3300 in combination with other hardware (eg, the communication interface 3200) to complete the steps of the methods shown below. For specific working processes and beneficial effects, refer to the descriptions in the above method embodiments.

The methods disclosed in the embodiments of the present application may be applied to the memory 3300 or implemented by the memory 3300 . The memory 3300 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the method can be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA), or other possible solutions. Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. Software modules can be located in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc. in the storage medium. The storage medium is located in the memory, and the processor reads the instructions in the memory, and completes the steps of the above method in combination with its hardware.

It will be appreciated that memory 3300 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory can be a read-only memory ROM, a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory RAM, which acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

FIG. 13 is a schematic structural diagram of a terminal device 4000 provided by an embodiment of the present application. As shown in the figure, the terminal device 4000 includes a processor 4001 and a transceiver 4002 . Optionally, the terminal device 4000 may further include a memory 4003 . Among them, the processor 4001, the transceiver 4002 and the memory 4003 can communicate with each other through an internal connection path to transmit control and/or data signals, the memory 4003 is used to store computer programs, and the processor 4001 is used to retrieve data from the memory 4003. The computer program is invoked and executed to control the transceiver 4002 to send and receive signals.

The above-mentioned processor 4001 and the memory 4003 may be combined into a processing device 4004, and the processor 4001 is configured to execute the program codes stored in the memory 4003 to realize the functions of the terminal device in the above-mentioned method embodiments. It should be understood that the processing device 4004 shown in the figure is only an example. During specific implementation, the memory 4003 may also be integrated in the processor 4001 or independent of the processor 4001 . This application does not limit this.

The above-mentioned terminal device 4000 may further include an antenna 4010 for transmitting the uplink data or uplink control signaling output by the transceiver 4002 through wireless signals.

It should be understood that the terminal device 4000 shown in FIG. 13 can implement various processes related to the terminal device in the foregoing method embodiments. The operations or functions of each module in the terminal device 4000 are respectively to implement the corresponding processes in the foregoing method embodiments. For details, reference may be made to the descriptions in the foregoing method embodiments, and to avoid repetition, the detailed descriptions are appropriately omitted here.

Optionally, the above-mentioned terminal device 4000 may further include a power supply 4005 for providing power to various devices or circuits in the terminal device.

In addition, in order to make the functions of the terminal device more complete, the terminal device 4000 may also include one or more of an input unit 4006, a display unit 4007, an audio circuit 4011, a camera 4009, a sensor 4008, etc., the audio circuit 4011 may also include a speaker 40081, a microphone 40082, and the like.

It should be understood that the processing device 4004 or the processor 4001 may be a chip. For example, the processing device 4004 or the processor 4001 may be a field programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (application specific integrated circuit) integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and can also be a system on chip (system on chip, SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller). controller unit, MCU), it can also be a programmable logic device (PLD) or other integrated chips. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

The memory 4003 may be any form of memory described above, which will not be repeated here.

The present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer program code enables the computer to execute any of the foregoing method embodiments on the terminal device side, on the first network The method for the mobility management network element side or the interworking network element side in the first network.

The present application further provides a computer-readable medium, where program codes are stored in the computer-readable medium, and when the program codes are run on a computer, the computer enables the computer to perform the movement on the terminal device side and in the first network in the foregoing method embodiments. A method for managing a network element side or an interworking network element side in a first network.

The present application also provides a system, which includes one or more of the following: a terminal device, a mobility management network element in the first network, and an interworking network element in the first network.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media. The available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state discs, SSD)) etc.

The network equipment in each of the above apparatus embodiments completely corresponds to the terminal equipment and the network equipment or terminal equipment in the method embodiments, and corresponding steps are performed by corresponding modules or units. For the sending step, other steps except sending and receiving may be performed by a processing unit (processor). For functions of specific units, reference may be made to corresponding method embodiments. The number of processors may be one or more.

The terms "component", "module", "system" and the like are used in this specification to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, or a computer. By way of illustration, both an application running on a computing device and the computing device may be components. One or more components may reside within a process or thread of execution, and a component may be localized on one computer or distributed among 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may, for example, pass a signal through a local system based on a signal having one or more data packets (such as data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems through signals). or remote process to communicate.

It is to be understood that reference throughout the specification to an "embodiment" means that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Thus, various embodiments throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

It should be understood that, in the embodiments of the present application, the numbers "first", "second"... are only used to distinguish different objects, such as to distinguish different network devices, and do not limit the scope of the embodiments of the present application. The example is not limited to this.

It should also be understood that in this application, "when", "if" and "if" all mean that the network element will make corresponding processing under certain objective circumstances, not a limited time, and does not require the network element There must be a judgmental action during implementation, and it does not mean that there are other restrictions.

It should also be understood that, in this application, "at least one" refers to one or more, and "a plurality" refers to two or more.

It should also be understood that, in each embodiment of the present application, "B corresponding to A" indicates that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.

It should also be understood that the term "and/or" in this document is only an association relationship for describing associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time. B, there are three cases of B alone. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

In this application, meanings similar to the expression "an item includes one or more of the following: A, B, and C" generally means that the item can be any of the following: A; B, unless otherwise specified. ;C;A and B;A and C;B and C;A,B and C;A and A;A,A and A;A,A and B;A,A and C,A,B and B;A , C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B and C. A total of three elements of A, B and C are used as examples above to illustrate the optional items of the item. When the expression is "the item includes at least one of the following: A, B, ..., and X", it means that the expression is in When there are more elements, then the items to which the item can apply can also be obtained according to the preceding rules.

It can be understood that, in the embodiments of the present application, the terminal device and/or the network device may perform some or all of the steps in the embodiments of the present application, these steps or operations are only examples, and the embodiments of the present application may also perform other operations or various Variation of operations. In addition, various steps may be performed in different orders presented in the embodiments of the present application, and may not be required to perform all the operations in the embodiments of the present application.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk and other media that can store program codes.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

A method for accessing a network, comprising:

The mobility management network element in the first network receives the access type information of the terminal device, the access type information indicating the access type of the terminal device to access the first network;

The mobility management network element performs access control on the terminal device according to the access type information.
The method of claim 1, wherein the access type is accessing the first network through a second network, wherein the first network is a non-public network, and the second network is public network; or, the first network is a public network, and the second network is a non-public network.
The method of claim 1, wherein the access type is non-3rd Generation Mobile Partnership Project 3GPP access.
The method according to any one of claims 1 to 3, wherein receiving the access type information of the terminal device by the mobility management network element in the first network comprises:

The mobility management network element receives a registration request message from the terminal device, where the registration request message includes the access type information.
The method according to any one of claims 1 to 3, wherein receiving the access type information of the terminal device by the mobility management network element in the first network comprises:

The mobility management network element receives an N2 interface message from an interworking network element in the first network, where the N2 interface message includes the access type information.
The method according to claim 2, wherein the mobility management network element performs access control on the terminal device according to the access type information, comprising:

In the case that the terminal device is not allowed to access the first network through the second network, the mobility management network element sends a registration rejection message to the terminal device, where the registration rejection message includes a cause value, The cause value is used to indicate that the terminal device is not allowed to access the first network through the second network.
The method according to claim 3, wherein the mobility management network element performs access control on the terminal device according to the access type information, comprising:

In the case that the terminal device is not allowed to access the first network through the non-3GPP access, the mobility management network element sends a registration rejection message to the terminal device, where the registration rejection message includes a cause value , and the cause value is used to indicate that the terminal device is not allowed to access the first network through the non-3GPP access.
A method for accessing a network, comprising:

The terminal device sends the access type information of the terminal device to the mobility management network element in the first network, where the access type information indicates the access type of the terminal device to access the first network;

The terminal device receives a registration rejection message from the mobility management network element, the registration rejection message includes a cause value, and the cause value is used to indicate that the terminal device is not allowed to pass the information indicated by the access type information. The access type accesses the first network.
The method of claim 8, wherein the access type is accessing the first network through a second network, wherein the first network is a non-public network, and the second network is public network; or, the first network is a public network, and the second network is a non-public network.
The method according to claim 9, wherein the terminal device sends the access type information to the mobility management network element, comprising:

The terminal device sends a registration request message to the mobility management network element through the second network, where the registration request message includes the access type information.
The method of claim 8, wherein the access type is non-3rd Generation Mobile Partnership Project 3GPP access.
The method according to claim 11, wherein sending the access type information to the mobility management network element by the terminal device comprises:

The terminal device sends a registration request message to the mobility management network element through the non-3GPP access, where the registration request message includes the access type information.
A method for accessing a network, comprising:

The interworking network element in the first network receives the non-access stratum NAS message from the terminal device;

determining, by the interworking network element, an access type of the terminal device corresponding to the NAS message accessing the first network;

The interworking network element sends access type information to the mobility management network element in the first network, where the access type information is used to indicate the access type.
The method according to claim 13, wherein determining, by the interworking network element, an access type of the terminal device corresponding to the NAS message to access the first network, comprising:

If the NAS message comes from the user plane of the second network, the interworking network element determines that the access type is accessing the first network through the second network, where the first network is a non-public network , and the second network is a public network; or, the first network is a public network, and the second network is a non-public network.
The method according to claim 13, wherein determining, by the interworking network element, an access type of the terminal device corresponding to the NAS message to access the first network, comprising:

If the NAS message comes from a signaling connection between the terminal device and the interworking network element, the interworking network element determines that the access type is non-3rd Generation Mobile Partnership Project 3GPP access.
The method according to any one of claims 13 to 15, wherein the NAS message is a registration request message.
A communication system, comprising: a mobility management network element in a first network and an interworking network element in the first network;

The interworking network element is configured to send access type information to the mobility management network element, where the access type information indicates the access type of the terminal device to access the first network;

The mobility management network element is configured to receive the access type information from the interworking network element; and perform access control on the terminal device according to the access type information.
The system of claim 17, wherein the interworking network element is further configured to:

Receive a non-access stratum NAS message from a terminal device;

The access type of the terminal device corresponding to the NAS message is determined.
The system according to claim 17 or 18, wherein the performing access control on the terminal device according to the access type information comprises:

A registration rejection message is sent to the terminal device, the registration rejection message including a cause value for indicating that the terminal device is not allowed to access the first network through the access type.
The system according to any one of claims 17 to 19, wherein the access type is accessing the first network through a second network, wherein the first network is a non-public network, and The second network is a public network; or, the first network is a public network, and the second network is a non-public network.
The system according to any one of claims 17 to 19, wherein the access type is non-3rd Generation Mobile Partnership Project 3GPP access.
A communication device, characterized in that the device is configured to perform the method described in any one of claims 1 to 7, or any one of claims 8 to 12, or any one of claims 13 to 16. method.
A mobility management network element, comprising: a processor and a memory;

The memory is used for storing computer-executable instructions, and when the mobility management network element is running, the processor executes the computer-executable instructions stored in the memory, so that the mobility management network element executes the operations according to claims 1 to 1. The method of any one of 7.
A terminal device, comprising: a processor and a memory;

The memory is used to store computer-executed instructions, and when the terminal device is running, the processor executes the computer-executed instructions stored in the memory, so that the terminal device executes any one of claims 8 to 12 method described in item.
An intercommunication network element, characterized in that it comprises: a processor and a memory;

The memory is used for storing computer-executable instructions, and when the interworking network element is running, the processor executes the computer-executable instructions stored in the memory, so that the interworking network element executes the instructions in claims 13 to 16. The method of any one.
A processing device, characterized in that it includes:

memory for storing computer programs;

a processor for invoking and running the computer program from the memory to perform any one of claims 1 to 7, or any one of claims 8 to 12, or any one of claims 13 to 16 method described in item.
A processor, characterized by being configured to execute the method according to any one of claims 1 to 7, or any one of claims 8 to 12, or any one of claims 13 to 16.
A chip system, characterized in that it includes:

memory for storing computer programs;

A processor for invoking and running the computer program from the memory, so that the device on which the chip system is installed executes any one of claims 1 to 7, or any one of claims 8 to 12, or The method of any one of claims 13 to 16.
A computer readable storage medium comprising a computer program which, when run on a computer, causes the computer to perform any one of claims 1 to 7, or any one of claims 8 to 12, or claims The method of any one of 13 to 16.
A computer program product comprising a computer program that, when the computer program is run on a computer, causes the computer to perform any one of claims 1 to 7 or any one of claims 8 to 12 , or the method of any one of claims 13 to 16.