CN114071639A

CN114071639A - Network access method, communication system and communication device

Info

Publication number: CN114071639A
Application number: CN202010756365.2A
Authority: CN
Inventors: 舒林
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2022-02-18
Also published as: WO2022022347A1

Abstract

The application provides a method for accessing a network, a communication system and a communication device, wherein access type information of terminal equipment is received by a mobile management network element in a first network, so that the mobile management network element can perform access control on the terminal equipment according to the access type of the terminal equipment, which is indicated by the access type information, accessing the first network. For example, the type is non-3GPP access or SNPN access through PLMN, or the access type is non-3GPP access or PLMN access through SNPN.

Description

Network access method, communication system and communication device

Technical Field

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

Background

The fifth generation (5G) networks defined by the third generation partnership project (3 GPP) support multiple access types. The terminal equipment supporting multiple access types can select one of the access types to access a 5G core network (5G core, 5GCN) according to the configuration, and can also select multiple access types to access the 5GCN simultaneously. The operator can perform access control for different access types based on own network configuration and user subscription permission, allow the terminal device to access from a specific access type, and reject the terminal device to access from other access types.

The 3GPP supports the deployment of non-public networks (NPN). NPN is also known as private network, which is distinguished from a conventional cellular network. The NPN allows some terminal devices with specific rights to access. The separately deployed NPN is called a stand alone non-public networks (SNPN). The current SNPN 5GCN supported access types include: the SNPN is accessed by a 3GPP access and a Public Land Mobile Network (PLMN), the former is direct access, and the latter is indirect access. In addition, the SNPN may also support non-3GPP access (non-3GPP access) direct access.

Because of the introduction of SNPN, the access types supported by the 5GCN of the 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 a direct 3GPP access from a direct non-3GPP access. But cannot distinguish between two access types accessed through non-3 GPP: direct access through non-3GPP access and indirect access through SNPN access to PLMN or SNPN access through PLMN.

Disclosure of Invention

The application provides a network access method, a communication system and a communication device, so that a mobile management network element in a first network can acquire an access type of a terminal device accessing the first network, and thus access control can be performed on the terminal device.

In a first aspect, a method for accessing a network is provided, including: a mobile management network element in a first network receives access type information of terminal equipment, wherein the access type information indicates an access type of the terminal equipment accessing the first network; and the mobile management network element performs access control on the terminal equipment according to the access type information.

Optionally, the access type is that the first network is accessed 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.

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

Optionally, the access type is a non-third generation mobile partnership project 3GPP (non-3GPP) access.

According to the network access method provided by the application, the mobile management network element can acquire the access type of the terminal equipment accessing the first network according to the access type information, so that access control can be performed on the terminal equipment. For example, if the first network is an SNPN, the mobility management element may 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 a PLMN, so as to perform access control on access of a corresponding type. For another example, if the first network is a PLMN, the mobility management network element may determine, according to the access type information, whether the terminal device directly accesses the PLMN through non-3GPP or indirectly accesses the PLMN through SNPN, so as to perform access control on access of a corresponding type.

With reference to the first aspect, in a possible implementation manner of the first aspect, the receiving, by a mobility management network element in the first network, access type information of a terminal device includes: and the mobile management network element receives a registration request message from the terminal equipment, wherein the registration request message comprises the access type information.

Based on the scheme, the mobility management network element may determine the access type of the terminal device accessing 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 receiving, by a mobility management network element in the first network, access type information of a terminal device includes: 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.

Based on the scheme, the mobility management element may 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 element in the first network.

With reference to the first aspect, in a possible implementation manner of the first aspect, the performing, by the mobility management network element, access control on the terminal device according to the access type information includes: in a case where 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 indicating that the terminal device is not allowed to access the first network through the second network.

Based on the scheme, after receiving the cause value, the terminal device may learn that the first network cannot be accessed through the second network, so that a subsequent registration request to the first network is no longer initiated through the registered user plane of the second network, for example, the terminal device may disable (disable) the capability of accessing the first network through the second network.

With reference to the first aspect, in a possible implementation manner of the first aspect, the performing, by the mobility management network element, access control on the terminal device according to the access type information includes: in a case that the terminal device is not allowed to access the first network through the non-3GPP access, the mobility management element sends a registration reject message to the terminal device, where the registration reject message includes a cause value indicating that the terminal device is not allowed to access the first network through the non-3GPP access.

Based on the scheme, after receiving the cause value, the terminal device may learn that the first network cannot be accessed through the non-3GPP access, so that the terminal device may no longer initiate a registration request to the first network through the non-3GPP access subsequently, for example, the terminal device may disable (disable) the capability of accessing the first network through the non-3GPP access.

In a second aspect, a method for accessing a network is provided, including: the method comprises the steps that terminal equipment sends access type information of the terminal equipment to a mobile management network element in a first network, wherein the access type information indicates an access type of the terminal equipment accessing the first network; the terminal equipment receives a registration rejection message from the mobile management network element, wherein the registration rejection message comprises a reason value, and the reason value is used for indicating that the terminal equipment is not allowed to access the first network through the access type indicated by the access type information.

According to the network access method provided by the application, the mobile management network element can acquire the access type of the terminal equipment accessing the first network according to the access type information provided by the terminal equipment, so that the access control can be performed on the terminal equipment. For example, if the first network is an SNPN, the mobility management element may 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 a PLMN, so as to perform access control on an access of a corresponding type, such as rejecting the terminal device from accessing 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: and the terminal equipment sends a registration request message to the mobile management network element through the second network, wherein the registration request message comprises the access type information.

Based on the scheme, 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 implementations of the second aspect, the sending, by the terminal device, the access type information to the mobility management network element includes: and the terminal equipment sends a registration request message to the mobile management network element through the non-3GPP access, wherein the registration request message comprises the access type information.

Based on the scheme, 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 a 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 an access type of the terminal equipment corresponding to the NAS message accessing the first network; and the interworking network element sends access type information to a mobility management network element in the first network, wherein the access type information is used for indicating the access type.

Based on the scheme, the interworking network element in the first network may determine an access type of the terminal device accessing the first network according to the NAS message of the terminal device, and may send the access type to the mobility management network element, so that the mobility management network element may determine the access type of the terminal device accessing the first network. Further, the mobility management network element may 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 determining, by the interworking network element, an access type of the terminal device accessing the first network, where the access type is corresponding to the NAS message includes: if the NAS message comes from a user plane of a second network, the interworking network element determines that the access type is that the first network is accessed 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.

With reference to the third aspect, in some implementations of the third aspect, the determining, by the interworking network element, an access type of the terminal device accessing the first network, where the access type is corresponding to the NAS message includes: if the NAS message comes from the signaling connection between the terminal equipment and the interworking network element, the interworking network element determines that the access type is non-third generation mobile partnership project (3 GPP) access.

Based on the above scheme, the interworking network element may determine the access type of the terminal device accessing the first network according to whether the NAS message of the terminal device is 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, there is provided a communication system comprising: 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, where the access type information indicates an access type of the terminal device accessing the first network; the mobility management network element is configured to receive the access type information from the terminal device; and performing access control on the terminal equipment according to the access type information.

According to the communication system provided by the application, the mobile management network element in the first network can acquire the access type of the terminal equipment accessing the first network according to the access type information provided by the terminal equipment, so that the access control can be performed on the terminal equipment. For example, if the first network is an SNPN, the mobility management element may 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 as to perform access control on an access of a corresponding type.

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 registration rejection message including a cause value indicating that the terminal device is not allowed to access the first network via the access type.

With reference to the fourth aspect, in some implementations of the fourth aspect, the access type is that the first network is accessed 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.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the access type is a non-third generation mobile partnership project 3GPP access.

In a fifth aspect, a communication system is provided, which includes: 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 an access type of the terminal device accessing the first network; the mobility management network element is configured to receive the access type information from the interworking network element; and performing access control on the terminal equipment according to the access type information.

According to the communication system provided by the application, the mobile management network element in the first network can acquire the access type of the terminal equipment accessing the first network according to the access type information provided by the interworking network element, so that the access control can be performed on the terminal equipment. For example, if the first network is an SNPN, the mobility management element may 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 as to perform access control on an access of a corresponding type.

With reference to the fifth aspect, in some implementations of the fifth aspect, the interworking network element is further configured to: receiving a non-access stratum (NAS) message from terminal equipment; and determining the access type of the terminal equipment corresponding to the NAS message.

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 registration rejection message including a cause value indicating that the terminal device is not allowed to access the first network via the access type.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the access type is that the first network is accessed 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.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the access type is a non-third generation mobile partnership project 3GPP access.

In a sixth aspect, a communication device is provided, which includes various means or units for performing the method in any one of the possible implementations of the first to third aspects or the first to third aspects.

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

In an eighth aspect, a processor is provided, comprising: input circuit, output circuit and 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 any one of the possible implementations of the first to third aspects or the first to third aspects.

In a specific implementation process, the 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, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.

In a ninth aspect, a processing apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory, and may receive a signal via the receiver and transmit a signal via the transmitter to perform the method of any one of the possible implementations of the first to third aspects or the first to third aspects.

Optionally, the number of the processors is one or more, and the number of the memories is one or more.

Alternatively, the memory may be integral to the processor or provided separately from the processor.

In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

The processing device in the above ninth aspect may be a chip, the processor may be implemented by hardware or may be implemented by software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.

In a tenth aspect, there is provided a computer program product comprising: a computer program (which may also be referred to as code, or instructions), which when executed, causes a computer to perform the method of any of the possible implementations of the first to third aspects or the first to third aspects described above.

In an eleventh aspect, a computer-readable medium is provided, which stores a computer program (which may also be referred to as code or instructions) that, when executed on a computer, causes the computer to perform the method of any one of the possible implementations of the first to third aspects or the first to third aspects.

In a twelfth aspect, there is provided a communication system comprising 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.

Drawings

Fig. 1 is a schematic diagram of a communication system provided in the present application.

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

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

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

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

Fig. 6 is a schematic flow chart of a method for accessing a network provided by the present application.

Fig. 7 is a schematic flow chart of a specific example of a method for accessing a network as provided.

Fig. 8 is a schematic flow chart of a specific example of a method for accessing a network as provided.

Fig. 9 is a schematic flow chart of a specific example of a method for accessing a network as provided.

Fig. 10 is a schematic flow chart of a specific example of a method for accessing a network as provided.

Fig. 11 is a schematic block diagram of a communication device as provided.

Fig. 12 is a schematic block diagram of another communication device provided in the application.

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

Detailed Description

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

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, a LTE Frequency Division Duplex (FDD) system, a LTE Time Division Duplex (TDD), a fifth generation (5G) system, a New Radio (NR) or other communication systems that may appear in the future, and the like.

The network elements or devices to which the present application mainly relates include:

(1) the terminal equipment: may refer to a User Equipment (UE), an access terminal, a terminal in V2X communication, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a terminal device, a wireless communication device, a user agent, or a 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 handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which are not limited in this embodiment. The terminal may also include a V2X device, such as a vehicle or an On Board Unit (OBU) in a vehicle.

(2) A mobility management network element: access and mobility management control are mainly performed.

(3) The intercommunication network element: interworking between different networks can be achieved. For example, interworking of a core network of a non-public network and a public network may be implemented. For another example, interworking between the non-3GPP access network and the core network of the non-public network, or interworking between the non-3GPP access network and the core network of the public network may be implemented.

The present application provides a communication system, which is described below with reference to fig. 1, respectively.

Fig. 1 is a schematic diagram of another communication system provided herein. The system 200 may include a mobility management element 210 in a first network and an interworking 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 an access type of the terminal device 230 accessing the first network;

the mobility management element 210 is configured to receive the access type information from the interworking element 220; and performing 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; determining 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, the registration rejection message including a cause value indicating that the terminal device 230 is not allowed to access the first network via the access type.

Optionally, the access type is that a first network is accessed through a second network, wherein the first network is a non-public network, and the second network is a public network; alternatively, 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-3 GPP.

According to the communication system provided by the application, the mobile management network element in the first network can acquire the access type of the terminal equipment accessing the first network according to the access type information provided by the interworking network element, so that the access control can be performed on the terminal equipment. For example, if the first network is an NPN, the mobility management element may 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 as to perform access control on an access of a corresponding type.

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

It should also be understood that the mobility management element, the interworking element, etc. are only names, and the names do not limit the device itself. In 5G networks and other networks in the future, the network elements may also be named otherwise. In addition, the system shown in fig. 1 may further include other network elements interacting or communicating 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, and the embodiment of the present application is not particularly limited thereto. When any one of the above systems is implemented by a 5G system, the terminal device, the mobility management element, and the interworking element in the above system may respectively correspond to the UE, the AMF, and the N3IWF in the 5G system.

The system architecture applied in the present application is described below with reference to fig. 2 and 3 by taking a 5G system as an example.

A brief description of the network elements referred to in fig. 2 and 3 will first be given.

(1) Radio Access Network (RAN): including but not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (Node B, NB), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (home evolved NodeB, or home Node B, HNB), baseband unit (base band unit, BBU), Access Point (AP) in wireless fidelity (WIFI) system, wireless relay Node, wireless backhaul Node, Transmission Point (TP), or transmission and reception point (TP), etc., and may also be a fifth generation (TRP) system, for example, a gbb or TP in a new radio, NR), or a group of antennas may also constitute a network panel or a multiple-panel TRP system, or a network panel may constitute a network panel or a group of antennas including a network Node (NB), for example, a baseband unit (BBU) or a Distributed Unit (DU) may be used.

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

(3) Session Management Function (SMF): the session management and Policy Control Function (PCF) mainly performs functions such as execution of a policy control, selection of a UPF, and allocation of a UE IP address.

(4) User Plane Function (UPF): routing and transmission of data packets, packet detection, service usage reporting, QoS processing, lawful interception, uplink packet detection, downlink data packet storage and other user plane related functions.

(5) Data Network (DN): an operator network providing data transmission services for users, such as an IP Multimedia Service (IMS), the internet, etc.

(6) N3 interface interoperability function (N3 inter-working function, N3 IWF): interworking between different networks can be achieved. For example, interworking of a core network of a non-public network and a public network may be implemented. For another example, interworking between the non-3GPP access network and the core network of the non-public network, or interworking between the non-3GPP access network and the core network of the public network may be implemented.

Fig. 2 and 3 each show a system architecture diagram. In fig. 2 and 3, the NPN (SNPN is taken as an example in fig. 2 and 3) and the PLMN have independent Radio Access Network (RAN) and Core Network (CN). The core network of SNPN and PLMN is connected by N3IWF, and the intercommunication of user plane and control plane can be carried out by N3 IWF.

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

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

It should be understood that each network element shown in fig. 2 and 3 may be a hardware device, a chip, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). It should also be understood that some network elements shown in fig. 2 and fig. 3 may be deployed at the same location (e.g., on the same hardware device or software function) or may be separately deployed, 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 only an example, and the interfaces between the network elements in different communication systems or along with the evolution of the systems may also be different from those shown in the figures, and are not limited herein.

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

Referring to fig. 4, the UE accessing SNPN internally includes an SNPN non-access stratum NAS and an SNPN Access Stratum (AS), and the SNPN NAS is above the SNPN AS. The SNPN AS includes two: SNPN 3GPP AS and SNPN non-3GPP (non-3GPP) AS. SNPN 3GPP AS supports 3GPP access, including NR and the like. The SNPN 3GPP AS includes a Service Data Adaptation Protocol (SDAP) layer and a Radio Resource Control (RRC) layer. SNPN 3GPP AS supports UE to directly access SNPN through 3GPP access. Since the UE supports indirect access to SNPN via PLMN, the SNPN NAS of the UE sees the PLMN NAS AS an integral part of the SNPN non-3GPP AS, so that the SNPN non-3GPP AS comprises the PLMN NAS and the SNPN non-3GPP AS sub-layers, wherein the SNPN non-3GPP AS sub-layer further comprises a management entity and non-3GPP access (such AS 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 the non-3GPP access.

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

Referring to fig. 5, the UE accessing the PLMN includes a PLMN NAS and a PLMN AS inside, and the PLMN NAS is above the PLMN AS. The PLMN AS includes two: PLMN 3GPP AS and PLMN non-3GPP (non-3GPP) AS. PLMN 3GPP AS supports 3GPP access including NR etc. The PLMN 3GPP AS includes an SDAP layer and an RRC layer. PLMN 3GPP AS supports direct access of UEs to the PLMN through 3GPP access. Since the UE supports indirect access to the PLMN via SNPN, the PLMN NAS of the UE sees SNPN NAS AS an integral part of the PLMN non-3GPP AS, so that the PLMN non-3GPP AS comprises SNPN NAS and PLMN non-3GPP AS sub-layers, wherein the PLMN non-3GPP AS sub-layer further comprises a management entity and non-3GPP access (for example: WiFi). The SNPN NAS supports the UE to be indirectly accessed to the PLMN through the SNPN, and the PLMN non-3GPPAS sublayer supports the UE to be directly accessed to the PLMN through the non-3 GPP.

The following describes a method for accessing a network provided by the present application.

Fig. 6 is a schematic flow chart 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 explained below.

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

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

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

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

Herein, the public network may be a PLMN; the non-public network may be SNPN or public network integrated NPN (PNI-NPN).

Accessing PLMN (access PLMN via SNPN) via SNPN may also be referred to as: access to PLMN services (access to PLMN services a SNPN or to access PLMN services a SNPN) through SNPN. Accessing PLMN services through SNPN means: the UE connects to the core network of the PLMN through 3GPP access using SNPN to obtain PLMN service (A UE is accessing PLMN service a SNPN where the UE is connecting to the 5GCN of the PLMN using the 3GPP access of the SNPN).

Accessing SNPN (access SNPN via PLMN) may also be referred to as: the SNPN service (access to SNPN service via PLMN or to access SNPN service via PLMN) is accessed through the PLMN. Accessing the SNPN service through the PLMN means: the UE connects to the core network of SNPN by using the 3GPP access of PLMN to obtain SNPN service (A UE is accessing SNPN services a PLMN where 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: and the UE accesses the core network of the PLMN or SNPN through the access layer connection with the N3 IWF. The access layer connection between the UE and the N3IWF is untrusted non-3GPP access (untrusted non-3GPP access), for example: wireless Fidelity (WiFi). This access type is distinguished from a core network in which the UE accesses the PLMN or SNPN through an access layer connection with a radio access network RAN, which is a 3GPP access (3GPP access), for example: NR in 5G systems.

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

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

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

Specifically, the terminal device may send an NAS message to an interworking network element in the first network, and the interworking network element may determine an 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.

And S520, the mobile management network element performs access control on the terminal equipment 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 element may send a registration reject message to the terminal device, where the registration reject message includes a cause value indicating 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, where the registration accept message indicates that the terminal device is allowed to access the first network through the access type indicated by the access type information.

According to the network access method provided by the application, the mobile management network element can acquire the access type of the terminal equipment accessing the first network according to the access type information, so that access control can be performed on the terminal equipment.

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

It should be noted that, for the convenience of understanding, the following description will be given by taking the naming of the network element in the 5G network as an example, and taking the public network as PLMN and the non-public network as SNPN as an example.

The first network is SNPN

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

This is explained in connection with the flow chart shown in fig. 7.

Referring to fig. 7, fig. 7 is a schematic flow chart of a method for accessing a network provided in the present application. The method 600 may be applied in the network shown in fig. 2.

S601, the UE transmits a registration request message #1 to the AMF in the SNPN through the PLMN. Accordingly, the AMF receives the registration request message #1 transmitted 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, which indicates that the access type is SNPN accessed through a PLMN, i.e., access SNPN via PLMN.

It is understood that the registration request message #1 is encapsulated as a NAS PDU, and may be sent to the N3IWF in the SNPN via the user plane (e.g., UPF) of the PLMN, and further sent to the AMF by the N3 IWF.

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, does not allow the access SNPN via PLMN, the AMF performs:

s603a, the AMF sends a registration reject message #1 (i.e., an example of a registration reject message) to the UE. Accordingly, the UE receives the registration reject message #1 from the AMF.

The registration reject message #1 includes a cause value indicating that the UE is not allowed to access the SNPN through the PLMN, i.e., rejects the access SNPN via PLMN. For example, the cause value is: access to SNPN is not allowed through PLMN (access SNPN via PLMN not allowed).

After receiving the cause value, the UE may learn that the SNPN cannot be accessed through the PLMN, so that a registration request to the SNPN is not initiated through the user plane of the registered PLMN any more subsequently, for example, the UE may disable (disable) the ability to access the SNPN through the PLMN.

For another example, if the UE is allowed to access the SNPN through the PLMN, i.e., access SNPN via PLMN is allowed, the AMF may perform:

s603b, the AMF transmits a registration accept message #1 (i.e., an example of a registration accept message) to the UE. Accordingly, the UE receives the registration accept message #1 from the AMF.

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

S604, the UE transmits a registration request message #2 to the AMF through the non-3GPP access. Accordingly, the AMF receives the registration request message #2 transmitted by the UE.

If the UE currently accesses the SNPN directly through non-3GPP access (e.g., wifi), the UE may send a registration request message #2 to the AMF in the SNPN, where the registration request message includes access type information #2, and the access type information #2 indicates that the access type is non-3GPP access (non-3GPP access).

Wherein the registration request message may be sent to the N3IWF in SNPN over an access stratum Nwu connection between the UE and the N3IWF, which is further sent by the N3IWF to the AMF.

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, is not allowed to directly access the SNPN through non-3GPP access, the AMF performs:

s606a, the AMF sends a registration reject message #2 (i.e., another example of the registration reject message) to the UE. Accordingly, the UE receives the registration reject message #2 from the AMF.

The registration reject message #2 may include a cause value indicating that the UE is not allowed to directly access the SNPN through non-3GPP access, i.e., reject direct access of the SNPN through non-3GPP access. For example, the cause value is specifically: non-3GPP access not allowed (non-3GPP access not allowed).

After receiving the reason, the UE may know that the SNPN cannot be directly accessed through the non-3GPP access, so that the UE does not initiate a registration request to the SNPN through the non-3GPP access any more subsequently, for example, the UE may prohibit the access capability of directly accessing the SNPN through the non-3GPP access.

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

s606b, the AMF sends a registration accept message #2 (i.e., another example of the registration accept 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, i.e., allow direct access to the SNPN through non-3GPP access.

According to the method for accessing the network provided by the application, the UE can select to directly access the SNPN through non-3GPP access or indirectly access the SNPN through PLMN, or simultaneously access the SNPN based on the capability and configuration of the UE. When a registration request of the SNPN core network is initiated through the selected access type, the UE can carry corresponding access type information to the SNPN core network, so that the SNPN core network can identify the access type of the registration request initiated by the current UE according to the access type information carried by the UE, different access type controls can be executed according to network configuration and subscription information of users, the access control requirements of operators for different access types are met, and the network operation efficiency is improved.

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

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

This is explained in connection with the flow chart shown in fig. 8.

Referring to fig. 8, fig. 8 is a schematic flow chart of a method for accessing a network provided in the present application. The method 700 is explained below.

S701, the UE transmits NAS message #1 to N3IWF in 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 NAS message #1 (i.e., an example of the NAS message) to N3IWF in the SNPN through a user plane (e.g., UPF) in the PLMN. Illustratively, the NAS message #1 may be a registration request message.

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

If the N3IWF receives the NAS message #1 through the user plane, it may determine that the access type of the UE accessing the first network corresponding to the NAS message #1 is accessing 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 (i.e., an example of access type information) from the N3 IWF.

Wherein the access type information #1 is used to indicate the access type, i.e. accessing SNPN through PLMN.

Alternatively, the N3IWF may carry the access type information #1 through an interface message (e.g., 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, access SNPN via PLMN is not allowed, the AMF performs:

s705a, the AMF sends a registration reject message #1 (i.e., an example of a registration reject message) to the UE. Accordingly, the UE receives the registration reject message #1 from the AMF.

Step S705a is the same as S603a, and reference may be made to S603 a.

s705b, the AMF transmits a registration accept message #1 (i.e., an example of a registration accept message) to the UE. Accordingly, the UE receives the registration accept message #1 from the AMF.

Step S705b is the same as S603b, and reference may be made to S603 b.

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

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

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

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

S708, the N3IWF transmits access type information #2 (i.e., another example of the access type information) to the AMF in the SNPN. Accordingly, the AMF receives access type information from the N3 IWF.

Wherein the access type information #2 is used to indicate the access type, i.e. non-3GPP access.

Alternatively, the N3IWF may carry the access type information #2 through an interface message (e.g., 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 managing network element sends a registration reject message #2 (i.e., another example of a registration reject message) to the UE. Accordingly, the UE receives the registration reject message #2 from the AMF.

Step S710a is the same as S606a, and reference may be made to S606 a.

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

s710b, the AMF sends a registration accept message #2 (i.e., another example of the registration accept message) to the UE. Accordingly, the UE receives the registration accept message #2 from the AMF.

Step S710b is the same as S606b, and reference may be made to S606 b.

According to the method for accessing the network, the N3IWF determines the currently selected access type of the UE according to whether the received NAS message sent by the UE comes from a user plane or is in signaling connection, and then sends the access type information of the determined access type to the SNPN, 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, thereby executing different access type control according to network configuration and subscription information of the user, realizing the access control requirements of an operator for different access types, and improving the network operation efficiency.

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

The second and first networks are PLMN

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

This is explained in connection with the flowchart shown in fig. 9.

Referring to fig. 9, fig. 9 is a schematic flow chart of a method for accessing a network provided in the present application. The method 900 may be applied to the network architecture shown in fig. 3.

S901, the UE transmits a registration request message #3 to the AMF in the PLMN through SNPN. Accordingly, the AMF receives the registration request message #3 transmitted by the UE.

Specifically, if the UE currently accesses the PLMN through 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, which indicates that the access type is access to the PLMN through SNPN, i.e., access PLMN via SNPN, for example.

It is understood that the registration request message #3 is encapsulated as a NAS PDU, and may be sent to the N3IWF in the PLMN via the SNPN user plane (e.g., UPF), and further sent to the AMF by the N3 IWF.

It should be understood that the registration request message #3 may also be transmitted to the N3IWF in the PLMN through the SNPN control plane, 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 SNPN, i.e. access PLMN via SNPN is not allowed, the AMF performs:

at S903a, the AMF transmits a registration reject message #3 (i.e., an example of a registration reject message) to the UE. Accordingly, the UE receives the registration reject message #3 from the AMF.

The registration reject message #3 includes a cause value indicating that the UE is not allowed to access the PLMN through the SNPN, i.e., rejects the access PLMN via SNPN. For example, the cause value is specifically: access to PLMN via SNPN is not allowed (access PLMN via SNPN not allowed).

After receiving the reason, the UE may know that the PLMN cannot be accessed through the SNPN, so that a registration request to the PLMN is not initiated through the registered SNPN user plane any more subsequently, for example, the UE may prohibit accessing the PLMN through the SNPN.

As another example, if the UE is allowed to access the PLMN through SNPN, i.e., access PLMN via SNPN is allowed, the AMF may perform:

at S903b, the AMF transmits a registration accept message #3 (i.e., an example of a registration accept message) to the UE. Accordingly, the UE receives the registration accept message #3 from the AMF.

The registration accept message #3 is used to indicate that the UE is allowed to access the PLMN through the SNPN, i.e., allow access to the PLMN through the access PLMN via SNPN.

S904, the UE transmits a registration request message #4 to the AMF through the non-3GPP access. Accordingly, the AMF receives the registration request message #4 transmitted by the UE.

If the UE currently accesses the PLMN directly through the non-3GPP access, the UE may send a registration request message #4 to the AMF in the PLMN, where 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).

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

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, is not allowed to directly access the PLMN through non-3GPP access, the AMF performs:

s906a, the AMF sends a registration reject message #4 (i.e., another example of the registration reject message) to the UE. Accordingly, the UE receives the registration reject message #4 from the AMF.

The registration reject message #4 includes a cause value indicating that the UE is not allowed to directly access the PLMN through non-3GPP access, i.e., rejects direct access to the PLMN through non-3GPP access. For example, the cause value is specifically: non-3GPP access not allowed (non-3GPP access not allowed).

After receiving the reason, the UE may know that the PLMN cannot be directly accessed through the non-3GPP access, so that the UE does not initiate a registration request to the PLMN any more subsequently through the non-3GPP access, for example, the UE may prohibit the access capability of directly accessing the PLMN through the non-3GPP access.

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

s906b, the AMF sends a registration accept message #4 (i.e., another example of the registration accept message) to the UE. Accordingly, the UE receives the registration accept message #4 from the AMF.

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

According to the method for accessing the network provided by the application, the UE can select to directly access the PLMN through non-3GPP access or indirectly access the PLMN through SNPN or access the PLMN at the same time based on the capability and configuration of the UE. When a registration request of a core network of a PLMN is initiated through a selected access type, the UE can carry corresponding access type information to the core network of the PLMN, so that the core network of the PLMN can identify the access type of the registration request initiated by the current UE according to the access type information carried by the UE, different access type controls can be executed according to network configuration and subscription information of users, access control requirements of operators for different access types are met, and network operation efficiency is improved.

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 both steps. For example, if the UE supports accessing the PLMN through 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 the PLMN access through SNPN and the direct PLMN access through non-3GPP access, S901 and S904 may be performed, or only one of them may be performed.

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

This is explained in connection with the flowchart shown in fig. 10.

Referring to fig. 10, fig. 10 is a schematic flow chart of a method for accessing a network provided in the present application. The method 1000 is explained below.

S1001, the UE transmits 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 NAS message #3 (i.e., an example of the NAS message) to the N3IWF in the PLMN through the user plane in the SNPN. Illustratively, the NAS message #3 may be a registration request message.

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

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

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

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

Alternatively, the N3IWF may carry the access type information #3 through an interface message (e.g., 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 transmits a registration reject message #3 (i.e., an example of a registration reject message) to the UE. Accordingly, the UE receives the registration reject message #3 from the AMF.

Step S1005a is the same as S903a, and reference may be made specifically to S903 a.

s1005b, the AMF transmits a registration accept message #3 (i.e., an example of a registration accept message) to the UE. Accordingly, the UE receives the registration accept message #3 from the AMF.

Step S1005b is the same as S903b, and reference may be made specifically to S903 b.

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

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

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

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

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

Wherein the access type information #4 is used to indicate the access type, i.e. non-3GPP access.

Alternatively, the N3IWF may carry the access type information #4 through an interface message (e.g., 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 managing network element sends a registration reject message #4 (i.e., another example of a registration reject message) to the UE. Accordingly, the UE receives the registration reject message #4 from the AMF.

Step S1010a is the same as S906a, and reference may be made to S906 a.

s1010b, the AMF sends a registration accept message #4 (i.e., another example of the registration accept message) to the UE. Accordingly, the UE receives the registration accept message #4 from the AMF.

Step S1010b is the same as S906b, and reference may be made to S906 b.

According to the method for accessing the network, the N3IWF determines the currently selected access type of the UE according to whether the received NAS message sent by the UE comes from the user plane or is in signaling connection, and then the N3IWF can send the access type information of the determined access type to the PLMN, so that 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, different access type controls can be executed according to network configuration and subscription information of the user, the access control requirements of an operator for different access types are met, and the network operation efficiency is improved.

It should be noted that, based on the capability and configuration of the UE, the UE may perform only one or both of steps S1001 and S1006. For example, if the UE supports access to the PLMN through 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 the access to the PLMN through SNPN and the direct access to the PLMN through non-3GPP access, S1001 and S1006 may be performed, or only one of them may be performed.

It should be understood that the various aspects of the embodiments of the present application can be reasonably combined and explained, and the explanation or explanation of the various terms appearing in the embodiments can be mutually referred to or explained in the various embodiments, which is not limited.

It should also be understood that, in the various embodiments of the present application, the size of the serial number of each process described above does not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic of each process. The various numbers or serial numbers involved in the above processes are merely used for convenience of description and should not be construed as limiting the implementation processes of the embodiments of the present application in any way.

The method provided by the embodiment of the present application is described in detail above with reference to fig. 6 to 10. Hereinafter, the apparatus provided in the embodiment of the present application will be described in detail with reference to fig. 11 to 13.

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

The transceiving unit 2010 may be configured to transmit information to other apparatuses or receive information from other apparatuses. The processing unit 2020 may be used for internal processing of the device.

In one implementation, the communication device 2000 corresponds to a mobility management network element (e.g., an AMF in a PLMN or SNPN) in the first network in the above method embodiment. The communication apparatus 2000 may be a mobility management element in the first network or a chip configured in the mobility management element in the first network, and may include a unit for performing an operation performed by the mobility management element in the first network.

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

Optionally, the access type is a non-third generation mobile partnership project 3GPP access.

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

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

Optionally, the receiving unit is specifically configured to: in a case where the terminal device is not allowed to access the first network via the second network, sending a registration reject message to the terminal device, the registration reject message including a cause value indicating that the terminal device is not allowed to access the first network via the second network.

Optionally, the receiving unit is specifically configured to: in a case where the terminal device is not allowed to access the first network via the non-3GPP access, sending a registration reject message to the terminal device, the registration reject message including a cause value indicating that the terminal device is not allowed to access the first network via the non-3GPP access.

In another implementation, the communication apparatus 2000 corresponds to a terminal device (e.g., UE) in the above method embodiment. The communication apparatus 2000 may be a terminal device or a chip configured in the terminal device, and may include a unit for performing an operation performed by the terminal device.

A transceiving unit 2010, configured to send access type information of the communication apparatus 2000 to a mobility management network element in a first network, where the access type information indicates an access type of the communication apparatus 2000 accessing the first network; the transceiving unit 2010 is further configured to receive a registration reject message from the mobility management element, where the registration reject message includes a cause value indicating that the communication apparatus 2000 is not allowed to access the first network through the access type indicated by the access type information.

Optionally, the transceiving unit 2010 is specifically configured to: and sending a registration request message to the mobility management network element through the second network, wherein the registration request message comprises the access type information.

Optionally, the transceiving unit 2010 is specifically configured to: and sending a registration request message to the mobility management network element through the non-3GPP access, wherein the registration request message comprises the access type information.

In yet another implementation, the communication apparatus 2000 corresponds to an interworking network element in the first network (e.g., N3IWF in PLMN or SNPN) in the above-described 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 an operation performed by the interworking network element in the first network.

Specifically, the transceiving unit 2010 is configured to receive a non-access stratum NAS message from a terminal device; a processing unit 2020, configured to determine an access type, to which the terminal device accesses the first network, corresponding to the NAS message; the transceiving 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 is from a user plane of a second network, determining that the access type is to access 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.

Optionally, the processing unit 2020 is specifically configured to: if the NAS message received by the receiving unit is from the signaling connection between the terminal device and the communication apparatus 2000, it is determined that the access type is the non-third generation partnership project 3GPP access.

Optionally, the NAS message is a registration request message.

It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

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 transceiving unit 2010 in the communication device 2000 may correspond to the communication interface 3200 in the communication device 3000 shown in fig. 12, and the processing unit 2020 in the communication device 2000 may correspond to the processor 3100 in the communication device 3000 shown in fig. 12. When the communication apparatus 2000 corresponds to a terminal device, the transceiver 2010 in the communication apparatus 2000 may correspond to the transceiver 4010 in the terminal device 4000 shown in fig. 13, and the processing unit 2020 in the communication apparatus 2000 may correspond to the processor 4001 or the processing apparatus 4004 in the terminal device 4000 shown in fig. 13.

Fig. 12 shows a schematic block diagram of another communication device 3000 provided herein. 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, may be implemented by the communication apparatus shown in fig. 12.

It is understood that the communication apparatus 3000 may be a physical device, a component (e.g., an integrated circuit, a chip, etc.) of the physical device, or a functional module in the physical device.

As shown in fig. 12, the communication device 3000 includes: one or more processors 3100. Processor 3100 may store execution instructions for performing the methods of embodiments of the application. Optionally, communication interface 3200 may be invoked in processor 3100 to implement receive and transmit functionality. The communication interface 3200 may be a logical interface or a physical interface, which is not limited in this respect. For example, communication interface 3200 may be a transceiver circuit, an interface circuit, a transceiver, or a transceiver circuit for performing receive and transmit functions, among others. The transmit and receive functions of communication interface 3200 may be separate or integrated. The transceiver circuit or the interface circuit may be used for reading and writing code/data, or the transceiver circuit or the interface circuit may be used for transmitting or transferring signals.

Optionally, the communication device 3000 may further include a memory 3300. The embodiment of the present application does not specifically limit the specific deployment location of the memory 3300, and the memory 3300 may be integrated into the processor 3100 or may be independent from the processor 3100. For the case where the communication device 3000 does not include a memory, the communication device 3000 may have a processing function, and the memory may be disposed in other locations (e.g., a cloud system).

Processor 3100, memory 3300, and communication interface 3200 communicate among themselves via internal connection paths that carry control and/or data signals.

It is understood that although not shown, the communication device 3000 may also include other devices, such as an input device, an output device, a battery, etc.

Optionally, in some embodiments, the memory 3300 may store execution instructions for performing the methods of embodiments of the present application. Processor 3100 can execute instructions stored in memory 3300 in combination with other hardware (e.g., communication interface 3200) to perform the steps of the method described below, and the specific operations and advantages can be found in the description of the method embodiments above.

The method disclosed by the embodiment of the present application can be applied to the memory 3300, or implemented by the memory 3300. The memory 3300 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The 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 (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. 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 connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a Random Access Memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM, an electrically erasable programmable memory, a register, or other storage media that are well known in the art. The storage medium is located in a memory, and a processor reads instructions in the memory and combines hardware thereof to complete the steps of the method.

It will be appreciated that the memory 3300 can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory ROM, a programmable read-only memory (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. Volatile memory can be random access memory, RAM, which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 13 is a schematic structural diagram of a terminal device 4000 according to an embodiment of the present application. As shown, the terminal device 4000 includes a processor 4001 and a transceiver 4002. Optionally, the terminal device 4000 may further include a memory 4003. The processor 4001, the transceiver 4002 and the memory 4003 can communicate with each other via an internal connection path to transmit control and/or data signals, the memory 4003 is used for storing a computer program, and the processor 4001 is used for calling and running the computer program from the memory 4003 to control the transceiver 4002 to transmit and receive signals.

The processor 4001 and the memory 4003 may be combined into a processing means 4004, and the processor 4001 is configured to execute the program code stored in the memory 4003 to implement the functions of the terminal device in the above method embodiments. It should be understood that the processing device 4004 shown in the figures is merely an example. In a specific implementation, the memory 4003 may also be integrated into the processor 4001 or separate from the processor 4001. This is not limited in this application.

The terminal device 4000 may further include an antenna 4010, configured to send uplink data or uplink control signaling output by the transceiver 4002 through a wireless signal.

It should be understood that the terminal device 4000 shown in fig. 13 can implement the respective processes relating to the terminal device in the foregoing method embodiments. The operations or functions of the modules in the terminal device 4000 are respectively for implementing the corresponding flows in the above method embodiments. Reference may be made specifically to the description of the above method embodiments, and a detailed description is appropriately omitted herein to avoid redundancy.

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

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

It is to be understood that the processing means 4004 or the processor 4001 may be one 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 (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a Central Processing Unit (CPU), a network processor (network processor, NP), a Digital Signal Processor (DSP), a microcontroller (micro controller unit, MCU), a Programmable Logic Device (PLD), or other integrated chip. 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 connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

The memory 4003 may be any of the forms of memory described above and will not be described in detail herein.

The present application further provides a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the method of any of the preceding method embodiments, the method on the side of the terminal device, the side of the mobility management element in the first network, or the side of the interworking element in the first network.

The present application also provides a computer-readable medium storing a program code, which, when running on a computer, causes the computer to execute the method of the foregoing method embodiment on the side of the terminal device, the side of the mobility management element in the first network, or the side of the interworking element in the first network.

The present application also provides a system comprising one or more of the following: the mobile management network element comprises terminal equipment, a mobile management network element in a first network and an intercommunication network element in the first network.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

The network device in the foregoing device embodiments completely corresponds to the terminal device and the network device or the terminal device in the method embodiments, and the corresponding module or unit executes the corresponding steps, for example, the communication unit (transceiver) executes the steps of receiving or transmitting in the method embodiments, and other steps besides transmitting and receiving may be executed by the processing unit (processor). The functions of the specific elements may be referred to in the respective method embodiments. The number of the processors may be one or more.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on 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 can be a component. One or more components may reside within a process or thread of execution and a component may be localized on one computer and distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, or across a network such as the internet with other systems by way of the signal).

It should be appreciated that reference throughout this specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the various embodiments are not necessarily referring to the same embodiment throughout the specification. 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 embodiment of the present application, the numbers "first" and "second" … are only used for distinguishing different objects, such as for distinguishing different network devices, and do not limit the scope of the embodiment of the present application, and the embodiment of the present application is not limited thereto.

It should also be understood that, in this application, "when …", "if" and "if" all refer to a network element that performs the corresponding process under certain objective circumstances, and are not time-critical, nor do they require certain deterministic actions to be performed by the network element, nor do they imply that other limitations exist.

It is also understood that, in the present application, "at least one" means one or more, "a plurality" means two or more.

It should also be understood that in the embodiments of the present application, "B corresponding to a" means that B is associated with a, from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.

It should also be understood that the term "and/or" herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

Items appearing in this application as similar to "include one or more of the following: the meaning of the expressions A, B, and C "generally means that the item may be any of the following, unless otherwise specified: a; b; 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 C, C and C; c, C and C, and other combinations of A, B and C. The above description is made by taking 3 elements of a, B and C as examples of optional items of the item, and when the expression "item" includes at least one of the following: a, B, … …, and X ", i.e., more elements in the expression, then the items to which the item may apply may also be obtained according to the aforementioned rules.

It is understood that, in the embodiments of the present application, a terminal device and/or a network device may perform some or all of the steps in the embodiments of the present application, and these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or various modifications of the operations. Further, the various steps may be performed in a different order presented in the embodiments of the application, and not all operations in the embodiments of the application may be performed.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for accessing a network, comprising:

a mobile management network element in a first network receives access type information of terminal equipment, wherein the access type information indicates an access type of the terminal equipment accessing the first network;

and the mobile management network element performs access control on the terminal equipment according to the access type information.

2. The method of claim 1, wherein the access type is to access 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.

3. The method of claim 1, wherein the access type is a non-third generation mobile partnership project 3GPP access.

4. The method of any of claims 1 to 3, wherein receiving access type information of a terminal device by a mobility management network element in the first network comprises:

and the mobile management network element receives a registration request message from the terminal equipment, wherein the registration request message comprises the access type information.

5. The method of any of claims 1 to 3, wherein receiving access type information of a terminal device by a 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.

6. The method of claim 2, wherein the performing, by the mobility management network element, access control on the terminal device according to the access type information comprises:

in a case where 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 indicating that the terminal device is not allowed to access the first network through the second network.

7. The method of claim 3, wherein the performing, by the mobility management network element, access control on the terminal device according to the access type information comprises:

in a case that the terminal device is not allowed to access the first network through the non-3GPP access, the mobility management element sends a registration reject message to the terminal device, where the registration reject message includes a cause value indicating that the terminal device is not allowed to access the first network through the non-3GPP access.

8. A method for accessing a network, comprising:

the method comprises the steps that terminal equipment sends access type information of the terminal equipment to a mobile management network element in a first network, wherein the access type information indicates an access type of the terminal equipment accessing the first network;

the terminal equipment receives a registration rejection message from the mobile management network element, wherein the registration rejection message comprises a reason value, and the reason value is used for indicating that the terminal equipment is not allowed to access the first network through the access type indicated by the access type information.

9. The method of claim 8, wherein the access type is to access 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.

10. The method of claim 9, wherein the terminal device sending the access type information to the mobility management element comprises:

and the terminal equipment sends a registration request message to the mobile management network element through the second network, wherein the registration request message comprises the access type information.

11. The method of claim 8, wherein the access type is a non-third generation mobile partnership project 3GPP access.

12. The method of claim 11, wherein the terminal device sending the access type information to the mobility management element comprises:

and the terminal equipment sends a registration request message to the mobile management network element through the non-3GPP access, wherein the registration request message comprises the access type information.

13. A method for accessing a network, comprising:

an interworking network element in a first network receives a non-access stratum (NAS) message from terminal equipment;

the interworking network element determines an access type of the terminal equipment corresponding to the NAS message accessing the first network;

and the interworking network element sends access type information to a mobility management network element in the first network, wherein the access type information is used for indicating the access type.

14. The method of claim 13, wherein the determining, by the interworking network element, an access type of the terminal device accessing the first network, which corresponds to the NAS message, comprises:

if the NAS message comes from a user plane of a second network, the interworking network element determines that the access type is that the first network is accessed 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.

15. The method of claim 13, wherein the determining, by the interworking network element, an access type of the terminal device accessing the first network, which corresponds to the NAS message, comprises:

if the NAS message comes from the signaling connection between the terminal equipment and the interworking network element, the interworking network element determines that the access type is non-third generation mobile partnership project (3 GPP) access.

16. The method according to any of claims 13 to 15, wherein the NAS message is a registration request message.

17. 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 an access type of the terminal device accessing the first network;

the mobility management network element is configured to receive the access type information from the interworking network element; and performing access control on the terminal equipment according to the access type information.

18. The system of claim 17, wherein the interworking network element is further configured to:

receiving a non-access stratum (NAS) message from terminal equipment;

and determining the access type of the terminal equipment corresponding to the NAS message.

19. The system according to claim 17 or 18, wherein said performing access control on said terminal device according to said access type information comprises:

sending a registration rejection message to the terminal device, the registration rejection message including a cause value indicating that the terminal device is not allowed to access the first network via the access type.

20. The system of any one of claims 17 to 19, wherein the access type is to access 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.

21. The system of any of claims 17 to 19, wherein the access type is a non-third generation mobile partnership project 3GPP access.

22. A communications apparatus, characterized in that the apparatus is configured to perform the method of any of claims 1 to 7, or any of claims 8 to 12, or any of claims 13 to 16.