CN117377030A

CN117377030A - Method for accessing network and communication device

Info

Publication number: CN117377030A
Application number: CN202211252846.5A
Authority: CN
Inventors: 马春燕; 丁辉; 宗在峰; 刘佳琦
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-06-30
Filing date: 2022-10-13
Publication date: 2024-01-09

Abstract

The application provides a method for accessing a network, which can access UE to a proper core network. And the AMF of the first core network instructs the RAN to execute rerouting under the condition that the UE is judged to be suitable for accessing the second core network, and carries instruction information in a rerouting request message, wherein the instruction information is used for the RAN to determine the second core network, so that the UE is accessed to the second core network through the target AMF of the second core network. Or, if the AMF of the first core network determines that the UE is suitable for accessing the second core network, the AMF of the first core network sends a registration rejection response message, which includes a rejection cause value or network slice information of the second core network. And the UE performs cell reselection according to the rejection cause value, or the UE reinitiates a registration process through a registration request after updating the network slice information carrying the second core network, so that the UE can access the second core network.

Description

Method for accessing network and communication device

Technical Field

The embodiment of the application relates to the technical field of wireless communication, in particular to a method for accessing a network and a communication device.

Background

In some communications scenarios, to support providing network services for both public and private network users, operators may deploy a common base station for both public and private networks to support access to the public network by the public network user through the common base station, and the private network user to access the private network through the common base station. In another scenario, the operator may also deploy independent base stations for the public network and the private network, respectively, where the public network base station supports access to the public network by the public network user, and the private network base station supports access to the private network by the private network user.

As known, in the process that a terminal device accesses a core network through AN Access Network (AN), the AN needs to perform access and mobility management function (access and mobility management function, AMF) selection first, and finally registers the terminal device to the core network through the AMF to complete access. According to current communication protocols, the AN performs the selection of AN initial AMF based mainly on public land mobile network identity (public land mobile network identifier, PLMN ID), location of User Equipment (UE), list of network slices requested by the UE, and local operator policy. However, in the above information, PLMN ID, UE location, and local operator policy cannot support AN to distinguish between public network users and private network users. In addition, the capability of the existing network UEs to support network slicing is uneven, and some UEs do not have the capability of carrying network slicing information, so that AN cannot select a correct core network for private network users and public network users, for example, a situation that the AN selects a public network AMF for park users to provide network services, or selects a private network AMF for public network users to provide network services may occur.

In addition, under the scene of adopting independent base stations for the public network and the private network, the existing cell broadcast information can not support the UE to select the correct access network, so that the UE can not access the correct network to initiate service.

In the communication scenario where the public network and the private network share a base station, or where the public network and the private network use independent base stations, there is no solution at present how to select a suitable (or correct) core network for a terminal device.

Disclosure of Invention

The application provides a method and a communication device for accessing a network, which can be used for deploying a common base station in a public network core network and a private network core network or supporting terminal equipment to be accessed into a proper core network in a communication scene that the public network core network and the private network core network are respectively deployed with independent base stations.

In a first aspect, a method of accessing a network is provided, the method comprising:

the method comprises the steps that a first AMF receives a first message from access network equipment, wherein the first message comprises a registration request of terminal equipment, and the first AMF belongs to a first core network;

the first AMF sends a rerouting request message to the access network device based on the first message, wherein the rerouting request message comprises first indication information, and the first indication information is used for indicating the access network device to reroute the registration request to the second core network;

wherein the first core network and the second core network share access network equipment.

In the technical scheme, the first core network and the second core network share the access network device, which means that the access network device can access the UE of the first core network and the UE of the second core network into the respective corresponding core networks. Or, the UE of the first core network and the UE of the second core network access the core network through the same access network device.

Based on the above technical solution, if the first AMF of the first core network receives the registration request of the UE, the first AMF informs the access network device to reroute if the first AMF determines that the UE is suitable for accessing the second core network. The first AMF carries first indication information in the rerouting request message so that the access network equipment determines to reroute the registration request of the UE to the second core network, thereby realizing the access of the UE to the proper core network.

Illustratively, one of the first core network and the second core network is a public network, and the other is a private network, without limitation. It can be seen that if the access network device selects a private network AMF for a private network user suitable for accessing a public network, or selects an AMF of a public network for a private network user suitable for accessing a private network, or under other similar communication scenarios, the technical scheme can be adopted to reroute to a correct core network.

With reference to the first aspect, in certain implementations of the first aspect, the first indication information includes one or more of:

identification of the second core network;

identification of a network slice of the second core network;

AMF set identification, AMF set identification is used for access network equipment to confirm second core network.

With reference to the first aspect, in certain implementations of the first aspect, the first message includes an identification of the terminal device, and one or more of:

The position information of the terminal equipment comprises information of a tracking area TA and/or information of a cell where the terminal equipment resides;

identification of the network slice requested by the terminal device.

In this implementation, the first message sent by the access network device to the first AMF may include, in addition to the UE identifier, location information of the UE and/or an identifier of a network slice requested by the UE. The information can be used as a reference when the first AMF decides whether the UE is suitable for accessing the first core network, so that the accuracy of the decision is improved, and the UE is accessed to a more suitable core network.

With reference to the first aspect, in certain implementation manners of the first aspect, the sending, by the first AMF, a rerouting request message to the access network device based on the first message includes:

and the first AMF sends a rerouting request message to the access network equipment according to the identification of the terminal equipment under the condition that the first core network does not store the subscription data of the terminal equipment.

In this implementation manner, if the first AMF determines, according to the identifier of the UE, that the subscription data of the UE is not stored in the first core network, which indicates that the UE is not in the first core network for opening an account, the UE can only access another core network (i.e. the second core network), thereby notifying the RAN to perform rerouting.

For example, if the park user does not open an account in the public network, the first AMF discovers that the subscription data of the park UE is not stored in the public network through the identity of the UE, and determines that the UE may be the park UE, thereby instructing the RAN to reroute the registration request of the UE to the AMF of the park network.

the first AMF determines that the subscription data of the terminal equipment is stored in the first core network according to the identification of the terminal equipment, wherein the subscription data comprises type information of the terminal equipment, and the type information is used for indicating whether the terminal equipment is a public network user type or a private network user type;

and the first AMF sends a rerouting request message to the access network equipment according to the type information of the terminal equipment contained in the subscription data under the condition that the terminal equipment is determined not to belong to the user type of the first core network.

In this implementation manner, the first AMF determines, according to the identifier of the UE, that the subscription data of the UE is stored in the first core network, where the subscription data carries type information of the UE, where the type information may indicate that the UE is a public network user or a private network user. Taking the first core network as a public network as an example, if the type of the UE indicates that the UE is a private network user, directly judging that the UE is suitable for accessing the private network, and sending a rerouting request message to access network equipment. The implementation may support a first AMF decision whether to accept the UE to access the first core network.

With reference to the first aspect, in certain implementations of the first aspect, the first message contains an identification of the terminal device and location information of the terminal device,

the first AMF sends a rerouting request message to the access network device based on the first message, comprising:

the first AMF determines that the subscription data of the terminal equipment is stored in the first core network according to the identification of the terminal equipment;

and the first AMF sends a rerouting request message to the access network equipment according to the position information of the terminal equipment under the condition that the TA in the position information of the terminal equipment is determined to be positioned in the TA range of the second core network or the cell in the position information is determined to be positioned in the cell range of the second core network.

In this implementation manner, the first AMF determines, according to the identifier of the UE, that the subscription data of the UE is stored in the first core network, which indicates that the UE opens an account in the first core network. If the location information of the UE indicates that the UE is currently accessed in the area range corresponding to the second core network, the first AMF determines that the UE is suitable for accessing the second core network. For example, the park user opens an account on the public network and initiates a registration process in the park, and the implementation can improve the accuracy of the access decision.

With reference to the first aspect, in certain implementations of the first aspect, the first message includes an identification of the terminal device and an identification of the network slice requested by the terminal device,

the first AMF sends a rerouting request message to the access network device according to the identification of the network slice requested by the terminal device, in case that the network slice is determined to be provided by the second core network.

In this implementation manner, the first AMF determines, according to the identifier of the UE, that the subscription data of the UE is stored in the first core network, which indicates that the UE opens an account in the first core network. At this point, the first AMF performs an access decision for the UE in conjunction with the network slice requested by the UE. For example, a campus user opens an account on a public network, and the network slices identified by the network slice identification are provided by the campus network, and the public network AMF determines that the campus user is suitable for accessing the campus network. If the park user opens an account in the public network, but the network slice identified by the network slice identifier is provided by the public network, the public network AMF determines that the park user is suitable for accessing the public network. It can be seen that the implementation can improve the accuracy of the access decision.

With reference to the first aspect, in certain implementations of the first aspect, the first AMF is further configured with one or more of a user list of the second core network, a tracking area identity TAI list of the second core network, and a new radio cell global identity NCGI list of the second core network.

In this implementation, the first AMF is locally configured with information about the second core network, such as one or more of a user list (e.g., a user identification white list), a TAI list, or an NCGI list of the second core network. On the basis, the first AMF can directly determine whether the UE belongs to the user of the second core network or whether the UE is located in the area range of the second core network, so that the efficiency of the first AMF decision is improved.

With reference to the first aspect, in certain implementations of the first aspect, the first AMF is configured with a list of users of the second core network;

and the first AMF sends a rerouting request message to the access network equipment according to the identification of the terminal equipment and the user list of the second core network under the condition that the terminal equipment is determined to belong to the user of the second core network.

In this implementation manner, since the first AMF locally configures the user list of the second core network, the first AMF may directly determine, according to the UE identifier, whether the UE belongs to the user of the second core network, and if so, directly notify the RAN to perform rerouting, which may improve the efficiency of the first AMF decision.

With reference to the first aspect, in certain implementation manners of the first aspect, the first message includes an identifier of the terminal device and location information of the terminal device, and the first AMF is configured with a user list of the second core network and a TAI list of the second core network;

the first AMF determines that the subscription data of the terminal equipment is stored in the first core network according to the identification of the terminal equipment, and determines that the terminal equipment belongs to a user of the second core network according to the identification of the terminal equipment and a user list of the second core network;

in case that the TA in the location information of the terminal device is included in the TAI list of the second core network, the first AMF sends a rerouting request message to the access network device.

In this implementation manner, the first AMF determines, according to the identifier of the UE, that the subscription data of the UE is stored in the first core network, that is, the UE opens an account in the first core network, so that the UE may access the first core network. And, because the first AMF locally configures the user list of the second core network, the first AMF directly determines, according to the UE identifier, that the UE belongs to the user of the second core network. On this basis, in order to improve the accuracy of the decision, the first AMF may decide in combination with the current location of the UE, and if the UE is currently located in the area corresponding to the second core network, the first AMF determines that the UE is suitable for accessing the second core network.

With reference to the first aspect, in certain implementation manners of the first aspect, the first message includes an identifier of the terminal device and location information of the terminal device, and the first AMF is configured with a TAI list of the second core network and/or an NCGI list of the second core network;

the first AMF determines that the subscription data of the terminal equipment are not stored in the first core network according to the identification of the terminal equipment; and the first AMF sends a rerouting request message to the access network device in case the TA in the location information of the terminal device is included in the TAI list of the second core network or the cell in the location information of the terminal device is included in the NCGI list of the second core network.

In this implementation manner, the first AMF determines, according to the identifier of the UE, that the subscription data of the UE is not stored in the first core network, that is, the UE is not in the first core network for opening an account. And, since the first AMF locally configures a location list related to the second core network, the first AMF may determine, according to the location information of the UE, that the UE is currently located in a related area of the second core network, where the first AMF determines that the UE is suitable for accessing the second core network.

the first AMF sends an access policy request message to the AM PCF based on the first message, wherein the access policy request message is used for requesting to acquire a decision of the terminal equipment to access the network;

the first AMF receives an access policy response message from the AM PCF, and the access policy response message indicates that the terminal equipment is accessed to the second core network;

the first AMF sends a rerouting request message to the access network device based on the access policy response message.

In this implementation, the first AMF requests the AM PCF to perform a decision for the UE to access the network based on the first message. And under the condition that the AM PCF determines that the UE needs to be provided with service by the second core network, the first AMF sends a rerouting request message to the access network equipment, so that the registration request of the UE is rerouted to the second core network.

With reference to the first aspect, in certain implementations of the first aspect, the access policy response message carries one or more of the following information:

identification of the second core network;

identification of a network slice of the second core network;

an access and mobility management function network element set identifier for the access network device to determine the second core network;

A reject cause value, the reject cause value is used for indicating the terminal equipment to search cells of other TAs except the current TA to attempt to access the network;

updated network slice information including information of the network slice of the second core network.

With reference to the first aspect, in some implementations of the first aspect, the identifier of the terminal device includes a subscriber encryption identifier sui, where the sui includes a route identifier RI and a home network public key identifier HNPK ID, where the RI and/or HNPK ID are used to indicate a type of the terminal device, and the type of the terminal device indicates that the terminal device is a public network subscriber type or a private network subscriber type.

In this implementation, if the UE carries a sui in the registration request, and the public network user and the campus user are distinguished by RI and/or HNPK ID in the sui. In this implementation, the first AMF may determine the type of the UE according to the sui in the registration request, which not only improves the accuracy of the determination, but also may improve the decision efficiency of the AMF.

With reference to the first aspect, in certain implementations of the first aspect, the list of users of the second core network includes a number segment of the user of the second core network, the number segment of the user including one or more of: a globally unique subscriber permanent identity (subscription permanent identifier, SUPI) number segment, an international mobile subscriber identity (international mobile subscriber identifier, IMSI) number segment, a routing identity (routing identifier, RI) number segment in a global subscriber encryption identity (subscription concealed identifier, sui) or a home network public key identity (home network identifier, HNPK ID) number segment in a sui.

With reference to the first aspect, in certain implementations of the first aspect, one of the first core network and the second core network is a public network core network, and the other is a private network core network. For example, the first core network is a public network core network, and the second core network is a private network core network; or the second core network is a private network core network, and the first core network is a public network core network.

It should be noted that, in various specific implementations of the first AMF in the first aspect for sending the rerouting request message to the access network device based on the first message, the access network device is replaced by "terminal device", and the rerouting request message is replaced by "second message", which may be completely applicable to the method in the third aspect. In other words, in the first aspect, the first AMF performs an access decision based on the first message and sends a rerouting request message to the access network device in case it is determined to deny the UE access to the first core network. In a third aspect, the first AMF performs an access decision based on the first message and sends a second message to the terminal device in case it is determined to deny the UE access to the first core network. The first AMF in the first aspect performs an access decision and determines that the UE is denied access to the specific implementation of the first core network, which is also fully applicable in the third aspect. In order to avoid redundancy, in the third aspect, a specific implementation manner of the first AMF determining to reject the UE from accessing the first core network is not described again.

In a second aspect, a method of accessing a network is provided, the method comprising:

the access network equipment receives a rerouting request message from a first AMF, wherein the rerouting request message comprises first indication information, and the first indication information is used for indicating the access network equipment to reroute a registration request to a second core network, and the first AMF belongs to the first core network;

and the access network equipment sends a second message to a second AMF according to the first indication information, wherein the second message comprises a registration request, and the second AMF belongs to a second core network.

In this technical solution, the first core network and the second core network share access network devices, or the first core network and the second core network each have an independent access network device, which is not limited.

With reference to the second aspect, in certain implementations of the second aspect, the access network device is configured with one or more of the following information:

one or more network identifications, mapping relationship with one or more second core networks;

the identification of one or more network slices, and the mapping relation of one or more second core networks;

mapping relationship between one or more AMF set identifiers and one or more second core networks.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes:

The access network equipment determines a second core network according to the mapping relation and the first indication information;

the access network device selects a second AMF from the second core network.

Regarding the technical effects of the method of the second aspect or some implementation manner thereof, reference may be made to the description in the first aspect, which is not repeated here.

In a third aspect, a method of accessing a network is provided, the method comprising:

the first AMF sends a second message to the terminal equipment based on the first message, wherein the second message is used for reselecting the terminal equipment to the second core network, or the second message is used for indicating the terminal equipment to update the registration request and initiating a registration flow based on the updated registration request.

Alternatively, the first core network and the second core network may or may not share an access network device (i.e., each have an independent access network device), which is not limited in this application.

Based on one aspect of the third aspect, in a case where a first AMF (an example of an initial AMF) of the first core network receives a registration request of a UE, if the first AMF determines that the UE is suitable for accessing to the second core network, the first AMF sends a second message to the terminal device, where the second message is used for reselecting the terminal device to the suitable second core network. And the terminal equipment performs cell reselection according to the second message, so as to reselect to a proper second core network.

Based on another technical solution of the third aspect, in a case that a first AMF (an example of an initial AMF) of the first core network receives a registration request of the UE, if the first AMF determines that the UE is suitable for accessing the second core network, the first AMF sends a second message to the terminal device, the second message being used for updating the registration request by the UE. The UE updates the registration request according to the second message, and re-initiates the registration procedure using the updated registration request, so that the UE may access the appropriate (or correct) second core network.

With reference to the third aspect, in some implementations of the third aspect, the first AMF sends the second message to the terminal device based on the first message, including:

the first AMF sends a registration rejection response message to the terminal equipment based on the first message, wherein the registration rejection response message carries a rejection reason value, and the rejection reason value indicates the terminal equipment to search cells of other TAs except the current TA to attempt to access the network.

With reference to the third aspect, in some implementations of the third aspect, the first AMF sends the second message to the access network device based on the first message, including:

the first AMF sends a registration rejection response message to the terminal equipment based on the first message, wherein the registration rejection response message carries the information of the network slice of the second core network.

In the technical solution of the third aspect, the sending, by the first AMF, the second message to the terminal device based on the first message may be implemented in various ways. Specifically, the first AMF makes an access decision based on the first message, and sends a second message to the terminal device if it is determined to reject the UE from accessing the first core network. While the first AMF determines a specific implementation of rejecting the UE to the first core network, reference may be made to various implementations of the first aspect.

In a fourth aspect, a method of accessing a network is provided, the method comprising:

the terminal equipment receives a registration refusal response message from the access network equipment, wherein the registration refusal response message carries a refusal reason value;

and the terminal equipment searches cells of other TAs except the current TA to attempt to access the network according to the reject cause value.

The technical effects of the fourth aspect may be referred to in the description of the third aspect, and are not repeated here.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes:

and the terminal equipment stores the current TA into a permanently forbidden TA list according to the reject cause value, wherein the permanently forbidden TA list is cleared after the terminal equipment is restarted or the Subscriber Identity Module (SIM) is replaced.

In a fifth aspect, there is provided a method of accessing a network, the method comprising:

the terminal equipment receives a registration refusal response message from the access network equipment, wherein the registration refusal response message carries the information of the network slice of the second core network;

the terminal equipment re-initiates a registration process by adopting the updated registration request, wherein the updated registration request contains updated network slice information, and the updated network slice information comprises the information of the network slice of the second core network. The registration request is initiated by the UE through the target access network device, e.g., the UE may perform cell reselection in combination with cell broadcast information based on updated network slice information, determining the target access network device. The target access network device may be an original access network device or another access network device, which is not limited in this application.

The technical effects of the fifth aspect may be referred to in the description of the third aspect, and are not repeated herein.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the method further includes:

and the terminal equipment stores the information of the network slice of the second core network into a locally configured network slice list.

In a sixth aspect, a method for accessing a network is provided, including:

The AM PCF receives an access policy request message of a first AMF from a first core network, wherein the access policy request message is used for requesting to acquire a policy of the UE for accessing the network;

the AM PCF executes the decision of the UE to access the network based on the access strategy request message, and determines that the second core network provides service for the UE;

the AM PCF sends an access policy response message to the first AMF, the access policy response message indicating that the UE is to be accessed to the second core network.

Optionally, the first core network and the second core network share access network equipment, or the first core network and the second core network each deploy access network equipment separately.

In certain implementations of the sixth aspect, the access policy response message carries one or more of the following information:

identification of the second core network;

identification of a network slice of the second core network;

Optionally, in certain implementations of the sixth aspect, before the AM PCF performs the decision of the UE to access the network based on the access policy request message, the method further comprises:

the AM PCF acquires SUPI of the UE;

and, the AM PCF performs a decision for the UE to access the network based on the access policy request message, comprising:

the AM PCF performs the UE's decision to access the network based on the SUPI of the UE.

Optionally, the AM PCF obtains the SUPI of the UE, including:

the AM PCF acquires SUPI of the UE from the access strategy request message; or,

the AM PCF acquires SUCI of the UE from the access strategy request message, and determines SUPI mapped by the SUCI based on the local configuration information; or,

the AM PCF acquires SUCI of the UE from the access strategy request message, and acquires SUPI mapped by the SUCI from the UDM of the first core network.

Optionally, in one implementation, the AM PCF obtains the SUPI mapped by the SUCI from the UDM of the first core network, including:

the AMF PCF sends a SUCI decryption request to the UDM of the first core network, wherein the SUCI decryption request carries the SUCI of the UE;

the AM PCF receives a SUCI decryption response from the UDM of the first core network, wherein the SUCI decryption response carries SUPI mapped by the SUCI.

Technical effects of the sixth aspect may be referred to in the description of technical effects of corresponding implementation manners of the first aspect, which is not repeated here.

In a seventh aspect, a method for accessing a network is provided, including:

the first AMF sends first indication information to the access network equipment based on the first message, wherein the first indication information is used for indicating the access network equipment to reroute the registration request to the second core network.

Optionally, the first message further includes other information besides the registration request of the terminal device, and specific reference may be made to the detailed description of the first aspect, which is not repeated here.

In the technical scheme, under the condition that a first AMF of a first core network receives a registration request of UE, if the first AMF judges that the UE is suitable for accessing to a second core network according to a first message, the first AMF sends first indication information to access network equipment so that the access network equipment determines to reroute the registration request of the UE to the second core network according to the first indication information, thereby realizing that the UE is accessed to a suitable network.

Optionally, in one implementation, the first AMF sends, based on the first message, first indication information to the access network device, including:

The first AMF sends a downlink NAS transmission message to the access network equipment based on the first message, wherein the downlink NAS transmission message carries first indication information.

In an eighth aspect, a method for accessing a network is provided, including:

the access network equipment sends a first message to a first AMF, wherein the first message comprises a registration request of the terminal equipment, and the first AMF belongs to a first core network;

the access network device receives first indication information from a first AMF, wherein the first indication information is used for indicating the access network device to reroute the registration request to a second core network.

Technical effects of the eighth aspect may be referred to the description of the seventh aspect, and will not be repeated.

In an implementation manner of the eighth aspect, the access network device receives first indication information from the first AMF, including:

the access network equipment receives a downlink NAS transmission message from the first AMF, wherein the downlink NAS transmission message carries first indication information.

In an implementation manner of the eighth aspect, after the access network device receives the downlink NAS transport message from the first AMF, the method further includes:

the access network device sends an RRC release message to the terminal device, where the RRC release message includes redirection carrier information (redirection carrier info) and/or cell reselection priorities (cell reselection priorities) information.

In an implementation manner of the eighth aspect, before the access network device sends the RRC release message to the terminal device, the method further includes:

the access network equipment sends a downlink information transmission message to the terminal equipment, wherein the downlink information transmission message comprises a registration refusal response message.

In certain implementations of the seventh or eighth aspect, optionally, the first indication information includes RSFP index information.

In certain implementations of the seventh or eighth aspect, optionally, the first indication information is, for example, a specific implementation of the first indication information in the first aspect or any implementation thereof.

In certain implementations of the seventh or eighth aspect, optionally, the downstream NAS transport message further includes RFSP index information. In other words, the downlink NAS transport message includes first indication information and RFSP index information. For example, if the downlink NAS transport message includes first indication information and RFSP index information, the first indication information may be as a specific implementation of the first indication information in the first aspect or any implementation manner thereof.

In some implementations of the foregoing, if the first AMF of the first core network determines to reject the UE from accessing the first core network, the RFSP index information may be carried in a downlink NAS transport message sent to the RAN. The RAN maps the RFSP index information to corresponding frequency selection parameters (e.g., directedcarrierginfo and/or cellresulectionpriorities) and provides to the UE for cell reselection by the UE. The UE may select another access network device as appropriate based on the frequency selection parameter, thereby accessing the appropriate network.

A ninth aspect provides a communications apparatus having functionality to implement the first, third or seventh aspects, or the method in any possible implementation of these aspects. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

A tenth aspect provides a communication device having functionality to implement the second or eighth aspect, or any possible implementation of the second or eighth aspect. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

An eleventh aspect provides a communications device having functionality to implement the fourth or fifth aspect, or the method in any possible implementation of these aspects. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

A twelfth aspect provides a communications device having functionality to implement the sixth aspect, or the method in any possible implementation of the sixth aspect. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

In a thirteenth aspect, a communications apparatus is provided that includes a processor and a memory. Optionally, a transceiver may also be included. Wherein the memory is for storing a computer program, and the processor is for invoking and running the computer program stored in the memory and controlling the transceiver to transceive signals to cause the communication device to perform the method as in the first, third or seventh aspect, or any possible implementation of these aspects.

In a fourteenth aspect, a communications apparatus is provided that includes a processor and a memory. Optionally, a transceiver may also be included. Wherein the memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory and to control the transceiver to transceive signals to cause the communication device to perform the method as in the second or eighth aspect, or any possible implementation of the second or eighth aspect.

In a fifteenth aspect, a communications apparatus is provided that includes a processor and a memory. Optionally, a transceiver may also be included. Wherein the memory is for storing a computer program, and the processor is for invoking and running the computer program stored in the memory and controlling the transceiver to transceive signals to cause the communication device to perform the method as in the fourth or fifth aspect, or any possible implementation of these aspects.

In a sixteenth aspect, a communication device is provided that includes a processor and a memory. Optionally, a transceiver may also be included. Wherein the memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory and to control the transceiver to transceive signals to cause the communication device to perform the method as in the sixth aspect, or any possible implementation of the sixth aspect.

A seventeenth aspect provides a communication device comprising a processor and a communication interface for receiving data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information, and the communication interface further being for outputting the data and/or information after processing by the processor such that the method as in the first, third or seventh aspect, or any of the possible implementations of these aspects, is performed.

An eighteenth aspect provides a communication device comprising a processor and a communication interface for receiving and transmitting received data and/or information to the processor, the processor processing the data and/or information, and the communication interface further being for outputting the data and/or information after processing by the processor, such that the method as in the second or eighth aspect, or any possible implementation of the second or eighth aspect, is performed.

In a nineteenth aspect, there is provided a communications device comprising a processor and a communications interface for receiving data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information, and the communications interface further being for outputting the data and/or information after processing by the processor such that the method as in the fourth or fifth aspect, or any of the possible implementations of the aspects, is performed.

In a twentieth aspect, a communication device is provided, comprising a processor and a communication interface for receiving data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information, and the communication interface further being for outputting the data and/or information after processing by the processor, such that the method as in the sixth aspect, or any of the possible implementations of the sixth aspect, is performed.

In a twenty-first aspect, there is provided a communication device, at least one processor coupled with at least one memory, the at least one processor being configured to execute a computer program or instructions stored in the at least one memory to cause the communication device to perform the method of the first, third or seventh aspect, or to perform the method as in any one of the possible implementations of these aspects.

In a twenty-second aspect, there is provided a communication device, at least one processor coupled with at least one memory, the at least one processor being configured to execute a computer program or instructions stored in the at least one memory to cause the communication device to perform the second or eighth aspect, or to perform a method as in any one of the possible implementations of the second or eighth aspect.

In a twenty-third aspect, there is provided a communications apparatus, at least one processor coupled with at least one memory, the at least one processor configured to execute a computer program or instructions stored in the at least one memory to cause the communications apparatus to perform the fourth or fifth aspects, or to perform a method as in any one of the possible implementations of these aspects.

In a twenty-fourth aspect, there is provided a communication device, at least one processor coupled with at least one memory, the at least one processor being configured to execute a computer program or instructions stored in the at least one memory to cause the communication device to perform the sixth aspect, or to perform a method as in any one of the possible implementations of the sixth aspect.

In a twenty-fifth aspect, there is provided a computer readable storage medium having stored therein computer instructions which, when run on a computer, cause the method as in any one of the first to eighth aspects, or any one of the possible implementations of these aspects, to be performed.

In a twenty-sixth aspect, there is provided a computer program product comprising computer program code which, when run on a computer, causes the method as in any one of the first to eighth aspects, or any one of the possible implementations of these aspects, to be performed.

A twenty-seventh aspect provides a wireless communication system comprising communication means for performing the method as in the first aspect and communication means for performing the method as in the second aspect; alternatively, a communication device for performing a method as in the first aspect, a communication device for performing a method as in the second aspect, and a communication device for performing a method as in the sixth aspect are included; alternatively, a communication device for performing a method as in the third aspect and a communication device for performing a method as in the fourth aspect; alternatively, a communication device for performing a method as in the third aspect and a communication device for performing a method as in the fifth aspect; alternatively, a communication device for performing a method as in the seventh aspect and a communication device for performing a method as in the eighth aspect are included.

Drawings

Fig. 1 is a schematic diagram of a communication scenario suitable for the technical solution provided in the present application;

FIG. 2 is a schematic diagram of a network architecture suitable for use in embodiments of the present application;

fig. 3 is a schematic flow chart of a method of accessing a network provided herein;

fig. 4 is a schematic structural view of the sui;

fig. 5 is another exemplary flowchart of a method of accessing a network provided herein;

fig. 6 is a schematic flow chart of a method of accessing a network provided herein;

fig. 7 is an example of a method of accessing a network provided herein;

fig. 8 is an example of a method of accessing a network provided herein;

fig. 9 is an example of a method of accessing a network provided herein;

FIG. 10 is an example of a method of accessing a network in common with the present application;

fig. 11 is an example of a method for accessing a network provided herein;

FIG. 12 is a schematic block diagram of a communication device provided herein;

fig. 13 is a schematic structural diagram of a communication device provided in the present application.

Detailed Description

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

For ease of understanding, related concepts or technologies related to the present application will first be briefly described.

The technical scheme provided by the application can be applied to various communication systems, including but not limited to: the fifth generation (the 5th generation,5G) system or a New Radio (NR) system, a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD) system, and the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system. Further, it may also be applied to device-to-device (D2D) communication, vehicle-to-device (V2X) communication, machine-to-machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), and internet of things (internet of things, ioT) communication systems or other communication systems, and the like.

The terminal device in the embodiments of the present application may refer to a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device may also be a cellular telephone, a cordless telephone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved public land mobile network (public land mobile network, PLMN), etc., as the embodiments of the application are not limited in this regard.

The access network device in the embodiments of the present application may be a device with a radio transceiving function, located at a network side, including but not limited to a next generation base station (gndeb, gNB) in a fifth generation (5th generation,5G) communication system, a base station in a sixth generation (6th generation,6G) mobile communication system, a base station in a future mobile communication system, or an access Node in a wireless fidelity (wireless fidelity, wiFi) system, an evolved Node B (eNB) in a long term evolution (long term evolution, LTE) system, a radio network controller (radio network controller, RNC), a Node B (NB), a base station controller (base station controller, BSC), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a Base Band Unit (BBU), a transmission reception point (transmission reception point, TRP), a transmission point (transmitting point, TP), a base transceiver station (base transceiver station, BTS), and the like. In addition, the access network device may also be a wireless controller, a relay station, a vehicle-mounted device, a wearable device, etc. in a cloud wireless access network (cloud radio access network, CRAN) scenario. In addition, the base station may be a macro base station, a micro base station, a relay node, a donor node, a combination thereof, or the like, which is not limited in the embodiments of the present application.

Referring to fig. 1, fig. 1 is a schematic diagram of a network architecture suitable for use in embodiments of the present application.

Wherein, the main functions of each network element are described as follows:

application function (application network, AF): the requirements of the application side on the network side, such as quality of service (quality of service, qoS) requirements or user state event subscriptions, etc., are mainly delivered. The AF may be a third party functional entity or an operator deployed application service, such as an internet protocol multimedia subsystem (internet protocol, multimedia subsystem, IMS) voice call service. For the application function entity of the third party application, when it interacts with the core network, authorization processing may also be performed through the network opening function (network exposure function, NEF), for example, the third party application function directly sends a request message to the NEF, the NEF determines whether the AF is allowed to send the request message, and if the verification is passed, the request message is forwarded to the corresponding policy control function (policy control function, PCF) or unified data management (unified data management, UDM).

UDM: the method is mainly responsible for managing functions of user identification, subscription data, authentication data, user access authorization and the like.

Unified data warehouse (unified data repository, UDR): the access function of the subscription data, the policy data, the application data and other types of data is mainly responsible.

PCF: the method is mainly responsible for policy control functions such as charging, qoS bandwidth guarantee, mobility management, UE policy decision and the like aiming at session and service flow levels. In this architecture, PCFs to which access and mobility management functions (access and mobility management function, AMF) and session management functions (session management function, SMF) are connected correspond to an AM PCF (PCF for access and mobility control) and an SM PCF (PCF for session management), respectively, and may not be the same PCF entity in an actual deployment scenario.

SMF: the method mainly performs the functions of session management, PCF issuing control strategy execution, UPF selection, UE IP address allocation and the like.

Network slice selection function (network slice selection function, NSSF): a set of slice instances is selected for the UE, and an AMF set, allowed nsais, is determined for the UE.

AMF: the method mainly performs the functions of mobility management, access authentication/authorization and the like. In addition, it is also responsible for passing user policies between the UE and PCF.

User plane function (user plane function, UPF): as interface UPF of data network, the functions of user plane data forwarding, charging statistics based on session/stream level, bandwidth limitation, etc. are completed.

Radio access network (radio access network, (R) AN): and the method corresponds to different access networks in 5G, such as wired access, wireless base station access and other modes.

Authentication server function (authentication server function, AUSF): the method is used for carrying out security authentication on the UE when the UE accesses the network.

The interface functions between the network elements in fig. 1 are described as follows:

1) N1: the interface between the AMF and the terminal may be used to deliver QoS control rules, etc. to the terminal.

2) N2: the interface between the AMF and the RAN may be used to transfer radio bearer control information, etc., from the core network side to the RAN.

3) And N3: the interface between the RAN and the UPF is mainly used for transmitting uplink and downlink user plane data between the RAN and the UPF.

4) N4: the interface between SMF and UPF can be used to transfer information between control plane and user plane, including control plane-oriented forwarding rule, qoS control rule, flow statistics rule, etc. and user plane information reporting.

5) N5: the interface between AF and PCF can be used for application service request issue and network event report.

6) N6: and the interface of the UPF and the DN is used for transmitting uplink and downlink user data streams between the UPF and the DN.

7) N7: the interface between PCF and SMF may be used to deliver protocol data unit (protocol data unit, PDU) session granularity and traffic data flow granularity control policies.

8) N8: the interface between the AMF and the UDM can be used for the AMF to acquire subscription data and authentication data related to access and mobility management from the UDM, register current mobility management related information of the terminal from the AMF to the UDM, and the like.

9) N9: the user interface between UPF and UPF is used to transfer the uplink and downlink user data flow between UPF.

10 N10: the interface between the SMF and the UDM may be used for the SMF to obtain session management related subscription data from the UDM, and the SMF registers current session related information of the terminal to the UDM.

11 N11: the interface between the SMF and the AMF may be used to convey PDU session tunnel information between the RAN and the UPF, control messages sent to the terminal, radio resource control information sent to the RAN, etc.

12 N12: the interface between the AMF and the AUSF can be used for initiating an authentication flow to the AUSF by the AMF, wherein the authentication flow can carry SUCI as a subscription identifier;

13 N13): the interface between the UDM and the AUSF may be used for the AUSF to obtain the user authentication vector from the UDM to execute the authentication procedure.

14 N15: the interface between PCF and AMF can be used to issue terminal policies and access control related policies.

15 N35: the interface between the UDM and the UDR may be used for the UDM to obtain the user subscription data information from the UDR.

16 N36: the interface between the PCF and the UDR may be used for the PCF to obtain policy related subscription data and application data related information from the UDR.

17 N52: an interface between the UDM and the NEF for the NEF to open network capabilities to third party application functions, such as third party application functions subscribing to reachability events for all users in a particular group through the NEF to the UDM.

The network elements or functions described above may be either network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Alternatively, the network element or the function may be implemented by one device, or may be implemented by a plurality of devices together, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.

The "network element" may be referred to as an entity, a device, an apparatus, a module, or the like, and is not particularly limited in this application. Also, for ease of understanding and explanation, the description of "network element" is omitted in the following part of the description, for example, the AMF network element is abbreviated as AMF, in which case "AMF" is understood as an AMF network element or an AMF entity, and the description of the same or similar situation is omitted below.

It should be understood that fig. 1 is merely an exemplary network architecture, and a network architecture to which embodiments of the present application are applicable is not limited, and any network architecture capable of implementing the functions of the foregoing network elements is applicable to embodiments of the present application. For example, in some network architectures, network functional entities such as AMF, SMF, PCF and UDM are called Network Function (NF) network elements; alternatively, in other network architectures, the set of network elements, such as AMF, SMF, PCF and UDM, may be referred to as control plane function (control Plane function, CPF) network elements.

The technical problems to be solved by the present application and the technical solutions of the present application are introduced below on the basis of the network architecture introduced in fig. 1.

Referring to fig. 2, fig. 2 is a schematic diagram of a communication scenario suitable for the technical solution provided in the present application. One possible communication scenario is as in fig. 2 (a), where an operator may deploy a common base station, e.g., a next generation base station (next generation Node B, gNB), for a public network and a private network to support both network services for public network users and private network users, to support public network users accessing the public network through the common base station, and private network users accessing the private network through the common base station. As in fig. 2 (a), the core network #1 and the core network #2 share an access network device. Wherein, the core network #1 and the core network #2 each locally configure the PLMN #1, that is, the core network #1 and the core network #2 are deployed by the same operator. The PLMN ID broadcast by the access network device is PLMN #1. The general terminal device in fig. 2 represents a terminal device supporting access to only the core network of the public network, and the dedicated terminal device represents a terminal device supporting access to the core network of the private network. Alternatively, the dedicated terminal device may also support access to the core network of the public network. Illustratively, core network #1 is a public network core network and core network #2 is a campus network, e.g., an enterprise campus, or a mine campus, etc. Another possible communication scenario is shown in fig. 2 (b), where the core network #1 and the core network #2 each have an independent base station, e.g. core network #1 corresponds to access network device 1 and core network #2 corresponds to access network device 2. In the scenario of fig. 2 (b), as an example, in a possible case, the dedicated terminal device initiates a registration request, and the access network device 1 selects the AMF of the core network #1 for the dedicated terminal device to provide a network service, but based on the method provided in the present application, the AMF of the core network #1 performs an access decision, determines to reject the dedicated terminal device to access the core network #1, and triggers the dedicated terminal device to perform cell reselection. After the dedicated terminal device performs cell reselection, the selected target cell may be provided by the access network device 2. Subsequently, the access network device 2 selects the AMF of the core network #2 to provide the network service for the dedicated terminal device. It can be seen that the target access network device after the UE performs the cell reselection may be different from the access network device before the cell reselection is performed.

According to the current communication protocol, a 5G Access Network (AN) mainly performs the selection of AN initial AMF based on the following information:

PLMN ID；

the location of the UE;

the list of network slices requested by the UE, typically denoted as requested nsais; wherein NSSAI represents network slice selection assistance information (network slice selection assistance information);

local operator policy.

Among the above information, the 5G AN is temporarily unable to distinguish between public network users and private users according to PLMN ID, UE location, and local operator policy. While some UEs of the existing network do not have the capability to carry network slice information. Therefore, the AN currently cannot support distinguishing between the public network user and the private network user, so that the AN cannot guarantee to select a correct core network for the private network user or the public network user under the condition that the public network and the private network share the access network device. Taking a private network as an example of a campus network, if a public network core network and the campus network share a base station, a registration process is initiated by a public network user or a user of the campus network. After the common base station receives the registration request of the UE, an initial AMF is selected according to the above information, and the registration request is forwarded to the AMF of the corresponding core network (i.e., the selected initial AMF), that is, the registration request is forwarded to the corresponding core network. However, as described above, since the AN cannot distinguish between the public network user and the private network user, the common base station may forward the registration request of the UE to the AMF of the unsuitable core network, in other words, the common base station may provide network services for the AMF of the unsuitable core network selected by the UE. For example, the access network device selects an AMF of a campus network for a public network user, or an AMF of a public network for a campus user who is suitable for accessing the campus network, or an AMF of a campus network for a campus user who is suitable for accessing a core network of the public network, etc.

If the situation occurs, after the AMF of the campus network or the AMF of the public network receives the registration request of the user, the access of the user may be denied, which may cause problems, for example, the access efficiency of the UE accessing the core network is reduced, or the terminal device cannot access the network for a long time.

Under the present situation, the present application provides a method for accessing a network, which is not only suitable for a communication scenario where a public network core network and a private network core network deploy a common access network device, but also suitable for a communication scenario where a public network core network and a private network core network deploy an independent access network device, and can access a terminal device (for example, a public network user or a private network user) to a suitable core network.

It should be understood that, as used herein, accessing the UE to the correct core network may refer to accessing the UE to the appropriate core network, and is not limited to accessing the public network user to the public network core network, and accessing the private network user to the private network core network. For example, if a private network user does not open an account in the public network, the private network user can only access the private network core network, and the private network core network is the correct core network; if a public network user is not in a private network for opening an account, the public network user can only access a public network core network, and the public network core network is the correct core network; if a private network user opens an account in the public network, the private network user can access the public network core network or the private network core network, and at this time, the private network user is suitable for accessing which core network needs to be comprehensively considered by combining some other factors. For example, when the private network user requests access to a network outside the private network area, the appropriate network is a public network core network, not a private network core network. Examples of some detailed access decisions are given below.

Specific scheme details are described below by taking network elements in a 5G system as an example. It is to be understood that when the scheme is used in an LTE system, or a future communication system, each network element in the scheme may be replaced by another network element having a corresponding function, which is not limited in this application.

In addition, the embodiment of the application relates to a registration procedure of the UE in the core network, which is also commonly referred to as a user registration procedure. Illustratively, the general user registration procedure can be described simply as: the UE sends a registration request to the AMF through the AN, the AMF acquires subscription data from a specific UDM according to the user identification, and the UDM can acquire actual subscription data from the UDR after receiving the request.

As described above, the embodiments of the present application also relate to public networks or private networks.

Public networks refer to communication networks built by network service providers (or operators) for public users.

The private network is a private network which realizes network signal coverage in a specific area and provides communication services for specific users in links of organization, command, management, production, scheduling and the like. As one example, an enterprise campus is a private network, which may also be referred to as a campus network.

The core network refers to a public network or a private network deployed by an operator and is responsible for providing functions such as access and mobility management, session management, policy control, subscription management, and the like, and corresponds to other network elements except the UE, the AF, and the access network in the 5G system. In addition, the core network may include only a part of network elements in fig. 1, all network elements, or other network elements other than fig. 1, which is not limited in this application.

Furthermore, embodiments of the present application relate to registration procedures with AMF redirection.

Taking 5G AN as AN example, the 5GAN receives a registration request from the UE and AMF selection parameters, performs AMF selection based on the received AMF selection parameters and a local operator policy, determines AN initial AMF, and forwards the registration request to the initial AMF. After the initial AMF receives the registration request forwarded by the 5G AN, if it is determined that the UE cannot be served by itself, for example, the network slice requested by the UE is not supported, the registration request of the UE is forwarded to another AMF capable of serving the UE through redirection. Referred to as target AMF. Optionally, before performing redirection, the initial AMF may interact with a network element, such as UDM/NSSF/NRF, to determine information supporting a target AMF serving the UE. In one implementation, the initial AMF forwards the complete registration request message directly to the target AMF; in another implementation, the initial AMF forwards the registration request message to the target AMF via the gNB. The redirection request sent by the initial AMF to the gNB carries information of the target AMF. Thereafter, the registration procedure is continued for the UE by the target AMF.

It can be seen that in the above registration procedure with AMF redirection, the initial AMF may perform redirection of the registration request through a direct or indirect interface with the target AMF, i.e. the initial AMF needs to support direct or indirect contact with the target AMF.

In the UE access control communication scenario of the access network device shared by the public network core network and the private network core network to be solved in the present application, the direct or indirect connection between the private network AMF (for example, AMF of the campus network) and the public network AMF is usually not present, and the difficulty of registering the information of the private network AMF through the public network NRF is also greater. When the RAN receives a registration request from a campus user and selects a public network AMF for the campus UE to provide network services, the public network AMF cannot redirect the registration request from the campus user to the AMF of the campus network directly through a redirection registration procedure. Otherwise, the AMF of the campus network cannot redirect the registration request of the public network user to the public network core network.

It can be seen that in the UE access control communication scenario to be solved in the present application, the UE cannot be redirected to the correct (or suitable) core network by simply reusing the existing redirection registration procedure.

In the method for accessing the network provided by the application, the above problems are solved. And, many possible scenarios are applicable for a public network user or a private network user when accessing the network.

For clarity and brevity in description, the first core network and the second core network are introduced in the embodiments of the present application. Optionally, one of the first core network and the second core network is a public network core network, and the other is a private network core network.

The technical scheme provided by the application is described in detail below.

Scheme 1

Referring to fig. 3, fig. 3 is a schematic flow chart of a method for accessing a network provided in the present application.

310. The first AMF receives a first message from the access network device, wherein the first message comprises a registration request of the terminal device, and the first AMF belongs to a first core network.

320. The first AMF sends a rerouting request message to the access network device based on the first message, wherein the rerouting request message contains first indication information, and the first indication information is used for indicating the access network device to reroute the registration request to the second core network.

Wherein the access network device is shared by the first core network and the second core network.

Optionally, the first indication information may include one or more of the following:

identification of the second core network;

identification of a network slice of the second core network;

an AMF set identification (AMF set ID) for the access network device to determine the second core network.

It should be understood that the identifier of the second core network may uniquely identify a second core network, and the access network device may uniquely determine a second core network according to the identifier of the second core network indicated by the first indication information, that is, a one-to-one mapping relationship between the identifier of the second core network and the second core network.

The identification of the network slice of the second core network may be used to identify the second core network providing a certain network slice. The number of the second core networks may be one or more, that is, a one-to-one mapping relationship may be formed between the identifiers of the network slices and the second core networks, for example, the identifier of one network slice corresponds to one second core network; one-to-many mapping is also possible, for example, the identity of one network slice corresponds to a plurality of second core networks; a many-to-many mapping relationship is also possible, for example, the identity of one network slice corresponds to a plurality of second core networks, and different second core networks may provide the same or different network slices.

For example, taking the first core network as the public network as an example, if the network slice of the second core network indicated by the first indication information may be provided by a plurality of private networks, at this time, the identification of the network slice may be considered as indicating that the target network for rerouting is a private network. The access network device can determine a private network from the private networks which support access and can support the network slice indicated by the first indication information, and the determined private network is the second core network. Optionally, if the identification of the network slice indicated by the first indication information is provided by only a private network that the access network device supports access, the private network that can provide the network slice is the second core network.

Furthermore, the AMF set identification of the present application needs to be distinguished from the AMF set ID in the existing registration procedure with AMF redirection. It should be appreciated that the existing AMF set ID is used to indicate one AMF set to the access network device to assist the access network device in determining the target AMF from the AMF set. In this application, however, AMF set identification is used for the access network device to determine the second core network. As some examples, the AMF set identification indicated by the first indication information may be implemented by a specific AMF set identification, e.g. all 1's, or a specific value, for the access network device to determine the second core network. The mapping relationship between the AMF set identifier configured on the access network device and the second core network may be a one-to-one mapping relationship.

Optionally, the first message contains an identification of the terminal device, and one or more of the following:

position information of the terminal equipment;

identification of the network slice requested by the terminal device.

Alternatively, the location information of the terminal device may be information of the TA and/or information of a cell in which the terminal device resides.

It should be appreciated that for a UE supporting network slice identification carried in a registration request, the first message may carry the identification of the network slice requested by the terminal device.

Optionally, the first AMF sends the rerouting message to the access network device based on the first message, and various implementations are possible, some possible examples of which are given below.

(1) In one possible implementation, the first AMF determines to reroute the registration request of the terminal device to the second core network based on information carried in the first message.

In one example, the first AMF initiates an authentication procedure to an AUSF/UDM in the first core network according to the identity of the terminal device carried in the first message. The first AMF sends a rerouting request message to the access network device.

In another example, the first AMF initiates an authentication procedure to the AUSF/UDM in the first core network according to the identifier of the terminal device carried in the first message, and obtains subscription data of the terminal device stored in the first core network. In one possible implementation, the subscription data may include type information of the terminal device, the type information being used to indicate whether the terminal device is of a public network user type or a private network user type. The first AMF may learn the type of the terminal device according to the subscription data. And the first AMF sends a rerouting request message to the access network equipment according to the type information of the terminal equipment under the condition that the terminal equipment is determined not to belong to the user type of the first core network.

It should be understood that if the first core network is a public network core network, then the "user type of the first core network" in this example refers to the public network user type; the terminal device belongs to the user type of the first core network, and the terminal device belongs to the public network user. If the first core network is a private network core network, the "user type of the first core network" in this example refers to the private network user type; the terminal device belongs to the user type of the first core network, and the terminal device belongs to the private network user.

For example, the first core network is a public network core network, and the first AMF in the first core network determines that subscription data of the terminal device is stored in the first core network according to the identifier of the terminal device. And if the type information contained in the subscription data indicates that the terminal equipment is of the private network user type, the first AMF sends a rerouting request message to the access network equipment.

In another example, the first message contains an identification of the terminal device and location information of the terminal device. The first AMF determines that the subscription data of the terminal equipment is stored in the first core network according to the identification of the terminal equipment. And the first AMF determines that the TA in the position information is positioned in the TA range of the second core network according to the position information of the terminal equipment, or sends a rerouting request message to the access network equipment when the cell in the position information is positioned in the cell range of the second core network. It should be understood that the location information of the terminal device may be TA granularity or cell granularity, which is not limited.

In another example, the first message contains an identification of the terminal device and an identification of the network slice requested by the terminal device. The first AMF determines that the subscription data of the terminal equipment is stored in the first core network according to the identification of the terminal equipment. The first AMF sends a rerouting request message to the access network device according to the identification of the network slice requested by the terminal device, in case that the network slice requested by the terminal device is determined to be provided by the second core network. The implementation is applicable to supporting decisions when a terminal device carrying a network slice in a registration request accesses the network.

(2) In another possible implementation, the first AMF is configured with one or more of a user list of the second core network, a TAI list of the second core network, and an NCGI list of the second core network. In this case, the first AMF determines to reroute the registration request of the terminal device to the second core network based on the information carried in the first message and one or more of the user list, the TAI list and the NCGI list of the locally configured second core network.

Alternatively, the user list of the second core network may be a number segment of the user of the second core network. Illustratively, the user's number segment may be one or more of the following:

A globally unique subscriber permanent identity (subscription permanent identifier, SUPI) number segment, an international mobile subscriber identity (international mobile subscriber identifier, IMSI) number segment, a routing identity (routing identifier, RI) number segment in a global subscriber encryption identity (subscription concealed identifier, sui) or a home network public key identity (home network identifier, HNPK ID) number segment in a sui.

Referring to fig. 4, fig. 4 is a schematic structural view of the sui. As shown, the sui includes the following fields:

SUPI type (SUPI type): the value range is 0-7, and the SUPI type is indicated;

home network identification (home network identifier, HN ID): the format used to identify the home network of the UE depends on the type of SUPI. When the SUPI type is IMSI, the HN ID consists of a mobile country code (mobile country code, MCC) and a mobile network code (mobile network code, MNC);

RI: the home operator distributes decimal numbers with the length of 1-4 digits and the value range of 0000-9999;

protection policy identification (protection scheme identifier): the range is 0 to 15;

HNPK ID: the value range is 0-255;

the protection policy output (scheme output), the format depends on the protection policy.

Optionally, in one implementation, the RI in the sui may be used to distinguish between the public network user and the private network user, or the ri+hnpk ID in the sui may be used to distinguish between the private network user and the public network user. In addition, there are mobile country code (mobile country code, MCC) and mobile network code (mobile network code, MNC), ri+hnpkid, MNC are combined to distinguish public network users or private network users, and the value space of the UE number segment is the value range of MNC number RI HNPK ID.

Optionally, in one implementation, if the first AMF may obtain the SUPI information, the private network user or the public network user may be differentiated based on the SUPI number segment.

If the private network user is considered to access the network only in the range (such as the park range) corresponding to the private network, the implementation manner will not affect the public network user. In one possible scenario, the private network UE initiates the registration procedure with the sui. After the first AMF (i.e., the initial AMF) acquires the registration request, the access network device may be triggered to perform rerouting directly based on the RI and/or HNPK ID, and tai+ncgi. In another possible scenario, the private network UE initiates a registration procedure with a 5G-GUTI, which in this case is allocated by the private network AMF. At this point, the access network device may reroute the registration request to the private network AMF based on the S-TMSI.

In addition, if the private network user is considered to access the public network beyond the range corresponding to the private network, the following scenario may also occur:

if the UE initiates a registration procedure with a 5G-GUTI and the 5G-GUTI is allocated by the public network AMF, in this case, the following is possible:

the first AMF (an example of an initial AMF) obtains the user context from the old AMF (old AMF) based on the 5G-GUTI and determines to trigger the access network device to reroute based on the received supi+tai (an example of the UE current location information) +ncgi (e.g., campus range).

It is understood that the initial AMF (initial AMF) and Old AMFs are different AMFs. The Old AMF refers to the AMF accessed by the UE in the last registration, and the initial AMF refers to the AMF accessed by the UE currently, and an interface may be deployed between the two AMFs for the initial AMF to inquire about the user context information from the Old AMF.

The first AMF (an example of the initial AMF) determines that the received registration Request is from a range (e.g., a park range) corresponding to the private network, and requests the UE to register with the sui instead of the 5G-GUTI, e.g., the first AMF indicates that the UE reports the sui through the Identity Request or the error code # 9. Wherein error code #9 indicates the cause of the error as: the network cannot derive the UE identity (UE identity cannot be derived by the network).

In one example, the first AMF is configured with a user list of the second core network, and the first AMF may learn, according to the identity of the terminal device in the first message and the user list of the second core network, whether the terminal device belongs to a user of the second core network. If the identity of the terminal device is located in the user list of the second core network, the first AMF sends a rerouting request message to the access network device.

Optionally, in one example, the first message contains an identification of the terminal device and location information of the terminal device, and the first AMF is configured with a user list of the second core network and a TAI list of the second core network.

In this case, in one example, the first AMF determines, according to the identity of the terminal device, that subscription data of the terminal device is stored in the first core network. And the first AMF determines that the terminal equipment belongs to the user of the second core network according to the identification of the terminal equipment and the user list of the second core network. At this time, the first AMF decides whether to reroute the registration request of the terminal device to the second core network in combination with the location information of the terminal device. For example, if the TA in the location information of the terminal device is included in the TAI list of the second core network, the first AMF sends a rerouting request message to the access network device. Alternatively, the TAI list of the second core network in this example may also be a cell list of the second core network, and if the cell in the location information of the terminal device is included in the cell list of the second core network, the first AMF sends a rerouting request message to the access network device.

In another example, the first message contains an identification of the terminal device and location information of the terminal device, and the first AMF is configured with a TAI list of the second core network and/or an NCGI list of the second core network. The first AMF determines that the subscription data of the terminal equipment is not stored in the first core network according to the identification of the terminal equipment, and the TA in the position information of the terminal equipment is contained in a TAI list of the second core network, or the cell in the position information of the terminal equipment is contained in an NCGI list of the second core network. In this case, the first AMF sends a reroute request message to the access network device.

330. And the access network equipment sends a second message to the second AMF according to the first indication information.

Wherein the second message contains a registration request of the terminal device, and the second AMF belongs to the second core network.

Illustratively, the access network device is configured with one or more of the following information:

a mapping relation between the network identification and the second core network;

mapping relation between the identification of the network slice and the second core network;

the AMF set identifies a mapping relationship of the second core network.

It should be understood that the mapping relationship may be a one-to-one mapping relationship, a many-to-one mapping relationship, or a many-to-many mapping relationship. For example, the network identity is typically in a one-to-one mapping with the second core network; the network slice identifier and the second core network may be in a one-to-one mapping relationship, for example, one network slice identifier uniquely corresponds to one second core network; or may be a one-to-many mapping relationship, for example, one network slice identifier corresponds to a plurality of second core networks, which indicates that the plurality of second core networks may each provide the network slice; or a many-to-many mapping relationship is also possible, for example, one network slice identifier corresponds to a plurality of second core networks, and different second core networks may provide the same network slice. For example, the AMF set identification and the second core network may be in a one-to-one mapping relationship, for example, one AMF set identification uniquely corresponds to one second core network.

When the access network device obtains the first indication information from the first AMF, the first indication information indicates one or more of an identity of the second core network, an identity of a network slice of the second core network, or an AMF set identity, as described above. The access network equipment determines a second core network according to the information indicated in the first indication information and combining with the mapping relation of the local configuration, and selects a target AMF from the second core network, namely the second AMF.

The first indication information indicates a network identifier (for example, identifier a), and the access network device determines, according to a mapping relationship between the locally configured network identifier and the second core network, the second core network corresponding to the network identifier a indicated by the first indication information.

Illustratively, the first indication information indicates an identity (e.g. identity a) of one network slice, and the access network device determines the second core network providing the network slice corresponding to the identity a according to a mapping relationship between the locally configured identity of the network slice and the second core network.

Illustratively, the first indication information indicates an AMF set identifier (AMF set ID), and the access network device determines the second core network according to the AMF set ID and a mapping relationship between the locally configured AMF set identifier and the second core network.

The above is an introduction to the embodiment 1.

As can be seen from the above examples, the solution 1 provided in the present application can provide a solution in the following scenario:

(1) The private network user does not open an account in the public network, and the first AMF may perform the actions in the embodiment based on the number segment information of the user of the second core network configured locally and other information (e.g., current location information (optional)) of the UE;

(2) The private network user opens an account in the public network, and the first AMF executes actions in the embodiment based on the number segment information of the user of the second core network configured locally and other information (such as current position information (optional)) of the UE;

(3) The private network user does not open an account in the public network, and the number segment information of the user of the second core network is not configured on the first AMF, and the AMF triggers the execution of the actions in the embodiment based on other information of the UE, for example, the current location information of the UE, the requested network slice, and the like.

Scheme 1 is implemented by enhancing the redirection procedure with the AMF to trigger the AMF to redirect the registration request of the terminal device to the correct AMF for access. The scheme 1 is suitable for the situation that the RAN selects the private network AMF for the public network user or the RAN selects the public network AMF for the private network user suitable for accessing the private network.

It can be seen that in scheme 1, after determining that the UE is suitable for accessing another core network, the initial AMF (e.g., the first AMF) may notify the RAN to perform rerouting, and carry first indication information in the rerouting request message, which is used to assist the RAN in determining the target core network, and determine the target AMF from the target core network, so as to access the UE to the suitable core network.

Scheme 2

Referring to fig. 5, fig. 5 is another exemplary flowchart of a method for accessing a network provided herein.

510. The first AMF receives a first message from the access network device, the first message comprising a registration request of the terminal device. Wherein the first AMF belongs to a first core network.

520. The first AMF sends a second message to the terminal device based on the first message, the second message being used for reselection of the terminal device to the second core network.

The first access network and the second core network may or may not share an access network device, which is not limited in this application.

Optionally, as an example, in step 520, the first AMF sends a registration rejection response message to the terminal device based on the first message, where the registration rejection response message carries a rejection cause value, and the rejection cause value indicates that the terminal device searches for cells of other TAs than the current TA to attempt to access the network.

530. And the terminal equipment searches cells of other TAs except the current TA to attempt to access the network according to the reject cause value.

Optionally, the terminal device performs cell selection of other TAs according to the reject cause value, and the selected new cell may be located in another access network device, or may also continue to be located in the original access network device, i.e. the access network device in step 510.

In addition, the terminal equipment does not attempt to access the network at the current TA according to the reject cause value.

Scheme 2 enhances the registration rejection procedure to trigger the terminal device to initiate the registration procedure through the correct TA. The scheme 2 is suitable for a scene that the RAN provides network services for AMFs of a private network user selecting a public network core network suitable for accessing the private network or the RAN provides network services for AMFs of the private network user selecting the private network core network.

It can be seen that, in scheme 2, if the first AMF determines to reject the UE accessing the first core network, a new reject cause value may be carried in the registration reject response message. Based on the new reject cause value, the UE may re-search for cells in other TAs in the vicinity to attempt to access the network. In this case, the reselected cell may be located in the same base station or may be located in a different base station, which is not limited in this application.

Scheme 3

Referring to fig. 6, fig. 6 is a schematic flow chart of a method for accessing a network provided herein.

610. The first AMF receives a first message from the access network device, the first message comprising a registration request of the terminal device. Wherein the first AMF belongs to a first core network.

620. The first AMF sends a second message to the terminal equipment based on the first message, wherein the second message is used for indicating the terminal equipment to update the registration request, and initiates a registration flow based on the updated registration request.

Alternatively, the first access network and the second core network may or may not share an access network device, which is not limited in this application.

Optionally, as an example, in step 620, the first AMF sends a registration reject response message to the terminal device based on the first message, where the registration reject response message carries information of a network slice of the second core network.

630. The terminal equipment re-initiates a registration process by adopting an updated registration request, wherein the updated registration request comprises updated network slice information, and the updated network slice information comprises network slice information of the second core network.

It will be appreciated that the updated registration request is initiated by the terminal device via the target access network device. Specifically, the terminal device may perform cell reselection based on the updated network slice information in combination with cell broadcast information, and determine the target access network device. The target access network device may be the original access network device, i.e. the access network device in step 610, or may be another access network device, which is not limited in this application. Alternatively, the cell broadcast information may include TA information, information of optional network slices, and the like. The terminal device illustratively decides that network access is required through another cell based on the updated network slice information and the cell broadcast information. The further cell may be located at the original access network device or at another access network device.

Optionally, the method further comprises step 640.

640. And the terminal equipment stores the information of the network slice of the second core network into a locally configured network slice list.

And 3, enhancing the registration rejection flow, wherein the AMF updates the registration request by carrying the information of the network slice of the second core network in the registration rejection response message, carrying the information of the network slice in the updated registration request, and reinitiating the registration flow. The updated information of the network slice carried in the registration request enables the access network equipment to select a proper core network for the terminal equipment to access. Scheme 3 is mainly applicable to a scenario in which a terminal device that carries network slice information in a registration request attempts to access a network (specifically, a core network).

It can be seen that, in scheme 3, when the first AMF determines that the UE is denied access to the first core network, the registration denial response message may carry the identification information of the network slice of the second core network, so as to trigger the UE to carry the updated requested nsai to reinitiate the registration procedure, thereby correctly accessing to the second core network.

The method for accessing the network provided by the application is described in detail above, and several examples are given below, which respectively illustrate the above schemes.

In the following example, the first core network is taken as a public network core network, and the first AMF belongs to the public network core network.

Referring to fig. 7, fig. 7 is an example of a method for accessing a network provided in the present application. Fig. 7 is an example of the above scheme 1.

701. The UE sends AN message to the RAN.

Wherein the AN message carries AN parameter and a registration request (registration request). The registration request is a non-access stratum (NAS) message. Illustratively, the AN parameters may include information such as AN identity of the UE, e.g., 5G-S-TMSI, globally unique AMF identity (globally unique AMF identifier, guim), selected PLMN ID (selected PLMN ID), etc. The registration request contains an identification of the UE, e.g., sui, 5G-globally unique temporary identity (5G globally unique temporary identifier,5G-GUTI), etc. In addition, the registration request may further include information such as tracking area identifier (tracking area identifier, TAI) last visited by the UE, registration type, and the like. Alternatively, the registration type may include initial registration, mobility registration, periodic registration, or emergency registration.

Wherein 5G-S-TMSI is a shortened form of 5G-GUTI.

The RAN receives AN message from the UE.

702. The RAN sends the N2 parameter to AMF1 and a registration request for the UE.

For example, the RAN performs AMF selection based on information in the AN message, the cell in which the UE is currently camping, and the home operator policy. It is assumed that after the RAN performs AMF selection, an AMF of the public network core network is selected, such as AMF1 in fig. 7. The RAN sends the N2 parameter and a registration request for the UE to AMF1. Illustratively, the RAN sends an N2 interface message to AMF1, where the N2 interface message includes the N2 parameter and a registration request for the UE. Wherein the N2 parameter includes the selected PLMN ID and location information of the UE. Alternatively, the location information of the UE may be information of a current camping cell of the UE, or information of a TA corresponding to the camping cell, for example, TAI information.

703. The AMF1 performs an access decision and determines to deny the UE access to the first core network.

The AMF1 performing the access decision may specifically refer to the AMF1 deciding whether to access the UE to the first core network. In this example, the first core network is taken as a public network core network.

In step 703, AMF1 may determine to accept the UE to access the core network of the public network based on different scenarios, or AMF1 determines to reject the UE from accessing the core network of the public network. In case of rejecting the UE to access the public network core network, the AMF1 sends a rerouting request message to the RAN to reroute the registration request of the UE to the private network core network. It should be understood that, the technical solution of the present application is mainly applicable to the case that the RAN selects the public network core network for providing the network service for the dedicated UE, and the AMF1 of the public network core network reroutes the registration request of the dedicated UE to the AMF of the private network core network, which may refer to various possible examples in step 320, and will not be described herein.

In the case where AMF1 determines to reroute the UE to the private network core network, AMF1 sends a reroute request message to the RAN, as in step 704.

704. AMF1 sends a reroute request message to the RAN.

The rerouting request message includes a first indication information in addition to a registration request sent by the UE. The description of the first indication information may be referred to the detailed description in scheme 1 above, and will not be repeated here.

In addition, AMF1 may also send to the RAN other information that AMF1 (i.e., the initial AMF) provides to the target AMF, such as a list of network slices (rejected nsais) that the first core network/current TA refuses UE access, a list of configured network slices (configured nsais) that need to be provided to the UE, etc.

Subsequently, the RAN reroutes the registration request of the UE to the private network core network based on the rerouting request message from the AMF1, as in steps 705-706.

705. The RAN sends an initial registration request for the UE to the target AMF.

Specifically, the RAN re-performs AMF selection according to the re-route request message, determines a target AMF, and transmits an initial registration request of the UE to the determined AMF.

In addition, the information sent by the RAN to the target AMF may also include information provided by the source AMF (i.e., AMF 1) to the target AMF, as illustrated in step 704.

It should be appreciated that in this example, the target AMF is an AMF of a private network core network, such as AMF2 in fig. 7.

706. The UE completes the registration procedure through the target AMF (e.g., AMF 2) and accesses the second core network.

And the target AMF continues to execute a registration process for the UE according to the information received in the step 705, and completes the access of the UE in the private network core network.

Referring to fig. 8, fig. 8 is an example of a method for accessing a network provided in the present application. Fig. 8 is an example of the above scheme 2.

801. The UE sends AN message to the RAN.

802. The RAN sends the N2 parameter to AMF1 and a registration request for the UE.

803. The AMF1 performs an access decision and determines to deny the UE access to the first core network.

Steps 801 to 803 may refer to steps 701 to 703 in fig. 7, and are not described herein.

Similar to the embodiment in fig. 7, in fig. 8, after the first AMF still focuses on performing the access decision, it is determined that the UE is suitable for accessing the private network core network, and a case of rejecting the UE from accessing the first core network is determined.

804. The first AMF sends a registration reject response message to the UE via the RAN.

In one possible implementation, the registration reject response message carries a reject cause value that instructs the UE to add the current TA to the "permanent forbidden TA" list and search for cells in other TAs to attempt to access the network. Wherein the "permanent forbidden TA" list may be cleared after the UE reboots or replaces the SIM card.

In another possible implementation, the registration reject response message carries a reject cause value, which is #15, or, in other words, multiplexes the reject cause value #15 of the existing registration reject response message. It should be appreciated that if the reject cause value in the registration reject response message is #15, the ue will save the current TA to the "forbidden TA for roaming" list and search for other TAs to attempt to access the network.

805. And according to the received registration rejection response message, the UE performs cell reselection.

Specifically, the UE adds the current TA to the corresponding forbidden TA list, and selects a cell in the other TA of the current location to attempt to access the network. In this case, the reselected cell may be located in the same base station (e.g., RAN in steps 801 to 804), or may be located in a different base station, which is not limited in this application.

806. The UE completes the registration process through the newly selected cell and accesses the corresponding private network core network.

Referring to fig. 9, fig. 9 is an example of a method for accessing a network provided in the present application. Fig. 9 is an example of the above-described scheme 3.

901. The UE sends AN message to the RAN.

902. The RAN sends the N2 parameter to AMF1 and a registration request for the UE.

903. The AMF1 performs an access decision and determines to deny the UE access to the first core network.

Steps 901 to 903 may refer to steps 701 to 703 in fig. 7, and are not described herein.

904. The first AMF sends a registration reject response message to the UE via the RAN, the registration reject response message carrying a network slice ID of the private network core network. In addition, the rejection reason value is carried in the registration rejection response message. The reject cause value is used to instruct the UE to update the registration request and to reinitiate the registration procedure using the updated registration request. Illustratively, the reject cause value may be different from any reject cause value carried in the existing registration reject response message, or a new reject cause value; the present reject cause value may be multiplexed, and the UE may update the registration request based on the cause value by some other technical means or technology, and re-initiate the registration procedure with the updated registration request, which is not limited.

905. And according to the received registration refusal response message, the UE updates the locally configured network slice list.

According to the reject cause value, the UE updates a locally configured network slice list (configured nsai), specifically adds the network slice ID of the private network core network carried in the registration reject response message to the locally configured network slice list.

906. And the UE reinitiates a registration process based on the updated registration request, completes the registration process and accesses the second core network, wherein the updated registration request carries the network slice ID of the private network core network.

In other words, the updated registration request carries a requested nsai, where the requested nsai carries the network slice ID of the private network core network indicated by the first AMF. The RAN that receives the updated registration request may select the correct private network core network for the UE to complete the registration procedure based on the requested nsai.

The updated registration request is initiated by the UE through the target base station. The UE may perform cell reselection to determine the target base station in conjunction with the cell broadcast information based on the updated network slice information. The target base station may be the original base station or another base station, which is not limited in this application.

An example of a method of accessing a network is provided below.

Referring to fig. 10, fig. 10 is an example 400 of a method of accessing a network provided herein.

401. The UE sends AN message to the RAN.

402. The RAN sends the N2 parameter to AMF1 and a registration request for the UE.

Steps 401 to 402 may refer to steps 701 to 702 in fig. 7, and are not described herein.

403. AMF1 sends an access policy request to the AMPCF based on the registration request of the UE.

The AMPCF is an access and mobility management policy control network element, which is one of the access policy control network elements, and may be replaced by another type of access policy control network element. It should be understood that the AM PCF may be replaced by any network element in the core network, as the invention is not limited in this regard. The description below uses AMPCF as an access policy control network element. The above description is applicable to descriptions elsewhere, and will not be repeated.

Wherein, the access policy request carries the UE identifier. Alternatively, the UE identity may be SUPI or sui.

Alternatively, the access policy request may be triggered by AMF1 based on the UE's current access location determination, e.g., the UE is currently accessing from a campus-wide.

In addition, the UE identity carried in the access policy request may come from the UE (e.g., the UE carries the sui and/or SUPI in the initial registration request); or from the Old AMF that the UE has previously accessed (e.g., AMF1 determines the Old AMF based on the 5G-GUTI carried by the UE and obtains the UE context from the Old AMF, which may include the SUPI of the UE).

Optionally, the access policy request may further include location information of the UE received by the AMF1, for example, information of a cell in which the UE currently resides, such as NCGI, TAI, and the like.

404. The AM PCF performs an access decision based on the received access policy request and determines that the UE is served by the second core network.

Before executing the access decision, the AM PCF needs to acquire the SUPI identifier of the UE first, mainly by the following three ways:

mode 1

The AM PCF obtains the SUPI of the UE from the access policy request, in other words, the access policy request sent by the AMF1 carries the SUPI of the UE.

Mode 2

The AM PCF interacts with the UDM1 based on the SUCI, the mapping from the SUCI to the SUPI is completed by the UDM1, and the mapped SUPI is returned. For example, the AM PCF sends a sui decryption request to UDM1, wherein the sui decryption request carries the sui for decryption, and the AMF1 receives a sui decryption response from UDM1, wherein the sui mapped by the sui is carried. In this manner, the access policy request sent by the AMF1 carries the sui of the UE.

Mode 3

The AM PCF performs mapping from SUCI to SUPI based on the local configuration information to obtain SUPI. In this manner, the access policy request carries the sui.

Modes 1 to 3 described above are respectively indicated as a/b/c shown in a dotted line frame in fig. 10.

In step 404, the AM PCF may specifically perform an access decision based on the SUPI, location information of the UE, and locally stored user data, area coverage of the second core network, etc., and determine that the second core network serves the UE.

Illustratively, the AM PCF may determine to serve the UE by the second core network based on one or more of the following reasons:

the AM PCF determines that the UE is a user of the second core network according to the SUPI of the UE;

the AM PCF determines that the UE belongs to a private network user or a public network user based on the user type; or,

the AM PCF determines, based on the user type and the location of the UE, that the current location of the UE is located in the area range of the private network or the area range of the public network, and needs to be served by the private network or the public network.

405. The AM PCF feeds back an access policy response to the AMF 1.

Wherein, the access policy response may carry one or more of the following information:

(a) A network identification of the second core network, such as a campus network identification;

(b) Network slice identification in the second core network;

(c) An AMF set identifier corresponding to the second core network, where the AMF set identifier is used to indicate the second core network that provides service for the UE;

(d) Registering a reject cause value;

(e) Updated network slice (i.e., updated configured nsai).

Wherein, the function and specific implementation of the registration rejection cause value can refer to the description of the registration rejection cause value in scheme 2, see the description in step 520 and step 530 for details; the function and specific implementation of the updated configured nsai may refer to the description of "updated network slice" in scheme 3, and detailed descriptions in step 620 and step 630 are omitted herein.

406. The AMF1 responds according to the access policy, and makes the UE access to the second core network by performing the rerouting procedure of scheme 1 or performing the registration reject procedure in scheme 2 or scheme 3.

It should be appreciated that in this example, the UE access network decision is performed by the AM PCF. When the AM PCF determines that the UE needs to access the second core network and feeds back the decision result to the first AMF through the access decision response message, the process executed by the first AMF subsequently may be multiplexed with any one of the processes executed after the first AMF determines to reject the UE from accessing the first core network, for example, the rerouting process or the registration reject process, which are not limited, in the above scheme 1, scheme 2 or scheme 3. In other words, after the first AMF receives the access policy response message, the RAN/UE may be instructed to access the UE to the network through the second core network.

In addition, the method flow shown in fig. 10 is applicable to a scenario in which the RAN provides network services for an AMF that is suitable for a private network user to access a private network and selects a public network core network, or the RAN provides network services for an AMF that is suitable for a public network user to select a private network core network.

Referring to fig. 11, fig. 11 is another example 200 of a method of accessing a network provided herein.

201. The UE sends a radio resource control (radio resourece control, RRC) message to the RAN.

The RRC message includes AN parameter and a registration request of the UE. The AN parameters and the registration request of the UE may be as described in step 701, which is not described here.

For example, the UE may send an RRC setup complete message to the RAN after triggering the RRC setup procedure to succeed. Taking 5G as an example, the RRC setup complete message may be an rrcsetup complete message, also referred to as message 5.

202. The RAN sends the N2 parameter to AMF1 and a registration request for the UE.

Alternatively, step 202 may also be expressed as: the RAN sends a first message to AMF1, the first message containing the N2 parameter and a registration request for the UE.

Step 202 may refer to step 702, which is not described herein.

203. AMF1 determines that the UE is served by the second core network.

As in the above embodiments, AMF1 represents the AMF of the first core network.

Optionally, in one example, AMF1 determines that the UE is served by the second core network based on the local configuration, and the specific implementation may refer to the various possible examples in step 320 above. Optionally, in another example, the AMF1 sends an access policy request to the AM PCF and receives an access policy response from the AM PCF, and determines, according to the access policy response, that the second core network provides services for the UE, as shown in steps 403-405 in the flowchart of fig. 10, which are not described herein.

204. The AMF1 sends first indication information to the RAN, wherein the first indication information is used for indicating the RAN to reroute the registration request to the second core network.

Optionally, in an example, the first indication information may be referred to as described in the foregoing embodiments, for example, the description of the first indication information in step 320 is not repeated.

Alternatively, in another example, the first indication information may be radio access technology/frequency selection policy (radio access technology (RAT)/frequency selection policy, RFSP) index information.

As one example, AMF1 sends a downlink NAS transport message to the RAN, which carries a registration reject response message and first indication information.

Alternatively, as another example, the AMF1 sends a downlink NAS transport message to the RAN, where the downlink NAS transport message carries a registration reject response message, first indication information, and RFSP index information. In this example, the first indication information may be as described in the above embodiments, for example, the description of the first indication information in step 320.

Illustratively, the RFSP Index information may be denoted as RFSP Index (Index to RAT/frequency selection priority), defining the priority of selection of different access types/frequencies by the UE.

For example, the downlink NAS Transport message may be denoted as downlink NAS Transport, i.e. DL NAS Transport.

In the above example, if the downlink NAS transport message carries RFSP index information, the RAN maps the RFSP index information to a specific frequency selection parameter, and then sends the frequency selection parameter to the UE for cell reselection of the UE.

205. The RAN sends a downlink information transmission message to the UE, wherein the downlink information transmission message carries the registration rejection response message.

Specifically, the RAN sends a downlink information transmission message to the UE according to the first indication information. Illustratively, the downlink information transfer message may be downlink InfoTransfer, namely DL InfoTransfer.

206. The RAN sends an RRC release (RRC release) message to the UE.

Optionally, if the downlink NAS transport message in step 204 carries RFSP index information, the RRC release message may carry the frequency selection parameter. For example, the frequency selection parameter may be indicated by redirection carrier information (redirection carrier info) information and/or cell reselection priorities (cell reselection priorities) information in the RRC release message.

The redirection carrier information is used for indicating that the UE is about to attempt to reside in a specified system/frequency point after leaving the RRC connection state; the cell reselection priority information is used to indicate the frequency priority of cell reselection.

207. The UE performs cell reselection according to the redirection carrier information and/or the cell reselection priority information and accesses to a suitable network through another access network device.

It should be understood that the reselected cell is a cell in the other access network device, and the UE accesses the appropriate network according to the other access network device.

In this example, the AMF may carry the first indication information in a downlink NAS transport message sent by the AMF to the RAN, or the first indication information and the RFSP index information, based on a self-decision or an access policy response received from the AM PCF, to determine that the UE is redirected to the second core network, so as to trigger the RAN to provide the UE with a frequency selection parameter corresponding to the RFSP index information, so that the UE performs cell reselection according to the RFSP index information, and accesses a suitable network.

In this example, if the first AMF of the first core network determines to reject the UE from accessing the first core network, the RFSP index information may be carried in a downlink NAS transport message sent to the RAN. The RAN maps the RFSP index information to corresponding frequency selection parameters (e.g., directedcarrierginfo and/or cellresulectionpriorities) and provides to the UE for cell reselection by the UE. The UE may select another access network device as appropriate based on the frequency selection parameter, thereby accessing the appropriate network.

The method for accessing the network is described in detail above, and the communication device provided by the present application is described below.

Referring to fig. 12, fig. 12 is a schematic block diagram of a communication device provided herein. As shown in fig. 12, the communication apparatus 1000 includes a processing unit 1100, a receiving unit 1200, and a transmitting unit 1300.

Alternatively, the communication apparatus 1000 may correspond to the first AMF in the embodiment of the present application.

In one implementation, the communication apparatus 1000 may apply for the first AMF in scheme 1 of the embodiment in correspondence with the method. In this implementation, the units of the communication apparatus 1000 are configured to implement the following functions:

the receiving unit 1200 is configured to receive a first message from an access network device, where the first message includes a registration request of a terminal device, and the communication device belongs to a first core network;

The sending unit 1300 is configured to send a rerouting request message to the access network device based on the first message, where the rerouting request message includes first indication information, where the first indication information is used to instruct the access network device to reroute the registration request to a second core network;

Optionally, in one embodiment, the first indication information includes one or more of:

an identification of the second core network;

an identification of a network slice of the second core network;

and the AMF set identifier is used for the access network equipment to determine the second core network.

Optionally, in one embodiment, the first message contains an identification of the terminal device, and one or more of:

the location information of the terminal equipment comprises information of a tracking area TA and/or information of a cell where the terminal equipment resides;

and the identification of the network slice requested by the terminal equipment.

Optionally, in one embodiment, the processing unit 1100 is configured to determine, according to the identifier of the terminal device, that subscription data of the terminal device is not stored in the first core network;

And the sending unit 1300 is configured to send the rerouting request message to the access network device.

Optionally, in one embodiment, the processing unit 1100 is configured to:

determining that subscription data of the terminal equipment is stored in the first core network according to the identification of the terminal equipment, wherein the subscription data comprises type information of the terminal equipment, and the type information is used for indicating whether the terminal equipment is a public network user type or a private network user type;

determining the user type of the terminal equipment which does not belong to the first core network according to the type information of the terminal equipment contained in the subscription data;

Optionally, in one embodiment, the first message includes an identification of the terminal device and location information of the terminal device, and the processing unit 1100 is configured to:

determining that subscription data of the terminal equipment are stored in the first core network according to the identification of the terminal equipment;

determining that a TA in the position information of the terminal equipment is positioned in a TA range of the second core network or a cell in the position information is positioned in a cell range of the second core network according to the position information of the terminal equipment;

Optionally, in one embodiment, the first message includes an identifier of the terminal device and an identifier of a network slice requested by the terminal device, and the processing unit 1100 is configured to:

according to the identification of the network slice requested by the terminal equipment, determining that the network slice is provided by the second core network;

Optionally, in one embodiment, the communication device is further configured with one or more of a user list of the second core network, a tracking area identity TAI list of the second core network, and a new radio cell global identity NCGI list of the second core network.

Optionally, in one embodiment, the first AMF is configured with a list of users of the second core network;

the processing unit 1100 is configured to determine, according to the identifier of the terminal device and the user list of the second core network, that the terminal device belongs to a user of the second core network;

The sending unit 1300 is configured to send the rerouting request message to the access network device.

Optionally, in one embodiment, the first message includes an identifier of the terminal device and location information of the terminal device, and the communication apparatus is configured with a user list of the second core network and a TAI list of the second core network; the processing unit 1100 is configured to:

determining that subscription data of the terminal equipment is stored in the first core network according to the identifier of the terminal equipment, and determining that the terminal equipment belongs to a user of the second core network according to the identifier of the terminal equipment and a user list of the second core network;

determining that the TA in the position information of the terminal equipment is contained in a TAI list of the second core network;

Optionally, in one embodiment, the first message contains an identification of the terminal device and location information of the terminal device, and the communication apparatus is configured with a TAI list of the second core network and/or an NCGI list of the second core network; the processing unit 1100 is configured to:

Determining that the subscription data of the terminal equipment is not stored in the first core network according to the identification of the terminal equipment; and the TA in the position information of the terminal equipment is contained in a TAI list of the second core network, or the cell in the position information of the terminal equipment is contained in an NCGI list of the second core network;

Optionally, in an embodiment, the identifier of the terminal device includes a subscriber encryption identifier sui, where the sui includes an RI and a HNPK ID, and the RI and/or the HNPK ID are used to indicate a type of the terminal device, and the type of the terminal device indicates that the terminal device is a public network subscriber type or a private network subscriber type.

Optionally, in one embodiment, the user list of the second core network includes a number segment of a user of the second core network, and the number segment of the user includes one or more of the following:

SUPI number field, IMSI number field, RI number field in SUCI or HNPK ID number field in SUCI.

Optionally, in an embodiment, the first core network is a public network core network, and the second core network is a private network core network; or the second core network is a public network core network, and the first core network is a private network core network.

Optionally, in another implementation, the communication apparatus 1000 may also correspond to the first AMF in scheme 2 or scheme 3 of the method application embodiment.

In this implementation, the units of the communication apparatus 1000 are configured to implement the following functions:

the sending unit 1300 is configured to send, based on the first message, a second message to the terminal device, where the second message is used for reselecting the terminal device to a second core network, or the second message is used to instruct the terminal device to update the registration request, and initiate a registration procedure based on the updated registration request.

Optionally, in one embodiment, the sending unit 1300 is configured to:

and based on the first message, sending a registration rejection response message to the terminal equipment, wherein the registration rejection response message carries a rejection reason value, and the rejection reason value indicates that the terminal equipment searches cells of other TAs except the current TA to attempt to access the network.

Optionally, in one embodiment, the sending unit 1300 is configured to:

And sending a registration refusal response message to the terminal equipment based on the first message, wherein the registration refusal response message carries the information of the network slice of the second core network.

the sending unit 1300 is configured to send the second message to the terminal device.

Optionally, in one embodiment, the processing unit 1100 is configured to:

and the sending unit 1300 is configured to send the second message to the terminal device.

Optionally, in one embodiment, the sending unit 1300 is configured to send, based on the first message, an access policy request message to the AM PCF, where the access policy request message is used to request a decision to obtain the access of the terminal device to the network;

the receiving unit 1200 is configured to receive an access policy response message from the AM PCF, where the access policy response message indicates to access the terminal device to the second core network;

and the sending unit 1300 is further configured to send a rerouting request message to the access network device based on the access policy response message.

Optionally, in one embodiment, the access policy response message carries one or more of the following information:

identification of the second core network;

identification of a network slice of the second core network;

Optionally, in one embodiment, the receiving unit 1200 is further configured to: receiving a first message from an access network device, wherein the first message comprises a registration request of a terminal device, and the communication device belongs to a first core network;

the sending unit 1300 is configured to send, based on the first message, first indication information to the access network device, where the first indication information is used to instruct the access network device to reroute the registration request to a second core network.

Optionally, the first indication information is RFSP index information.

Alternatively, the communication apparatus 1000 may correspond to an access network device in an embodiment of the present application, for example, an access network device in scheme 1 of a method embodiment. In this implementation, the units of the communication apparatus 1000 are configured to implement the following functions:

the receiving unit 1200 is configured to receive a rerouting request message from a first AMF, where the rerouting request message includes first indication information, where the first indication information is used to instruct the access network device to reroute the registration request to a second core network, and the first AMF belongs to the first core network;

the sending unit 1300 is configured to send a second message to a second AMF according to the first indication information, where the second message includes the registration request, and the second AMF belongs to the second core network.

an identification of the second core network;

an identification of a network slice of the second core network;

Optionally, in an embodiment, the access network device is configured with one or more of the following information:

Optionally, in one embodiment, the processing unit 1100 is further configured to:

determining the second core network according to the mapping relation and the first indication information;

and selecting the second AMF from the second core network.

Optionally, in one embodiment, the sending unit 1300 is configured to: sending a first message to a first AMF, wherein the first message comprises a registration request of terminal equipment, and the first AMF belongs to a first core network;

the receiving unit 1200 is configured to receive first indication information from a first AMF, where the first indication information is used to instruct the communication device to reroute the registration request to a second core network.

Optionally, the first indication information is RFSP index information.

Alternatively, the communication apparatus 1000 may correspond to a terminal device in the embodiment of the present application.

In one implementation, the communication apparatus 1000 may correspond to the terminal device in scheme 2 of the method embodiment. In this implementation, the units of the communication apparatus 1000 are configured to implement the following functions:

the receiving unit 1200 is configured to receive a registration rejection response message from the access network device, where the registration rejection response message carries a rejection cause value;

the sending unit 1300 is configured to search for cells of other TAs except the current TA to attempt to access the network according to the reject cause value.

and according to the reject cause value, storing the current TA into a permanent forbidden TA list, wherein the permanent forbidden TA list is cleared after the communication device is restarted or a Subscriber Identity Module (SIM) is replaced.

In another implementation, the communication apparatus 1000 may correspond to the terminal device in scheme 3 of the method embodiment. In this implementation, the units of the communication apparatus 1000 are configured to implement the following functions:

the receiving unit 1200 is configured to receive a registration rejection response message from the access network device, where the registration rejection response message carries information of a network slice of the second core network;

The processing unit 1100 is configured to reinitiate a registration procedure using an updated registration request, where the updated registration request includes updated network slice information, and the updated network slice information includes information of a network slice of the second core network.

and saving the information of the network slice of the second core network to a locally configured network slice list.

Alternatively, the communication device 1000 may correspond to an AM PCF in an embodiment of the present application.

the receiving unit 1200 is configured to receive an access policy request message from a first AMF of a first core network, where the access policy request message is used to request to obtain a policy of the UE for accessing the network;

the processing unit 1100 is configured to perform a decision for the UE to access the network based on the access policy request message, and determine that the second core network provides services for the UE;

the sending unit 1300 is configured to send an access policy response message to the first AMF, where the access policy response message indicates that the UE is accessed to the second core network.

Optionally, in an embodiment, the first core network and the second core network share access network equipment, or the first core network and the second core network each deploy access network equipment separately.

identification of the second core network;

identification of a network slice of the second core network;

Optionally, in one embodiment, the processing unit 1100 is further configured to obtain a SUPI of the UE;

and performing a decision for the UE to access the network based on the SUPI of the UE.

Optionally, the processing unit 1100 is specifically configured to:

acquiring SUPI of the UE from the access strategy request message; or,

acquiring SUCI of the UE from the access strategy request message, and determining SUPI mapped by the SUCI based on the local configuration information; or,

acquiring SUCI of the UE from the access strategy request message; and, the receiving unit 1200 is configured to map SUPI mapped from the sui of the UDM of the first core network; and, the processing unit 1100 acquires the SUPI from the receiving unit 1200.

Optionally, in an implementation manner, the sending unit 1300 is configured to send a sui decryption request to the UDM of the first core network, where the sui decryption request carries the sui of the UE;

and the receiving unit 1200 is configured to receive a sui decryption response from the UDM of the first core network, where the sui decryption response carries the sui mapped by the sui.

In the above embodiments, the receiving unit 1200 and the transmitting unit 1300 may be integrated into one transceiver unit, and have both functions of receiving and transmitting, which is not limited herein.

In embodiments of the communication device 1000 corresponding to the first AMF, the processing unit 1100 is configured to perform processing and/or operations implemented internally by the first AMF in addition to actions of transmitting and receiving. The receiving unit 1200 is configured to perform an action of receiving the first AMF, and the transmitting unit 1300 is configured to perform an action of transmitting the first AMF.

For example, in fig. 3, receiving section 1200 performs the operation of receiving in step 310, and transmitting section 1300 performs the operation of transmitting in step 320.

For another example, in fig. 5, receiving section 1200 performs the operation of receiving in step 510, and transmitting section 1300 performs the operation of transmitting in step 520.

For another example, in fig. 6, receiving section 1200 performs the operation of receiving in step 610, and transmitting section 1300 performs the operation of transmitting in step 620.

For another example, in fig. 11, receiving section 1200 performs the operation of receiving in step 202, and transmitting section 1300 performs the operation of transmitting in step 204. The processing unit 1100 performs step 203 and the like.

In embodiments of the communication apparatus 1000 corresponding to an access network device, the processing unit 1100 is configured to perform processing and/or operations implemented internally by the access network device, in addition to actions of transmitting and receiving. The receiving unit 1200 is configured to perform an action of receiving by the access network device, and the transmitting unit 1300 is configured to perform an action of transmitting by the access network device.

For example, in fig. 3, the transmitting unit 1300 is used to perform the actions transmitted in step 310 and step 330, and the receiving unit 1200 is used to perform the actions received in step 320.

For another example, in fig. 5, the transmitting unit 1300 is used for performing the actions transmitted in step 510.

For another example, in fig. 6, the transmitting unit 1300 is used for executing the actions transmitted in step 610.

For another example, in fig. 11, the receiving unit 1200 is used to perform the actions received in step 201 and step 204, the transmitting unit 1300 is used to perform the actions transmitted in step 202, step 205-step 206, and so on.

In embodiments of the communication apparatus 1000 corresponding to a terminal device, the processing unit 1100 is configured to perform processing and/or operations that are internally implemented by the terminal device, in addition to actions of transmitting and receiving. The reception unit 1200 is configured to perform an action of reception by the terminal device, and the transmission unit 1300 is configured to perform an action of transmission by the terminal device.

For example, in fig. 5, the receiving unit 1200 is used for performing the actions received in step 520, and the processing unit 1100 is used for performing step 530.

For example, in fig. 6, the receiving unit 1200 is used to perform the actions received in step 620, and the processing unit 1100 is used to perform steps 630 and 640. At this time, the communication apparatus 1000 may further include a storage unit 1400 for holding a network slice list of the local configuration.

In various embodiments of communication device 1000 corresponding to an AM PCF, processing unit 1100 is operative to perform processing and/or operations implemented internally by the AM PCF in addition to the acts of transmitting and receiving. The receiving unit 1200 is configured to perform an action of receiving an AM PCF, and the transmitting unit 1300 is configured to perform an action of transmitting an AM PCF.

For example, in fig. 10, receiving section 1200 performs the operation received in step 403, transmitting section 1300 performs the operation transmitted in step 405, and processing section 1100 performs step 404. Optionally, the processing unit 1100 is further configured to perform operations a/c shown in a dashed box in fig. 10, the transmitting unit 1300 performs an action of transmitting the sui decoding request in operation b, and the receiving unit 1200 performs an action of receiving the sui decoding response in operation b.

Referring to fig. 13, fig. 13 is a schematic structural diagram of a communication device provided in the present application. As shown in fig. 13, the communication apparatus 10 includes: one or more processors 11, one or more memories 12, and one or more communication interfaces 13. The processor 11 is configured to control the communication interface 13 to send and receive signals, the memory 12 is configured to store a computer program, and the processor 11 is configured to call and run the computer program from the memory 12, so that the communication apparatus 10 performs a process performed by the first AMF, or the access network device, or the AM PCF, or the terminal device in each method embodiment of the present application.

For example, the processor 11 may have the functions of the processing unit 1100 shown in fig. 12, and the communication interface 13 may have the functions of the receiving unit 1200 and/or the transmitting unit 1300 shown in fig. 12. In particular, the processor 11 may be used to perform processes or operations performed internally by the communication device, and the communication interface 13 is used to perform operations of transmission and/or reception of the communication device.

Alternatively, in one implementation, the communication apparatus 10 may be a network device in a method embodiment, for example, a first AMF or an access network device or an AM PCF. In such an implementation, the communication interface 13 may be a transceiver of a network device. The transceiver may include a receiver and/or a transmitter. Alternatively, the processor 11 may be a baseband device of the network device, and the communication interface 13 may be a radio frequency device.

In another implementation, the communication apparatus 10 may be a chip (or chip system) installed in a network device. In such an implementation, the communication interface 13 may be an interface circuit or an input/output interface.

Alternatively, in one implementation, the communication apparatus 10 may be a terminal device in a method embodiment. In such an implementation, the communication interface 13 may be a transceiver of the terminal device. The transceiver may include a receiver and/or a transmitter. Alternatively, the processor 11 may be a baseband device of the terminal device, and the communication interface 13 may be a radio frequency device.

In another implementation, the communication apparatus 10 may be a chip (or chip system) installed in a terminal device. In such an implementation, the communication interface 13 may be an interface circuit or an input/output interface.

Wherein the dashed box behind a device (e.g., a processor, memory, or communication interface) in fig. 13 indicates that the device may be more than one.

Furthermore, the present application also provides a computer-readable storage medium having stored therein computer instructions that, when executed on a computer, cause operations and/or processes performed by the first AMF in the method embodiments of the present application to be performed.

The present application also provides a computer readable storage medium having stored therein computer instructions that, when executed on a computer, cause operations and/or processes performed by an access network device in method embodiments of the present application to be performed.

The present application also provides a computer-readable storage medium having stored therein computer instructions that, when executed on a computer, cause operations and/or processes performed by an AM PCF in method embodiments of the present application to be performed.

The present application also provides a computer-readable storage medium having stored therein computer instructions that, when executed on a computer, cause operations and/or processes performed by a terminal device in method embodiments of the present application to be performed.

The present application also provides a computer program product comprising computer program code or instructions which, when run on a computer, cause operations and/or processes performed by the first AMF in the method embodiments of the present application to be performed.

The present application also provides a computer program product comprising computer program code or instructions which, when run on a computer, cause operations and/or processing performed by an access network device in the method embodiments of the present application to be performed.

The present application also provides a computer program product comprising computer program code or instructions that, when run on a computer, cause operations and/or processes performed by the AM PCF in the method embodiments of the present application to be performed.

The present application also provides a computer program product comprising computer program code or instructions which, when run on a computer, cause operations and/or processes performed by a terminal device in the method embodiments of the present application to be performed.

The present application also provides a chip including a processor, a memory for storing a computer program being provided independently of the chip, the processor being configured to execute the computer program stored in the memory, such that a communication device in which the chip is installed performs the operations and/or processes performed by the first AMF in any one of the method embodiments.

The present application also provides a chip comprising a processor, the memory for storing a computer program being provided independently of the chip, the processor being configured to execute the computer program stored in the memory, such that a communication device in which the chip is installed performs the operations and/or processes performed by the access network device in any one of the method embodiments.

The present application also provides a chip including a processor, a memory for storing a computer program being provided separately from the chip, the processor being configured to execute the computer program stored in the memory, such that a communication device in which the chip is installed performs the operations and/or processes performed by the AM PCF in any one of the method embodiments.

The present application also provides a chip including a processor, where a memory for storing a computer program is provided separately from the chip, and the processor is configured to execute the computer program stored in the memory, so that a communication device on which the chip is installed performs operations and/or processes performed by a terminal device in any one of the method embodiments.

Further, the chip may also include a communication interface. The communication interface may be an input/output interface, an interface circuit, or the like. Further, the chip may further include the memory.

In the alternative, the processor may be one or more, the memory may be one or more, and the memory may be one or more.

The present application also provides a communication device (e.g., may be a chip or a chip system) including a processor and a communication interface for receiving (or referred to as inputting) data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information, and the communication interface further for outputting (or referred to as outputting) the data and/or information after being processed by the processor, such that the operations and/or processing performed by the first AMF in any one of the method embodiments is performed.

The present application also provides a communication apparatus (e.g., may be a chip or a chip system) comprising a processor and a communication interface for receiving (or referred to as inputting) data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information, and the communication interface further for outputting (or referred to as outputting) the data and/or information after processing by the processor, such that operations and/or processing performed by the access network device in any of the method embodiments are performed.

The present application also provides a communication device (e.g., may be a chip or a chip system) including a processor and a communication interface for receiving (or referred to as inputting) data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information, and the communication interface further for outputting (or referred to as outputting) the data and/or information after processing by the processor, such that operations and/or processing performed by the AM PCF in any one of the method embodiments are performed.

The present application also provides a communication device (e.g., may be a chip or a chip system) including a processor and a communication interface for receiving (or referred to as inputting) data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information, and the communication interface further for outputting (or referred to as outputting) the data and/or information after being processed by the processor, so that operations and/or processing performed by the terminal device in any of the method embodiments are performed.

The present application also provides a communications apparatus comprising at least one processor coupled with at least one memory, the at least one processor configured to execute computer programs or instructions stored in the at least one memory, such that the communications apparatus performs the operations and/or processes performed by the first AMF in any one of the method embodiments.

The present application also provides a communication apparatus comprising at least one processor coupled with at least one memory, the at least one processor configured to execute a computer program or instructions stored in the at least one memory, such that the communication apparatus performs the operations and/or processes performed by an access network device in any of the method embodiments.

The present application also provides a communications apparatus comprising at least one processor coupled with at least one memory, the at least one processor configured to execute computer programs or instructions stored in the at least one memory, such that the communications apparatus performs the operations and/or processes performed by the AM PCF in any one of the method embodiments.

The present application also provides a communication apparatus comprising at least one processor coupled with at least one memory, the at least one processor configured to execute a computer program or instructions stored in the at least one memory, such that the communication apparatus performs the operations and/or processes performed by the terminal device in any of the method embodiments.

The application also provides a wireless communication system, which comprises the first AMF and access network equipment in the scheme 1 of the embodiment of the method; or, the first AMF, the access network device, and the AM PCF shown in fig. 10; or, the method comprises the first AMF and the terminal equipment in the scheme 2 of the method embodiment; or, the first AMF and the terminal device in scheme 3 as in the method embodiment are included. In addition, the wireless communication system may further include other network devices or terminal devices, which are not limited.

The processor in the embodiments of the present application may be an integrated circuit chip with the capability of processing signals. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. 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 the embodiments of the present application may be directly implemented as a hardware encoding processor executing, or may be implemented by a combination of hardware and software modules in the encoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

The memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DRRAM). 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.

The methods provided by the above embodiments may be implemented in whole or in part 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 may include one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media.

The term "and/or" in this application is merely an association relation describing an associated object, and indicates that three relations may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. Wherein, A, B and C can be singular or plural, and are not limited.

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 solution. 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 will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in 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 may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely 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 think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to 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 of accessing a network, comprising:

a first access and mobility management function network element receives a first message from access network equipment, wherein the first message comprises a registration request of terminal equipment, and the first access and mobility management function network element belongs to a first core network;

the first access and mobility management function network element sends a rerouting request message to the access network device based on the first message, wherein the rerouting request message comprises first indication information, and the first indication information is used for indicating the access network device to reroute the registration request to a second core network;

2. The method of claim 1, wherein the first indication information comprises one or more of:

An identification of the second core network;

an identification of a network slice of the second core network;

and the access and mobility management function network element set identifier is used for the access network equipment to determine the second core network.

3. A method according to claim 1 or 2, characterized in that the first message contains an identification of the terminal device, and one or more of the following:

the location information of the terminal equipment comprises information of a tracking area and/or information of a cell where the terminal equipment resides;

4. A method according to claim 3, wherein the first access and mobility management function network element sends a rerouting request message to the access network device based on the first message, comprising:

and the first access and mobility management function network element sends the rerouting request message to the access network device according to the identification of the terminal device under the condition that the first core network does not store the subscription data of the terminal device.

5. A method according to claim 3, wherein the first access and mobility management function network element sends a rerouting request message to the access network device based on the first message, comprising:

the first access and mobility management function network element determines that subscription data of the terminal equipment is stored in the first core network according to the identifier of the terminal equipment, wherein the subscription data comprises type information of the terminal equipment, and the type information is used for indicating whether the terminal equipment is a public network user type or a private network user type;

and the first access and mobility management function network element sends the rerouting request message to the access network device according to the type information of the terminal device contained in the subscription data under the condition that the terminal device is determined not to belong to the user type of the first core network.

6. The method of claim 3, wherein the first message contains an identification of the terminal device and location information of the terminal device,

the first access and mobility management function network element sends a rerouting request message to the access network device based on the first message, including:

The first access and mobility management function network element determines that subscription data of the terminal equipment are stored in the first core network according to the identification of the terminal equipment;

and the first access and mobility management function network element sends the rerouting request message to the access network device according to the position information of the terminal device when determining that the TA in the position information of the terminal device is positioned in the tracking area range of the second core network or that the cell in the position information is positioned in the cell range of the second core network.

7. The method of claim 3, wherein the first message contains an identification of the terminal device and an identification of the network slice requested by the terminal device,

the first access and mobility management function network element sends the rerouting request message to the access network device according to the identifier of the network slice requested by the terminal device, under the condition that the network slice is determined to be provided by the second core network.

8. A method according to claim 3, characterized in that the first access and mobility management function network element is further configured with one or more of a list of users of the second core network, a list of tracking area identities of the second core network and a list of new radio cell global identities of the second core network.

9. The method according to claim 8, characterized in that the first access and mobility management function network element is configured with a list of users of the second core network;

the first access and mobility management function network element sends the rerouting request message to the access network device based on the first message, including:

and the first access and mobility management function network element sends the rerouting request message to the access network device according to the identification of the terminal device and the user list of the second core network under the condition that the terminal device is determined to belong to the user of the second core network.

10. The method according to claim 8, wherein the first message contains an identity of the terminal device and location information of the terminal device, the first access and mobility management function network element being configured with a list of users of the second core network and a list of tracking area identities of the second core network;

the first access and mobility management function network element determines that subscription data of the terminal equipment is stored in the first core network according to the identifier of the terminal equipment, and determines that the terminal equipment belongs to a user of the second core network according to the identifier of the terminal equipment and a user list of the second core network;

and the first access and mobility management function network element sends the rerouting request message to the access network device under the condition that the tracking area in the position information of the terminal device is contained in the tracking area identification list of the second core network.

11. The method according to claim 8, characterized in that the first message contains the identity of the terminal device and location information of the terminal device, the first access and mobility management function network element being configured with a tracking area identity list of the second core network and/or a new radio cell global identity list of the second core network;

The first access and mobility management function network element determines that the subscription data of the terminal equipment are not stored in the first core network according to the identification of the terminal equipment; and the first access and mobility management function network element sends the rerouting request message to the access network device in case that the tracking area in the location information of the terminal device is included in the tracking area identification list of the second core network or the cell in the location information of the terminal device is included in the new wireless cell global identification list of the second core network.

12. A method according to any of claims 1-3, wherein the first access and mobility management function network element sends a reroute request message to the access network device based on the first message, comprising:

the first access and mobility management function network element sends an access policy request message to an access and mobility policy control service network element based on the first message, wherein the access policy request message is used for requesting to acquire a decision of the terminal equipment to access a network;

the first access and mobility management function network element receives an access policy response message from the access and mobility policy control service network element, wherein the access policy response message indicates that the terminal equipment is accessed to the second core network;

And the first access and mobility management function network element sends the rerouting request message to the access network equipment based on the access policy response message.

13. The method of claim 12, wherein the access policy response message carries one or more of the following information:

an identification of the second core network;

an identification of a network slice of the second core network;

an access and mobility management function network element set identifier, wherein the access and mobility management function network element set identifier is used for the access network device to determine the second core network;

a reject cause value, where the reject cause value is used to instruct the terminal device to search cells of other TAs except the current TA to attempt to access the network;

updated network slice information, the updated network slice information comprising information of a network slice of the second core network.

14. The method according to any of claims 3-13, wherein the identity of the terminal device comprises a subscriber encryption identity, the subscriber encryption identity comprising a routing identity and a home network public key identity, the routing identity and/or the home network public key identity being used to indicate the type of the terminal device, the type of the terminal device indicating that the terminal device is a public network subscriber type or a private network subscriber type.

15. The method according to any of claims 8-12, wherein the list of users of the second core network comprises a number segment of the users of the second core network, the number segment of the users comprising one or more of the following:

a subscriber permanent identification number segment, an international mobile subscriber identity number segment, a routing identification number segment in a subscriber encryption identification, or a home network public key identification number segment.

16. The method according to any of claims 1-15, wherein the first core network is a public network core network and the second core network is a private network core network; or the second core network is a public network core network, and the first core network is a private network core network.

17. A method of accessing a network, comprising:

an access network device receives a rerouting request message from a first access and mobility management function network element, wherein the rerouting request message comprises first indication information, and the first indication information is used for indicating the access network device to reroute the registration request to a second core network, wherein the first access and mobility management function network element belongs to a first core network, and the first core network and the second core network share the access network device;

And the access network equipment sends a second message to a second access and mobility management function network element according to the first indication information, wherein the second message comprises the registration request, and the second access and mobility management function network element belongs to the second core network.

18. The method of claim 17, wherein the first indication information comprises one or more of:

an identification of the second core network;

an identification of a network slice of the second core network;

19. The method according to claim 17 or 18, wherein the access network device is configured with one or more of the following information:

and the mapping relation between the one or more access and mobility management function network element set identifiers and the one or more second core networks.

20. The method of claim 19, wherein the method further comprises:

the access network equipment determines the second core network according to the mapping relation and the first indication information;

the access network device selects the second access and mobility management function network element from the second core network.

21. The method according to any of claims 17-20, wherein the first core network is a public network core network and the second core network is a private network core network; or the second core network is a public network core network, and the first core network is a private network core network.

22. A communication device comprising at least one processor coupled to at least one memory, the at least one processor configured to execute a computer program or instructions stored in the at least one memory to cause the communication device to perform the method of any one of claims 1-16.

23. A communication device comprising at least one processor coupled to at least one memory, the at least one processor configured to execute a computer program or instructions stored in the at least one memory to cause the communication device to perform the method of any one of claims 17-21.

24. A chip comprising a processor and a communication interface for receiving data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information to perform the method of any of claims 1-16.

25. A chip comprising a processor and a communication interface for receiving data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information to perform the method of any of claims 17-21.

26. A computer readable storage medium having stored therein computer instructions which, when run on a computer, cause the method of any of claims 1-16 or the method of any of claims 17-21 to be implemented.

27. A computer program product, characterized in that the computer program product comprises computer program code which, when run on a computer, causes the method according to any one of claims 1-16 or the method according to any one of claims 17-21 to be implemented.

28. A wireless communication system comprising a communication device according to claim 22 and a communication device according to claim 23.