Hybrid networking terminal registration method, communication equipment and hybrid networking system

Abstract

The embodiment of the invention provides a hybrid networking terminal registration method, communication equipment and a hybrid networking system, and relates to the technical field of networks, a public network AMF sends a re-registration request to a private network terminal after determining that the private network terminal is currently located in a first area served by a private network slice and an AMF providing service for the private network slice is not the public network AMF; the public network AMF sends the context information of the private network terminal and the second registration request to the private network AMF; and the private network AMF completes registration of the private network terminal based on the received context information and the second registration request and sends a registration receiving message for the second registration request to the private network terminal, and the registration receiving message indicates that the private network terminal is allowed to access the private network slice and is refused to access the public network slice under the condition that the private network terminal is located in the first area. By applying the scheme provided by the embodiment of the invention, the private network terminal can access the private network AMF and access the private network when being in the area of the private network slice service.

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a hybrid networking terminal registration method, communication equipment and a hybrid networking system. Background Art

[0002] Based on the network requirements of vertical industry services, the industry has proposed a networking scenario that combines core network sinking and wireless sharing. That is, the control plane network elements AMF (Access and Mobility Management function), SMF (Session Management function) and data plane network elements UPF (User Plane Function) in the core network are deployed to the local side where the terminal is located as a dedicated network on the local side, referred to as a private network. The private network is often deployed in the park where the terminal is located, dedicated to providing network services for some special terminals in the park. The private network uses a customized UDM (User Data Management) to back up terminal data. The above networking method can realize local data unloading and function customization optimization. Some network functions are implemented by the operator's public network elements, while other network functions are implemented by private network elements. Since only some specific terminals can access the private network, the data security of the terminals accessing the private network can be guaranteed, and personalized special services can be provided to the terminals through the private network elements.

[0003] However, private network terminals can also access the public network. Therefore, in some cases, private network terminals will access the public network AMF by default, and then access the public network, but will not be able to access the private network AMF, and thus cannot access the private network. Summary of the invention

[0004] The purpose of the embodiment of the present application is to provide a hybrid networking terminal registration method, communication equipment and hybrid networking system, so that the private network terminal can access the private network AMF and access the private network when it is in the area served by the private network slice. The specific technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a hybrid networking terminal registration method, which is applied to a hybrid networking system, wherein the hybrid networking system includes a private network and a public network, and a network element in the private network subscribes to a private network slice, and the private network includes a private network access and mobility management function network element AMF;

[0006] The network element in the public network networking subscribes to the public network slice, and the public network networking includes the public network AMF;

[0007] The method comprises:

[0008] The public network AMF receives a first registration request sent by a private network terminal. The private network terminal subscribes to a public network slice and a private network slice, and both the public network slice and the private network slice are default slices. The first registration request contains a first identifier of the area where the private network terminal is currently located;

[0009] When the public network AMF determines, based on the first identifier, that the private network terminal is currently located in a first area served by the private network slice and the AMF providing services for the private network slice is not the public network AMF, the public network AMF sends a reregistration request to the private network terminal and instructs the base station to which the private network terminal is currently connected to release its connection with the private network terminal;

[0010] The public network AMF receives a second registration request sent by the private network terminal, and sends the context information of the private network terminal and the second registration request to the private network AMF;

[0011] The private network AMF completes the registration of the private network terminal based on the received context information and the second registration request sent by the public network AMF, and sends a registration acceptance message for the second registration request to the private network terminal. The registration acceptance message indicates that the private network terminal is allowed to access the private network slice and indicates that the private network terminal is refused access to the public network slice when it is located in the first area served by the private network slice.

[0012] In an embodiment of the present application, the public network networking further includes: a public network policy control function network element PCF. In the public network PCF, a correspondence relationship between a first slice identifier of the private network slice and at least one first area identifier is configured, and the at least one first area identifier corresponds one-to-one to at least one first area served by the private network slice;

[0013] The method further includes:

[0014] After the public network PCF determines that the private network terminal has subscribed to the private network slice, based on the configured correspondence relationship, the public network PCF sends the at least one first area identifier to the public network AMF;

[0015] The public network AMF determines whether the first identifier is included in the at least one first area identifier; if the first identifier is included in the at least one first area identifier, it is determined that the private network terminal is currently located in the first area served by the private network slice.

[0016] In an embodiment of the present application, after determining that the private network terminal is currently located in the first area served by the private network slice, it further includes:

[0017] The public network AMF sends a first message to the public network PCF, and the first message indicates that the private network terminal is currently located in the first area served by the private network slice;

[0018] After receiving the first message, the public network PCF sends the corresponding relationship between the first slice identifier and the at least one first area identifier to the public network AMF;

[0019] If the public network AMF completes the registration of the private network terminal, based on the corresponding relationship, it sends a registration acceptance message for the first registration request to the private network terminal, and this registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when it is located in the first area.

[0020] In an embodiment of the present application, a network slice selection function network element NSSF of the public network is further included in the public network, and a second identifier of the private network AMF is registered in the public network NSSF;

[0021] It is determined that the AMF providing services for the private network slice is not the public network AMF in the following manner:

[0022] The public network AMF sends a second message to the public network NSSF, and the second message is used to query the second identifier of the private network AMF;

[0023] In response to the second message, the public network NSSF sends the second identifier to the public network AMF;

[0024] The public network AMF determines whether the second identifier is its own identifier. If the second identifier is not its own identifier, it is determined that the AMF providing services for the private network slice is not the public network AMF.

[0025] In an embodiment of the present application, the sending the context information of the private network terminal and the second registration request to the private network AMF includes:

[0026] The public network AMF directly sends a third message to the private network AMF, and the third message contains the context information of the private network terminal and the second registration request; or

[0027] The public network AMF sends a fourth message to the first base station to which the private network terminal is currently connected, and the fourth message contains the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request;

[0028] The first base station sends the fourth message to the private network AMF corresponding to the second identifier.

[0029] In an embodiment of the present application, a public network repository function network element NRF is further included in the public network networking. The unified resource identifier URI of the private network AMF is registered in the public network NRF. The public network AMF directly sends a third message to the private network AMF, including:

[0030] The public network AMF obtains the URI of the private network AMF from the public network NRF and sends a third message to the private network AMF through the URI.

[0031] In an embodiment of the present application, the first registration request is sent by the private network terminal after moving from outside the first area to inside the first area, or is sent by the private network terminal when it is inside the first area and the temporary identifier of the private network terminal becomes invalid.

[0032] In an embodiment of the present application, the method further includes:

[0033] The public network AMF receives a third registration request sent by the private network terminal. The third registration request contains a first identifier of the area where the private network terminal is currently located. When it is determined based on the first identifier that the private network terminal is currently outside the first area, the registration of the private network terminal is completed based on the third registration request, and a registration reception message for the third registration request is sent to the private network terminal. This registration reception message indicates that the private network terminal is allowed to access the public network slice and indicates that the private network terminal is denied access to the private network slice when it is in the first area served by the private network slice.

[0034] In a second aspect, an embodiment of the present application provides a method for registering a hybrid networking terminal, which is applied to a private network access and mobility management function network element AMF in a hybrid networking system. The hybrid networking system includes a private network networking and a public network networking. The network elements in the private network networking subscribe to private network slices, and the private network networking includes a private network AMF;

[0035] The network elements in the public network networking subscribe to public network slices, and the public network networking includes a public network AMF;

[0036] The method includes:

[0037] Receiving the context information and a second registration request of the private network terminal;

[0038] Among them, the context information of the private network terminal and the second registration request are as follows: The public network AMF sends them after receiving the second registration request sent by the private network terminal; the second registration request is sent by the private network terminal after receiving the re-registration request sent by the public network AMF; the re-registration request is sent by the public network AMF to the private network terminal after receiving the first registration request sent by the private network terminal, and when it is determined based on the first identifier that the private network terminal is currently located in the first area served by the private network slice and the AMF providing services for the private network slice is not the public network AMF; the private network terminal subscribes to the public network slice and the private network slice, and both the public network slice and the private network slice are default slices, and the first registration request contains the first identifier of the area where the private network terminal is currently located.

[0039] Complete the registration of the private network terminal based on the context information and the second registration request;

[0040] Send a registration reception message for the second registration request to the private network terminal, and this registration reception message indicates that the private network terminal is allowed to access the private network slice and indicates that the private network terminal is refused access to the public network slice when it is located in the first area served by the private network slice.

[0041] In one embodiment of the present application, the receiving the context information and the second registration request of the private network terminal includes:

[0042] Directly receive a third message from the public network AMF, and the third message contains the context information of the private network terminal and the second registration request;

[0043] Or

[0044] Receive a fourth message from the first base station. Among them, the fourth message is sent by the first base station to the private network AMF corresponding to the second identifier after receiving the fourth message, and the fourth message contains the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request.

[0045] In one embodiment of the present application, the first registration request is sent by the private network terminal after moving from outside the first area to inside the first area, or is sent by the private network terminal when it is inside the first area and the temporary identifier of the private network terminal expires.

[0046] In a third aspect, an embodiment of the present application provides a hybrid networking terminal registration method, which is applied to the public network access and mobility management function network element AMF in a hybrid networking system. The hybrid networking system includes a private network networking and a public network networking. The network elements in the private network networking subscribe to the private network slice, and the private network networking includes a private network AMF;

[0047] The network elements in the public network networking subscribe to the public network slice, and the public network networking includes a public network AMF;

[0048] The method includes:

[0049] Receiving a first registration request sent by a private network terminal, where the private network terminal subscribes to the public network slice and the private network slice, and both the public network slice and the private network slice are default slices, and the first registration request includes a first identifier of the area where the private network terminal is currently located;

[0050] When it is determined based on the first identifier that the private network terminal is currently located in the first area served by the private network slice and the AMF serving the private network slice is not the public network AMF, sending a re-registration request to the private network terminal and instructing the base station to which the private network terminal is currently connected to release its connection with the private network terminal;

[0051] Receiving a second registration request sent by the private network terminal, sending the context information of the private network terminal and the second registration request to the private network AMF, so that the private network AMF completes the registration of the private network terminal based on the received context information and the second registration request sent by the public network AMF, and sending a registration acceptance message for the second registration request to the private network terminal, where the registration acceptance message indicates that the private network terminal is allowed to access the private network slice and indicates that the private network terminal is denied access to the public network slice when it is located in the first area served by the private network slice.

[0052] In an embodiment of the present application, the public network networking further includes: a public network policy control function network element PCF, and the first slice identifier of the private network slice and the corresponding relationship with at least one first area identifier are configured in the public network PCF, and the at least one first area identifier corresponds to at least one first area served by the private network slice one by one;

[0053] The determining that the private network terminal is currently located in the first area served by the private network slice based on the first identifier includes:

[0054] Determining whether the first identifier is included in the at least one first area identifier, where the at least one first area identifier is sent by the public network PCF to the public network AMF based on the configured corresponding relationship after determining that the private network terminal has subscribed to the private network slice;

[0055] If the first identifier is included in the at least one first area identifier, it is determined that the private network terminal is currently located in the first area served by the private network slice.

[0056] In one embodiment of the present application, after determining that the private network terminal is currently located in the first area served by the private network slice, the following steps are further included:

[0057] Send a first message to the public network PCF. The first message indicates that the private network terminal is currently located in the first area served by the private network slice. After receiving the first message, the public network PCF sends the correspondence between the first slice identifier and the at least one first area identifier to the public network AMF. If the public network AMF completes the registration of the private network terminal, based on the correspondence, a registration acceptance message for the first registration request is sent to the private network terminal. The registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when located in the first area.

[0058] In one embodiment of the present application, the public network networking further includes a public network network slice selection function network element NSSF, and a second identifier of the private network AMF is registered in the public network NSSF. The AMF that provides services for the private network slice is determined not to be the public network AMF in the following manner:

[0059] Send a second message to the public network NSSF. The second message is used to query the second identifier of the private network AMF, so that the public network NSSF responds to the second message and sends the second identifier to the public network AMF. The public network AMF determines whether the second identifier is its own identifier. If the second identifier is not its own identifier, it is determined that the AMF that provides services for the private network slice is not the public network AMF.

[0060] In one embodiment of the present application, the step of sending the context information of the private network terminal and the second registration request to the private network AMF includes:

[0061] Directly send a third message to the private network AMF. The third message contains the context information of the private network terminal and the second registration request; or

[0062] Send a fourth message to the first base station to which the private network terminal is currently connected. The fourth message contains the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request, so that the first base station sends the fourth message to the private network AMF corresponding to the second identifier.

[0063] In one embodiment of the present application, the public network networking further includes a public network network repository function network element NRF, and a uniform resource identifier URI of the private network AMF is registered in the public network NRF. The step of directly sending a third message to the private network AMF includes:

[0064] Obtain the URI of the private network AMF from the public network NRF, and send a third message to the private network AMF through the URI.

[0065] In an embodiment of the present application, the first registration request is sent by the private network terminal after moving from outside the first area to inside the first area, or the private network terminal sends the first registration request after the temporary identifier of the private network terminal expires while inside the first area.

[0066] In an embodiment of the present application, the method further includes:

[0067] Receive a third registration request sent by a private network terminal, where the third registration request includes a first identifier of the area where the private network terminal is currently located. When it is determined based on the first identifier that the private network terminal is currently outside the first area, complete the registration of the private network terminal based on the third registration request, and send a registration reception message for the third registration request to the private network terminal. The registration reception message indicates that the private network terminal is allowed to access the public network slice, and indicates that the private network terminal refuses to be accessed to the private network slice when it is located in the first area served by the private network slice.

[0068] In a fourth aspect, an embodiment of the present application provides a method for registering a hybrid networking terminal, which is applied to a public network policy control function network element PCF. In the public network PCF, a correspondence relationship between a first slice identifier of a private network slice and at least one first area identifier is configured. The at least one first area identifier corresponds one-to-one to at least one first area served by the private network slice. The public network PCF is included in a public network, the public network is included in a hybrid networking system, and the hybrid networking system further includes a private network. Network elements in the private network subscribe to the private network slice, and the private network includes a private network access and mobility management function network element AMF;

[0069] Network elements in the public network subscribe to the public network slice, and the public network includes a public network AMF;

[0070] The method includes:

[0071] Determine whether the private network terminal has subscribed to the private network slice. The private network terminal is a terminal that sends a first registration request to the public network AMF. The private network terminal subscribes to the public network slice and the private network slice, and both the public network slice and the private network slice are default slices. The first registration request includes a first identifier of the area where the private network terminal is currently located;

[0072] If it is determined that the private network terminal has subscribed to the private network slice, based on the configured corresponding relationship, send the at least one first area identifier to the public network AMF, so that the public network AMF determines whether the first identifier is included in the at least one first area identifier. If the first identifier is included in the at least one first area identifier, it is determined that the private network terminal is currently located in the first area served by the private network slice. And when it is determined that the AMF providing service for the private network slice is not the public network AMF, send a re-registration request to the private network terminal, and instruct the base station to which the private network terminal is currently connected to release its connection with the private network terminal; and enable the public network AMF to receive the second registration request sent by the private network terminal, send the context information of the private network terminal and the second registration request to the private network AMF, and enable the private network AMF to complete the registration of the private network terminal based on the received context information and the second registration request sent by the public network AMF, and send a registration acceptance message for the second registration request to the private network terminal. This registration acceptance message indicates that the private network terminal is allowed to access the private network slice, and indicates that the private network terminal is rejected from accessing the public network slice when it is located in the first area served by the private network slice.

[0073] In one embodiment of the present application, the method further includes:

[0074] Receive a first message sent by the public network AMF. The first message is sent by the public network AMF after determining that the network terminal is currently located in the first area served by the private network slice. The first message indicates that the private network terminal is currently located in the first area served by the private network slice;

[0075] Send the corresponding relationship between the first slice identifier and the at least one first area identifier to the public network AMF, so that if the public network AMF completes the registration of the private network terminal, based on the corresponding relationship, send a registration acceptance message for the first registration request to the private network terminal. This registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when it is located in the first area.

[0076] In a fifth aspect, an embodiment of the present application provides a communication device, where the communication device includes:

[0077] A processor;

[0078] A memory for storing instructions executable by the processor;

[0079] Wherein, the processor is configured to execute the method steps of any one of the second aspect according to the executable instructions.

[0080] Sixth aspect, an embodiment of the present application provides a communication device, the communication device comprising:

[0081] a processor;

[0082] a memory for storing instructions executable by the processor;

[0083] wherein, the processor is configured to execute the method steps of any one of the third aspect according to the executable instructions.

[0084] Seventh aspect, an embodiment of the present application provides a communication device, the communication device comprising:

[0085] a processor;

[0086] a memory for storing instructions executable by the processor;

[0087] wherein, the processor is configured to execute the method steps of any one of the fourth aspect according to the executable instructions.

[0088] Eighth aspect, an embodiment of the present application provides a hybrid networking system, the hybrid networking system includes a private network networking and a public network networking, network elements in the private network networking subscribe to private network slices, and the private network networking includes private network access and a mobility management function network element AMF;

[0089] Network elements in the public network networking subscribe to public network slices, and the public network networking includes a public network AMF;

[0090] The public network AMF is configured to receive a first registration request sent by a private network terminal, the first registration request includes a first identifier of the area where the private network terminal is currently located; when it is determined based on the first identifier that the private network terminal is currently located in a first area served by the private network slice and the AMF providing service for the private network slice is not the public network AMF, send a re-registration request to the private network terminal and instruct the base station to which the private network terminal is currently connected to release its connection with the private network terminal; the private network terminal subscribes to both the public network slice and the private network slice, and both the public network slice and the private network slice are default slices;

[0091] The public network AMF is further configured to receive a second registration request sent by the private network terminal, and send the context information of the private network terminal and the second registration request to the private network AMF;

[0092] The private network AMF is used to complete the registration of the private network terminal based on the context information received from the public network AMF and the second registration request, and send a registration reception message for the second registration request to the private network terminal. The registration reception message indicates that the private network terminal is allowed to access the private network slice, and indicates that the private network terminal is refused access to the public network slice when it is located in the first area served by the private network slice.

[0093] In one embodiment of the present application, the public network also includes: a public network policy control function network element PCF. In the public network PCF, the corresponding relationship between the first slice identifier of the private network slice and at least one first area identifier is configured, and the at least one first area identifier corresponds to at least one first area served by the private network slice one by one;

[0094] The public network PCF is used to send the at least one first area identifier to the public network AMF based on the configured corresponding relationship after determining that the private network terminal has subscribed to the private network slice;

[0095] The public network AMF is further used for:

[0096] Determine whether the first identifier is included in the at least one first area identifier; if the first identifier is included in the at least one first area identifier, determine that the private network terminal is currently located in the first area served by the private network slice.

[0097] In one embodiment of the present application, the public network AMF is further used for:

[0098] After determining that the private network terminal is currently located in the first area served by the private network slice, send a first message to the public network PCF, and the first message indicates that the private network terminal is currently located in the first area served by the private network slice;

[0099] The public network PCF is used to send the corresponding relationship between the first slice identifier and the at least one first area identifier to the public network AMF after receiving the first message;

[0100] The public network AMF is specifically used for, if the public network AMF completes the registration of the private network terminal, based on the corresponding relationship, send a registration reception message for the first registration request to the private network terminal, and the registration reception message indicates that the private network terminal is allowed to access the private network slice and the public network slice when it is located in the first area.

[0101] In one embodiment of the present application, the public network also includes a public network network slice selection function network element NSSF, and the second identifier of the private network AMF is registered in the public network NSSF;

[0102] The public network AMF is specifically used for:

[0103] Sending a second message to the public network NSSF, where the second message is used to query the second identifier of the private network AMF;

[0104] The public network NSSF is used to send the second identifier to the public network AMF in response to the second message;

[0105] The public network AMF is specifically used to determine whether the second identifier is its own identifier. If the second identifier is not its own identifier, it is determined that the AMF providing services for the private network slice is not the public network AMF.

[0106] In an embodiment of the present application, the public network AMF is specifically used to directly send a third message to the private network AMF, where the third message includes the context information of the private network terminal and the second registration request; or

[0107] The public network AMF is specifically used to send a fourth message to the first base station to which the private network terminal currently accesses, where the fourth message includes the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request;

[0108] The first base station is used to send the fourth message to the private network AMF corresponding to the second identifier.

[0109] In an embodiment of the present application, the public network also includes a public network network repository function network element NRF. The uniform resource identifier URI of the private network AMF is registered in the public network NRF. The public network AMF is specifically used for:

[0110] Obtaining the URI of the private network AMF from the public network NRF and sending a third message to the private network AMF through the URI.

[0111] In an embodiment of the present application, the first registration request is sent after the private network terminal moves from outside the first area to inside the first area, or after the private network terminal restarts inside the first area.

[0112] In an embodiment of the present application, the public network AMF is further used for:

[0113] Receive a third registration request sent by a private network terminal, where the third registration request includes a first identifier of the area where the private network terminal is currently located. When it is determined based on the first identifier that the private network terminal is currently outside the first area, complete the registration of the private network terminal based on the third registration request, and send a registration reception message for the third registration request to the private network terminal. This registration reception message indicates that the private network terminal is allowed to access the public network slice, and indicates that the private network terminal is denied access to the private network slice when it is located in the first area served by the private network slice.

[0114] Beneficial effects of the embodiments of the present application:

[0115] In the hybrid networking terminal registration method provided by the embodiments of the present application, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will also determine whether the private network terminal is located within the first area served by the private network slice based on the first identifier of the area where the private network terminal is currently located. If so, and after the public network AMF determines that it is not the AMF providing services for the private network slice, it will actively initiate a re-registration request for the private network terminal. And when the private network terminal re-sends the second registration request after re-registration, it will actively send information so that the private network AMF receives the context information and the second registration request of the private network terminal, and completes the registration process with the private network terminal. That is, in the present application, even if the public network AMF can complete the registration of the private network terminal as the default AMF, it will not cause the private network terminal to always be registered in the public network AMF. Instead, when the private network terminal is located within the first area served by the private network slice, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, the private network AMF will not only determine the public network slice as the default slice after receiving the context information and the second registration request of the private network terminal, causing the private network terminal to be re-registered to the public network AMF. Instead, it will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), enabling the private network terminal to be registered to the private network AMF and then access the private network for communication. Description of the drawings

[0116] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other embodiments can also be obtained based on these drawings.

[0117] Figure 1 It is a schematic diagram of a hybrid networking;

[0118] Figure 2 It is a schematic flowchart of the first hybrid networking terminal registration method provided by the embodiment of the present application;

[0119] Figure 3 It is a schematic diagram of a terminal access scenario provided by the embodiment of the present application;

[0120] Figure 4 It is a schematic flowchart of the first terminal access process provided by the embodiment of the present application;

[0121] Figure 5 It is a schematic flowchart of the second terminal access process provided by the embodiment of the present application;

[0122] Figure 6 It is a schematic flowchart of the second hybrid networking terminal registration method provided by the embodiment of the present application;

[0123] Figure 7 It is a schematic flowchart of the third hybrid networking terminal registration method provided by the embodiment of the present application;

[0124] Figure 8 It is a schematic flowchart of the fourth hybrid networking terminal registration method provided by the embodiment of the present application;

[0125] Figure 9 It is a schematic diagram of the structure of the first communication device provided by the embodiment of the present application;

[0126] Figure 10 It is a schematic diagram of the structure of the second communication device provided by the embodiment of the present application;

[0127] Figure 11 It is a schematic diagram of the structure of the third communication device provided by the embodiment of the present application. Detailed implementation manners

[0128] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art based on the present application belong to the scope of protection of the present application.

[0129] See Figure 1 , which is a schematic diagram of a hybrid networking.

[0130] The figure includes the public network core network and the private network core network within the park. The public network core network includes the public network UPF, the public network NSSF (Network Slice Selection Function), the public network PCF (Policy Control Function), the public network AMF, the public network SMF, the public network NRF (Network Repository Function), the public network UDM / public network AUSF (Authentication Server Function). The private network core network includes the private network UDM, the private network AMF, the private network UPF, and the private network SMF. Public network terminals and private network terminals are distinguished by slices. Public network terminals sign up for public network slices (exemplarily marked as Slice 1), and private network terminals sign up for private network slices (exemplarily marked as Slice 2). As shown in the figure, the public network core network supports Slice 1, and the private network core network supports Slice 2. The area within the dotted box is the area served by the private network slice, and the area outside the dotted box is the area served by the public network slice.

[0131] The implementation between the base station and the core network in the figure indicates that there is a connection relationship between the two. The base station outside the park is a public network base station, which is connected to the public network core network and supports Slice1. The base station inside the park is a private network base station, which is connected to both the public network core network and the private network core network, and supports Slice1 and Slice2.

[0132] The devices that the dotted lines in the figure pass through represent the devices that the terminal needs to pass through to access the network. The terminals outside the park in the figure are public network terminals, which access the public network through public network base stations and public network core networks. The terminals within the park include public network terminals and private network terminals. Public network terminals access the network through private network base stations and public network core networks, and private network terminals access the park intranet, i.e., the private network, through private network base stations and private network core networks.

[0133] Although the private network base station in the park supports both Slice1 and Slice2, its default AMF is the public network AMF. This can prevent the public network terminal from mistakenly accessing the private network core network after entering the park and accessing the private network base station. This is because the private network core network usually does not allow the acquisition of contract data of non-private network terminals. Therefore, if the public network terminal mistakenly accesses the private network core network, it will cause abnormal access to the public network terminal.

[0134] However, the above configuration only applies to the scenario where the private network terminal is only used within the park. If the private network terminal moves from outside the park to inside the park, or the private network terminal is always located inside the park, but the private network terminal is powered on for the first time or powered on again after being powered off for a period of time, the private network terminal should register with the private network AMF and access the private network. However, if the private network terminal subscribes to both the public network slice and the private network slice at the same time, the registration request sent by the private network terminal to the AMF according to the regulations when accessing the network may carry the identifiers of both the public network slice and the private network slice, or may not carry the identifier of any slice. In either case, due to the reasons shown above, the default AMF is the public network AMF, so the private network terminal will default to registering with the public network AMF and will not access the private network AMF.

[0135] To solve the problem in the related art that the private network terminal defaults to accessing the public network AMF, does not access the private network AMF, and cannot access the private network, the embodiment of the present application provides a hybrid networking terminal registration method, a communication device, and a hybrid networking system.

[0136] See Figure 2 , which is a schematic flowchart of the first hybrid networking terminal registration method provided by the embodiment of the present application, and is applied to a hybrid networking system. The above hybrid networking system includes a private network networking and a public network networking. The network elements in the above private network networking subscribe to private network slices, and the above private network networking includes a private network AMF.

[0137] The network elements in the above public network networking subscribe to public network slices, and the above public network networking includes a public network AMF, and the above public network AMF is different from the private network AMF.

[0138] The above public network AMF executes step S201-step S203, and the private network AMF executes step S204.

[0139] S201: Receive a first registration request sent by a private network terminal.

[0140] Among them, the above private network terminal subscribes to a public network slice and a private network slice, and both the above public network slice and the above private network slice are default slices. The above first registration request includes a first identifier of the area where the above private network terminal is currently located. The above first identifier may be the TAI (Tracking Area Identity) of the area where the private network terminal is currently located.

[0141] In an embodiment of the present application, the above first registration request is sent by the private network terminal after moving from outside the above first area to inside the above first area.

[0142] In this case, if the terminal was originally connected to a public network base station outside the first area when it was outside the first area and the private network terminal was in the RRC (Radio Resource Control) connected state, after the private network terminal moves into the first area, it will connect to the private network base station in the first area. In this case, the originally connected public network base station, private network base station, public network core network, and private network core network will execute a handover process to hand over the private network terminal to the new private network base station. After the private network terminal is handed over to the private network base station, according to the specifications in the related technology, it will initiate a mobility registration update in the connected state and send a first registration request to the default public network AMF via the newly connected private network base station, that is, the Registration Request in the NAS (Non-Access Stratum) message.

[0143] Alternatively, if the private network terminal is in the RRC idle state, after the private network terminal moves into the first area, it will reselect to the private network base station in the first area. In this case, the private network terminal will initiate a mobility registration update in the idle state according to the specifications in the related technology and send a first registration request to the default public network AMF via the reselected private network base station, that is, the Registration Request in the NAS message.

[0144] In another embodiment of the present application, the above first registration request is sent by the above private network terminal when it is in the above first area and the temporary identifier of the private network terminal expires.

[0145] In this case, although the private network terminal is always located in the first area, the temporary identifier of the private network terminal expires. For example, it may be caused by the private network terminal being powered off for a duration exceeding the first preset duration (such as 24 hours, 48 hours), etc. In the 5G network, the above temporary identifier is the 5G GUTI (Globally Unique Temporary Identifier). Then the private network terminal will initiate an initial registration via the private network base station in the first area. Since the private network terminal subscribes to the public network slice and the private network slice, the first slice identifier of the private network slice and the second slice identifier of the public network slice will be carried in the first registration message sent during the initial registration, or no slice identifier will be carried in the first registration message. Whether or not a slice identifier is carried, according to the specifications, the first registration message will be routed to the default AMF, that is, the public network AMF, that is, the first registration message will be sent to the public network AMF. The slice identifiers of the above public network slice and private network slice can both be represented by S-NSSAI (Single Network Slice Selection Assistance Information), and each S-NSSAI corresponds to a separate network slice.

[0146] In addition, if the public network AMF receives a registration request from a private network terminal for the first time, the public network AMF also needs to perform a security authentication process with the private network terminal. In this case, the public network AMF does not store the access and mobility contract data of the private network terminal. Therefore, the public network AMF will interact with the public network UDM to obtain the access and mobility contract data of the private network terminal. The access and mobility contract data includes information about the public network slices and private network slices that the private network terminal has signed up for.

[0147] Alternatively, after the public network AMF is disconnected from the private network terminal for longer than a second preset time (such as 24 hours, 48 ​​hours, etc.), the public network AMF will delete the stored access and mobility contract data of the private network terminal. Afterwards, the private network terminal re-registers with the public network AMF. In order to ensure security, the public network AMF needs to re-perform the security authentication process with the private network terminal, and the public network AMF will interact with the public network UDM again to obtain the access and mobility contract data of the private network terminal. The access and mobility contract data includes information about the public network slices and private network slices that the private network terminal has signed. The above-mentioned private network terminal opens an account in the public network UDM to sign contracts for public network slices and private network slices, and sets these two slices as default slices.

[0148] S202: When it is determined based on the first identifier that the private network terminal is currently located in the first area served by the private network slice, and the AMF providing services for the private network slice is not the public network AMF, a re-registration request is sent to the private network terminal, and the base station currently accessed by the private network terminal is instructed to release its connection with the private network terminal.

[0149] In one embodiment of the present application, a correspondence between a first slice identifier of a private network slice and at least one first area identifier is pre-constructed. The at least one first area identifier corresponds one-to-one to at least one first area served by the private network slice. The first area identifier may be TAI. Since the number of first areas served by a private network slice may be greater than 1, the first area identifier may be recorded in the form of a list, the first slice identifier may be referred to as S-NSSAI-x, and the list may be referred to as TAIList-x.

[0150] If the public network AMF already stores the correspondence between the first slice identifier and at least one first area identifier, it can directly determine whether the first identifier is included in the above-mentioned at least one first area identifier. If so, it is determined that the private network terminal is currently located in the first area served by the private network slice.

[0151] In an embodiment of the present application, a public network PCF is further included in the above-mentioned public network networking. The correspondence between the first slice identifier of the above-mentioned private network slice and at least one first area identifier is configured in the public network PCF. The at least one first area identifier corresponds one-to-one to at least one first area served by the private network slice. The public network PCF opens an account and signs the private network slice information, that is, configures the correspondence between the first slice identifier of the private network slice and at least one first area identifier in the public network PCF.

[0152] In this case, the public network PCF executes step A, and the public network AMF executes steps B-C to determine whether the private network terminal is currently located in the first area served by the private network slice based on the above first identifier.

[0153] Step A: After determining that the above-mentioned private network terminal has subscribed to the above-mentioned private network slice, based on the configured correspondence, send the above-mentioned at least one first area identifier to the above-mentioned public network AMF.

[0154] Step B: Determine whether the above first identifier is included in the above at least one first area identifier.

[0155] If the above first identifier is included in the above at least one first area identifier, then execute step B.

[0156] Specifically, the above first registration request includes the terminal identifier of the private network terminal. The terminal identifier can be the SUPI (Subscription Permanent Identifier) of the private network terminal. The public network AMF can send Npcf_AMPolicyControl_Create Request as the first registration request to the public network PCF, which carries the above terminal identifier.

[0157] After receiving the first registration request, the above public network PCF queries based on the terminal identifier carried therein, so as to determine whether the terminal corresponding to the terminal identifier has subscribed to the private network slice. If subscribed, it feeds back at least one first area identifier corresponding to the first slice identifier of the private network slice to the public network AMF. Specifically, at least one first area indication can be carried in the pras attribute and sent to the public network AMF through the message Npcf_AMPolicyControl_Create Response. In this case, the public network PCF only sends the first area identifier to the public network AMF, and does not send the correspondence between the first slice identifier and at least one first area identifier.

[0158] Step C: If the above first identifier is included in the above at least one first area identifier, then determine that the private network terminal is currently located in the first area served by the private network slice.

[0159] In addition, after the public network AMF determines that the private network terminal is currently located in the first area served by the above-mentioned private network slice, the following steps D to F are further executed.

[0160] Step D: The above-mentioned public network AMF sends a first message to the above-mentioned public network PCF.

[0161] The above-mentioned first message indicates that the private network terminal is currently located in the first area served by the above-mentioned private network slice. The above-mentioned first message may be Npcf_AMPolicyControl_Update Request.

[0162] Step E: After receiving the above-mentioned first message, the above-mentioned public network PCF sends the corresponding relationship between the above-mentioned first slice identifier and the above-mentioned at least one first area identifier to the above-mentioned public network AMF.

[0163] After receiving the above-mentioned first message, the above-mentioned public network PCF can determine that the private network terminal is currently located within the service area of the private network slice. In this case, the first slice identifier (S-NSSAI-x) and at least one first area identifier (TAIList-x) can be encapsulated in the privateSnssai attribute and sent to the public network AMF through the message Npcf_AMPolicyControl_UpdateResponse.

[0164] Step F: If the above-mentioned public network AMF completes the registration of the above-mentioned private network terminal, based on the above-mentioned corresponding relationship, a registration acceptance message for the above-mentioned first registration request is sent to the above-mentioned private network terminal.

[0165] This registration acceptance message indicates that the above-mentioned private network terminal is allowed to access the above-mentioned private network slice and the above-mentioned public network slice when located in the above-mentioned first area.

[0166] In response to the first registration request, the above-mentioned public network AMF completes the registration of the above-mentioned private network terminal. The specific way to complete the registration can refer to the related technology and will not be elaborated here.

[0167] Based on the above-mentioned corresponding relationship, the above-mentioned public network AMF determines that the private network terminal subscribes to the private network slice and can determine the first area served by the private network slice. Therefore, the private network terminal is allowed to access the private network slice, and the private network terminal is successfully registered to the public network AMF. Therefore, the private network terminal can also access the public network slice. So this registration acceptance message indicates that the above-mentioned private network terminal is allowed to access the above-mentioned private network slice and the above-mentioned public network slice when located in the above-mentioned first area.

[0168] Specifically, the public network AMF can send a Registration Accept message to the private network terminal, and the configured NSSAI (Network Slice Selection Assistance Information) field included therein carries the first slice identifier of the private network slice and the second slice identifier of the public network slice. It is allowed for the NSSAI field to carry the first slice identifier and the second slice identifier, and it is allowed for the value of the registration area associated with the NSSAI field to be the first area identifier. This indicates that when the above-mentioned private network terminal is located in the above-mentioned first area, it is allowed to access the above-mentioned private network slice and the above-mentioned public network slice.

[0169] After receiving the Registration Accept, the private network terminal can choose to send a Registration Complete message to the public network AMF, indicating that the private network terminal has completed registration.

[0170] In an embodiment of the present application, the above-mentioned public network networking further includes a public network NSSF, and the second identifier of the above-mentioned private network AMF is registered in the public network NSSF. Specifically, the support for the private network slice by the private network AMF can be manually configured in the public network NSSF, or the private network AMF reports the support information of the private network slice to the public network NSSF, so that the second identifier of the above-mentioned private network AMF is registered in the public network NSSF.

[0171] It can be determined through the following steps G - step I that the AMF providing services for the private network slice is not the public network AMF.

[0172] Step G: The above-mentioned public network AMF sends a second message to the above-mentioned public network NSSF.

[0173] The above-mentioned second message is used to query the second identifier of the above-mentioned private network AMF. The first slice identifier of the private network slice is carried in the above-mentioned second message. The above-mentioned second message can be an Nnssf_NSSelection_Get Request, and the carried requested Nssai (requested NSSAI) is S-NSSAI-x.

[0174] Step H: In response to the above-mentioned second message, the above-mentioned public network NSSF sends the above-mentioned second identifier to the above-mentioned public network AMF.

[0175] The above-mentioned public network NSSF looks up the second identifier of the private network AMF that subscribes to the private network slice based on the first slice identifier, and the above-mentioned second identifier is the Set ID (configuration ID) of the private network AMF and / or the network element instance ID of the private network AMF.

[0176] The above-mentioned second identifier is carried in the Nnssf_NSSelection_Get Response.

[0177] Step I: The public network AMF determines whether the second identifier is its own identifier. If the second identifier is not its own identifier, it is determined that the AMF providing services for the private network slice is not the public network AMF.

[0178] Since the private network terminal is currently located in the first area, the private network terminal should theoretically be connected to the private network. When the public network AMF determines that it is not the AMF serving the private network slice, the public network AMF should trigger the private network terminal to re-register with the private network AMF, and thus send a re-registration request (Deregistration Request) to the private network terminal. The re-registration request carries a re-registration request identifier. After receiving the re-registration request, the private network terminal sends a re-registration acceptance message (Deregistration Accept) to the public network AMF, indicating that the private network terminal has received the re-registration request. After receiving the re-registration acceptance message, the public network AMF sends a UE CONTEXT RELEASE COMMAND to the base station to which the private network terminal is currently connected, instructing the base station to release the connection of the private network terminal. Specifically, since the private network terminal is located in the first area, the private network terminal should theoretically be connected to a private network base station. The first registration request received by the public network AMF is forwarded to the public network AMF via the base station to which the private network terminal is connected, so the public network AMF can determine the base station to which the private network terminal is connected. The base station in the first area is configured to support both the public network slice and the private network slice and can communicate with both the public network core network and the private network core network.

[0179] After the base station releases the connection with the private network terminal, it will send a UE CONTEXT RELEASE COMPLETE message to the public network AMF.

[0180] S203: Receive the second registration request sent by the private network terminal, and send the context information of the private network terminal and the second registration request to the private network AMF.

[0181] The information received by the private network terminal does not contain the slice identifier of any slice. Therefore, the private network AMF can independently re-determine the slice that the private network terminal can use without being affected by the received information.

[0182] After the connection between the base station and the private network terminal is released, since the private network terminal received a re-registration request before, it re-registers and sends a second registration request to the public network AMF via the base station. The public network AMF sends the context information of the private network terminal and the second registration request, enabling the private network terminal to access the private network AMF.

[0183] According to different configurations, the public network AMF may send the context information of the above-mentioned private network terminal and the above-mentioned second registration request in different ways.

[0184] If the public network AMF is configured for direct redirection with the private network AMF, the public network AMF sends the context information of the private network terminal and the above-mentioned second registration request to the private network AMF through the following step J.

[0185] Step J: The above-mentioned public network AMF directly sends a third message to the above-mentioned private network AMF.

[0186] The above-mentioned third message contains the context information of the above-mentioned private network terminal and the above-mentioned second registration request.

[0187] In an embodiment of the present application, the above-mentioned public network networking further includes a public network NRF, and the URI of the above-mentioned private network AMF is registered in the public network NRF. Step J is implemented through step K.

[0188] Step K: The above-mentioned public network AMF obtains the URI (Uniform Resource Identifier) of the above-mentioned private network AMF from the above-mentioned public network NRF, and sends a third message to the above-mentioned private network AMF through the above-mentioned URI.

[0189] Specifically, the private network AMF is registered to the public network NRF according to the rules of related technologies, so that the corresponding relationship between the second identifier of the private network AMF registered in the public network NRF and the URI of the private network AMF is established. The public network AMF sends an Nnrf_NFDiscovery Request carrying the second identifier of the private network AMF to the public network NRF, that is, the Set ID (configuration ID) of the private network AMF and / or the network element instance ID of the private network AMF, so that the public network NRF feeds back an Nnrf_NFDiscovery Response carrying the URI of the private network AMF based on the above-mentioned corresponding relationship.

[0190] The public network AMF uses this URI to send a Namf_Communication_N1MessageNotifyRequest to the private network AMF as the third message, which carries the second registration request and the context information of the private network terminal, but does not carry any slice information, so that the private network AMF can independently re-decide the slices that the private network terminal can use without being affected by the third message.

[0191] As can be seen from the above, if direct redirection is possible between the public network AMF and the private network AMF, the public network AMF can directly send a third message to the private network AMF.

[0192] In another embodiment of the present application, the public network AMF is configured not to directly redirect to the private network AMF. In this case, steps L - M are executed to send the context information of the private network terminal and the above-mentioned second registration request to the private network AMF.

[0193] Step L: The above-mentioned public network AMF sends a fourth message to the first base station to which the above-mentioned private network terminal is currently connected.

[0194] The above-mentioned fourth message includes the second identifier of the above-mentioned private network AMF, the context information of the above-mentioned private network terminal, and the above-mentioned second registration request.

[0195] The above-mentioned fourth message does not include the slice identifier of any slice.

[0196] The above-mentioned fourth message can be a REROUTE NAS REQUEST.

[0197] Step M: The above-mentioned first base station sends the fourth message to the private network AMF corresponding to the above-mentioned second identifier.

[0198] As can be seen from the above, if the public network AMF and the private network AMF cannot be directly redirected, the public network AMF can send the third message to the private network AMF through the first base station, so that the private network AMF can successfully receive the third message.

[0199] S204: Based on the received context information and the second registration request sent by the above-mentioned public network AMF, complete the registration of the above-mentioned private network terminal, and send a registration acceptance message for the above-mentioned second registration request to the above-mentioned private network terminal.

[0200] The registration acceptance message indicates that the above-mentioned private network terminal is allowed to access the above-mentioned private network slice, and indicates that the above-mentioned private network terminal is refused to access the above-mentioned public network slice when it is located in the first area served by the above-mentioned private network slice.

[0201] After receiving the context information and the second registration request, the private network AMF can complete the registration of the private network terminal according to the specifications in the related technology, which will not be elaborated here.

[0202] After the private network terminal is registered to the private network AMF, the private network terminal should access the private network provided for the private network terminal and should not access the public network. Therefore, the private network terminal is allowed to access the private network slice and is refused to access the public network slice when it is located in the first area.

[0203] Specifically, the public network AMF may send a Registration Accept to the private network terminal, and the configured NSSAI field included therein carries the first slice identifier of the private network slice and the second slice identifier of the public network slice. The NSSAI field is allowed to carry the first slice identifier, and the NSSAI field carrying the second slice identifier is rejected. The value of the registration area associated with the NSSAI field is the first area identifier. This indicates that the above private network terminal is allowed to access the private network slice and is rejected from accessing the public network slice when the private network terminal is located in the above first area.

[0204] After receiving the Registration Accept, the private network terminal will send a RegistrationComplete to the private network AMF, indicating that the private network terminal has completed registration.

[0205] As can be seen from the above, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will still determine whether the private network terminal is located within the first area served by the private network slice based on the first identifier of the area where the private network terminal is currently located. If so, and after the public network AMF determines that it is not the AMF serving the private network slice, it will actively initiate a re-registration request for the private network terminal. And in the case where the private network terminal re-sends the second registration request after re-registration, it will actively send information so that the private network AMF can receive the context information and the second registration request of the private network terminal, and complete the registration process with the private network terminal. That is, in this application, even if the public network AMF can complete the registration of the private network terminal as the default AMF, it will not cause the private network terminal to always be registered in the public network AMF. Instead, when the private network terminal is located within the first area served by the private network slice, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, when the private network AMF receives the context information and the second registration request of the private network terminal, it will not simply determine the public network slice as the default slice and cause the private network terminal to be re-registered to the public network AMF. Instead, it will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), so that the private network terminal can be registered to the private network AMF and then access the private network for communication.

[0206] In another case, currently the above private network terminal is located outside the first area, including when the private network terminal registers for the first time outside the first area, or when the private network terminal moves from within the first area to outside the first area, or when the private network terminal is outside the first area and the temporary identifier of the private network terminal expires (such as when it is restarted after being shut down for more than the first preset duration).

[0207] In this case, the above public network AMF also performs the following steps N - step O.

[0208] Step N: Receive the third registration request sent by the private network terminal.

[0209] The above-mentioned third registration request (Registration Request) contains the first identifier of the area where the above-mentioned private network terminal is currently located.

[0210] After receiving the third registration request, the public network AMF may need to interact with the terminal to perform security authentication, or obtain the access and mobility subscription data of the private network terminal from the public network UDM. This process is similar to the description in step S201 above and will not be elaborated here.

[0211] Step O: When it is determined based on the above first identifier that the private network terminal is currently outside the above first area, complete the registration of the above private network terminal based on the above third registration request, and send a registration acceptance message for the above third registration request to the above private network terminal.

[0212] This registration acceptance message indicates that the above private network terminal is allowed to access the above public network slice, and indicates that the above private network terminal is denied access to the above private network slice when it is located in the first area served by the above private network slice.

[0213] Specifically, the process by which the public network AMF determines whether the private network terminal is currently within the first area is similar to step S202 above, except that the judgment result in this scenario is that the private network terminal is currently outside the first area, which will not be elaborated here.

[0214] Since the public network AMF determines that the private network terminal is currently outside the first area served by the private network slice, the private network terminal cannot currently use the private network. Therefore, the above registration acceptance message indicates that the above private network terminal is allowed to access the above public network slice, and is denied access to the above private network slice when it is located in the above first area.

[0215] Specifically, the public network AMF can send a Registration Accept to the private network terminal. The configured NSSAI field contained therein carries the first slice identifier of the private network slice and the second slice identifier of the public network slice. The allowed NSSAI field carries the second slice identifier, the rejected NSSAI field carries the first slice identifier, and the value of the registration area associated with the rejected NSSAI field is the first area identifier. This indicates that the above private network terminal is allowed to access the public network slice, and is denied access to the private network slice when the private network terminal is located in the above first area.

[0216] After receiving the Registration Accept, the private network terminal will send a RegistrationComplete to the public network AMF, indicating that the private network terminal has completed the registration.

[0217] As can be seen from the above, the solution provided by the embodiments of the present application also supports the private network terminal to access the public network AMF outside the first area of the private network slice service. Whether the private network terminal registers for the first time outside the first area, or the private network terminal moves from inside the first area to outside the first area, or the private network terminal is outside the first area and the temporary identifier of the private network terminal becomes invalid, it can ensure that the private network terminal can complete the registration normally and achieve normal network access.

[0218] See Figure 3 , which is a schematic diagram of a terminal access scenario provided by the embodiments of the present application.

[0219] Figure 3 The network structure shown in Figure 1 is the same as the network structure shown above. Figure 3 It includes the private network terminal 1 that is always located in the park. The dotted line between the private network terminal 1 and the private network indicates that the private network terminal 1 accesses the private network through the private network base station and the private network core network.

[0220] Figure 3 It also includes the private network terminal 2. The private network terminal 2 moves inside and outside the park. After entering the park, the dotted line between the private network terminal 2 and the private network indicates that the private network terminal 2 accesses the private network through the private network base station and the private network core network; after leaving the park, the dotted line between the private network terminal 2 and the public network indicates that the private network terminal 2 accesses the public network through the public network base station and the public network core network.

[0221] Figure 3 The scenario shown in

[0222] The following describes the complete process of the private network terminal registering to the public network AMF for the first time outside the first area and then moving to the first area and registering to the private network AMF through a complete embodiment.

[0223] See Figure 4 , which is the first schematic diagram of the terminal access process provided by the embodiments of the present application.

[0224] The figure includes a private network terminal, a public network base station, a public network AMF, a public network UDM, a public network AUSF, a public network PCF, a public network NSSF, a public network NRF, a private network AMF, and a private network base station.

[0225] First, the private network terminal registers for the first time outside the first area. In this case, the private network terminal sends a 1.Registration Request to the public network AMF through the public network base station.

[0226] The private network terminal, the public network base station, the public network AMF, the public network UDM, and the public network AUSF jointly execute the 2. security authentication process, the access and mobility subscription data acquisition process of the public network AMF.

[0227] The public network AMF performs 3. PCF selection. After selecting the public network PCF, the public network AMF sends a 4. Npcf_AMPolicyControl_Create Request to the public network PCF.

[0228] The public network PCF feeds back a 5. Npcf_AMPolicyControl_Create Request (pras = TAIList-x) to the public network AMF. It indicates that the value of the pras attribute in the Npcf_AMPolicyControl_Create Request is TAIList-x.

[0229] The public network AMF sends a 5a. Npcf_AMPolicyControl_Update Request to the public network PCF. The public network PCF feeds back a 5b. Npcf_AMPolicyControl_Update Response to the public network AMF.

[0230] The public network AMF sends a 6. Registration Accept to the private network terminal.

[0231] The private network terminal feeds back a 7. Registration Complete to the public network AMF.

[0232] After that, it enters the 8. handover phase (the private network terminal moves into the first area).

[0233] The private network terminal sends a 9. Registration Request to the public network AMF.

[0234] The public network AMF sends a 10. Npcf_AMPolicyControl_Update Request to the public network PCF.

[0235] The public network PCF sends an 11. Npcf_AMPolicyControl_Update Response (privateSnssai) to the public network AMF. It indicates that the privateSnssai is carried in the Npcf_AMPolicyControl_Update Response.

[0236] The public network AMF sends a 12. Registration Accept to the private network terminal.

[0237] The private network terminal sends a 12a. Registration Complete to the public network AMF. It is represented by a dotted line in the figure, indicating that this step can be executed or not.

[0238] The public network AMF sends a 13.Nnssf_NSSelection_Get Request (requestedNssai = S-NSSAI-x) to the public network NSSF. This indicates that the value of requestedNssai carried in the Nnssf_NSSelection_Get Request is S-NSSAI-x.

[0239] The public network NSSF sends a 14.Nnssf_NSSelection_Get Response to the public network AMF.

[0240] The public network AMF sends a 15a.Deregistration Request to the private network terminal.

[0241] The private network terminal sends a 15b.Deregistration Accept to the public network AMF.

[0242] The public network AMF sends a 15c.UE CONTEXT RELEASE COMMAND to the private network base station.

[0243] The private network base station sends a 15d.UE CONTEXT RELEASE COMPLETE to the public network AMF.

[0244] The private network terminal sends a 16.Registration Request to the public network AMF.

[0245] After that, the public network AMF can make the private network AMF receive the third message through Case 1 or Case 2.

[0246] In Case 1, direct redirection between AMFs, including Step 17 - Step 19.

[0247] The public network AMF sends a 17.Nnrf_NFDiscovery Request to the public network NRF.

[0248] The public network NRF sends an 18.Nnrf_NFDiscovery Response to the public network AFM.

[0249] The public network AMF sends a 19.Namf_Communication_N1MessageNotify Request to the private network AMF.

[0250] In Case 2, redirection is based on the RAN (Radio Access Network), including Step 20 - Step 21.

[0251] The public network AMF sends a 20.REROUTE NAS REQUEST to the private network base station.

[0252] The private network base station sends a 21.INITIAL UE MESSAGE (Registration Request) to the private network AMF. It means that the Registration Request is carried in the INITIAL UE MESSAGE, that is, the second registration request is carried. The INITIAL UE MESSAGE is the fourth message sent by the aforementioned first base station to the private network AMF.

[0253] After that, the process of the private network terminal completing registration and access in the private network AMF is executed, including steps 22a - 22c.

[0254] The private network terminal, the public network base station, the public network AMF, the public network UDM, the public network AUSF, the public network PCF, the public network NSSF, the public network NRF, and the private network AMF jointly execute step 22a. The security authentication process, the access and mobility subscription data acquisition process of the private network AMF.

[0255] The private network AMF sends a 22b.Registration Accept to the private network terminal.

[0256] The private network terminal sends a 22c.Registration Complete to the private network AMF.

[0257] The above specific implementation manners can be referred to the previous description and will not be elaborated here.

[0258] The following describes the process of the private network terminal re - registering after the expiration of the temporary identifier in the first area through a complete embodiment.

[0259] See Figure 5 , which is the schematic diagram of the second terminal access process provided by the embodiment of the present application.

[0260] The figure includes a private network terminal, a public network AMF, a public network UDM, a public network AUSF, a public network PCF, a public network NSSF, a public network NRF, a private network AMF, and a private network base station.

[0261] The private network terminal sends a 1.Registration Request to the public network AMF.

[0262] The private network terminal, the public network AMF, the public network UDM, and the public network AUSF jointly execute 2. The security authentication process, the access and mobility subscription data acquisition process of the public network AMF.

[0263] The public network AMF performs 3.PCF selection. After selecting the public network PCF, the public network AMF sends a 4.Npcf_AMPolicyControl_Create Request to the public network PCF.

[0264] The public network PCF feeds back a 5.Npcf_AMPolicyControl_Create Request(pras=TAIList-x) to the public network AMF. It indicates that the value of the pras attribute in the Npcf_AMPolicyControl_Create Request is TAIList-x.

[0265] The public network AMF sends a 6.Npcf_AMPolicyControl_Update Request to the public network PCF.

[0266] The public network PCF feeds back a 7.Npcf_AMPolicyControl_Update Response(privateSnssai) to the public network AMF. It indicates that the privateSnssai is carried in the Npcf_AMPolicyControl_Update Response.

[0267] The public network AMF sends an 8.Registration Accept to the private network terminal.

[0268] The private network terminal sends an 8a.Registration Complete to the public network AMF.

[0269] The public network AMF sends a 9.Nnssf_NSSelection_Get Request(requestedNssai=S-NSSAI-x) to the public network NSSF. It indicates that the value of the requestedNssai carried in the Nnssf_NSSelection_Get Request is S-NSSAI-x.

[0270] The public network NSSF sends a 10.Nnssf_NSSelection_Get Response to the public network AMF.

[0271] The public network AMF sends an 11a.Deregistration Request to the private network terminal.

[0272] The private network terminal sends an 11b.Deregistration Accept to the public network AMF.

[0273] The public network AMF sends a 11c.UE CONTEXT RELEASE COMMAND to the private network base station.

[0274] The private network base station sends a 11d.UE CONTEXT RELEASE COMPLETE to the public network AMF.

[0275] The private network terminal sends a 12.Registration Request to the public network AMF.

[0276] After that, the public network AMF can enable the private network AMF to receive the third message through Case 1 or Case 2.

[0277] In Case 1, direct redirection between AMFs is included, which includes steps 13 - 15.

[0278] The public network AMF sends a 13.Nnrf_NFDiscovery Request to the public network NRF.

[0279] The public network NRF sends a 14.Nnrf_NFDiscovery Response to the public network AFM.

[0280] The public network AMF sends a 15.Namf_Communication_N1MessageNotify Request to the public network NRF.

[0281] In Case 2, redirection is based on the RAN, which includes steps 16 - 17.

[0282] The public network AMF sends a 16.REROUTE NAS REQUEST to the private network base station.

[0283] The private network base station sends a 17.INITIAL UE MESSAGE(Registration Request) to the private network AMF. It means that the Registration Request is carried in the INITIAL UE MESSAGE, that is, the second registration request is carried. The INITIAL UE MESSAGE is the fourth message sent by the aforementioned first base station to the private network AMF.

[0284] After that, the process of the private network terminal completing registration and access in the private network AMF is executed, including steps 18a - 18c.

[0285] The private network terminal, the public network AMF, the public network UDM, the public network AUSF, the public network PCF, the public network NSSF, the public network NRF, and the private network AMF jointly execute step 18a. The security authentication process, the access and mobility subscription data acquisition process of the private network AMF.

[0286] The private network AMF sends 18b.Registration Accept to the private network terminal.

[0287] The private network terminal sends 18c.Registration Complete to the private network AMF.

[0288] For the specific implementation manners above, reference can be made to the descriptions in the foregoing text, which will not be elaborated herein.

[0289] Corresponding to the foregoing hybrid networking terminal registration method, an embodiment of this application further provides a hybrid networking terminal registration method applied to a private network AMF.

[0290] See Figure 6 , which is a schematic flowchart of a second hybrid networking terminal registration method provided by an embodiment of this application, and is applied to the access and mobility management function network element AMF in a hybrid networking system. The hybrid networking system includes a private network networking and a public network networking. Network elements in the private network networking subscribe to private network slices, and the private network networking includes a private network AMF;

[0291] Network elements in the public network networking subscribe to public network slices, and the public network networking includes a public network AMF;

[0292] The method includes the following steps S601 - step S603.

[0293] S601: Receive the context information of the private network terminal and a second registration request.

[0294] Among them, the context information of the private network terminal and the second registration request are as follows: they are sent by the public network AMF after receiving the second registration request sent by the private network terminal; the second registration request is: sent by the private network terminal after receiving the re-registration request sent by the public network AMF; the re-registration request is: sent by the public network AMF after receiving the first registration request sent by the private network terminal, when it is determined based on the first identifier that the private network terminal is currently located in the first area served by the private network slice and the AMF providing services for the private network slice is not the public network AMF; the private network terminal subscribes to the public network slice and the private network slice, and both the public network slice and the private network slice are default slices, and the first registration request includes the first identifier of the area where the private network terminal is currently located;

[0295] S602: Complete the registration of the private network terminal based on the context information and the second registration request.

[0296] S603: Send a registration acceptance message for the second registration request to the private network terminal.

[0297] This registration receipt message indicates that the above-mentioned private network terminal is allowed to access the above-mentioned private network slice, and indicates that the above-mentioned private network terminal is denied access to the above-mentioned public network slice when it is located in the first area served by the above-mentioned private network slice.

[0298] As can be seen from the above, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will still judge whether the private network terminal is located within the first area served by the private network slice based on the first identifier of the current area where the private network terminal is located. If so, and after the public network AMF determines that it is not the AMF providing services for the private network slice, it will actively initiate a re-registration request to the private network terminal. And when the private network terminal re-sends the second registration request after re-registration, it will actively send information so that the private network AMF can receive the context information and the second registration request of the private network terminal, and complete the registration process with the private network terminal. That is, in this application, even if the public network AMF can complete the registration of the private network terminal as the default AMF, it will not cause the private network terminal to always be registered in the public network AMF. Instead, when the private network terminal is located within the first area served by the private network slice, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, after the private network AMF receives the context information and the second registration request of the private network terminal, it will not only determine the public network slice as the default slice, causing the private network terminal to re-register to the public network AMF, but will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), enabling the private network terminal to register to the private network AMF and then access the private network for communication.

[0299] In one embodiment of the present application, the receiving the context information and the second registration request of the private network terminal includes:

[0300] Directly receiving a third message from the public network AMF, where the third message contains the context information of the private network terminal and the second registration request;

[0301] Or

[0302] Receiving a fourth message from the first base station, where the fourth message is: after the first base station receives the fourth message, it sends it to the private network AMF corresponding to the second identifier, and the fourth message contains the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request.

[0303] In one embodiment of the present application, the first registration request is sent by the private network terminal after moving from outside the first area to inside the first area, or is sent by the private network terminal when it is inside the first area and the temporary identifier of the private network terminal expires.

[0304] Corresponding to the foregoing method for registering a hybrid networking terminal, an embodiment of the present application further provides a method for registering a hybrid networking terminal applied to a public network AMF.

[0305] See Figure 7 , which is a schematic flowchart of a third method for registering a hybrid networking terminal provided by an embodiment of the present application, applied to a public network access and mobility management function network element AMF in a hybrid networking system. The hybrid networking system includes a private network networking and a public network networking. Network elements in the private network networking subscribe to private network slices, and the private network networking includes a private network AMF;

[0306] Network elements in the public network networking subscribe to public network slices, and the public network networking includes a public network AMF;

[0307] The method includes the following steps S701-S703.

[0308] S701: Receive a first registration request sent by a private network terminal.

[0309] The private network terminal subscribes to a public network slice and a private network slice, and both the public network slice and the private network slice are default slices. The first registration request includes a first identifier of the area where the private network terminal is currently located.

[0310] S702: When it is determined based on the foregoing first identifier that the private network terminal is currently located in a first area served by the foregoing private network slice and the AMF providing services for the foregoing private network slice is not the foregoing public network AMF, send a reregistration request to the foregoing private network terminal, and instruct the base station to which the foregoing private network terminal is currently connected to release its connection with the foregoing private network terminal.

[0311] S703: Receive a second registration request sent by the foregoing private network terminal, and send the context information of the foregoing private network terminal and the second registration request to the foregoing private network AMF, so that the foregoing private network AMF completes the registration of the foregoing private network terminal based on the received context information and the second registration request sent by the foregoing public network AMF, and send a registration acceptance message for the second registration request to the foregoing private network terminal.

[0312] The registration acceptance message indicates that the foregoing private network terminal is allowed to access the foregoing private network slice, and indicates that the foregoing private network terminal is denied access to the foregoing public network slice when it is located in the first area served by the foregoing private network slice.

[0313] As can be seen from the above, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will determine whether the private network terminal is located within the first area of the private network slice service based on the first identifier of the area where the private network terminal is currently located. If so, and after the public network AMF determines that it is not the AMF providing services for the private network slice, it will actively initiate a re-registration request for the private network terminal. And in the case where the private network terminal re-sends the second registration request after re-registration, it will actively send information so that the private network AMF receives the context information and the second registration request of the private network terminal, and completes the registration process with the private network terminal. That is, in the present application, even if the public network AMF can complete the registration of the private network terminal as the default AMF, it will not cause the private network terminal to always register in the public network AMF. Instead, when the private network terminal is located within the first area of the private network slice service, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, after the private network AMF receives the context information and the second registration request of the private network terminal, it will not only determine the public network slice as the default slice, causing the private network terminal to register to the public network AMF again. Instead, it will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), enabling the private network terminal to register to the private network AMF and then access the private network for communication.

[0314] In one embodiment of the present application, the public network architecture further includes: a public network policy control function network element PCF, and the correspondence between the first slice identifier of the private network slice and at least one first area identifier is configured in the public network PCF, and the at least one first area identifier corresponds one-to-one to at least one first area served by the private network slice;

[0315] The determining that the private network terminal is currently located in the first area served by the private network slice based on the first identifier includes:

[0316] Determining whether the first identifier is included in the at least one first area identifier, where the at least one first area identifier is sent by the public network PCF to the public network AMF after determining that the private network terminal has subscribed to the private network slice based on the configured correspondence; if the first identifier is included in the at least one first area identifier, it is determined that the private network terminal is currently located in the first area served by the private network slice.

[0317] In one embodiment of the present application, after determining that the private network terminal is currently located in the first area served by the private network slice, it further includes:

[0318] Send a first message to the public PCF, where the first message indicates that the private network terminal is currently located in the first area served by the private network slice, so that after the public PCF receives the first message, it sends the corresponding relationship between the first slice identifier and the at least one first area identifier to the public AMF; if the public AMF completes the registration of the private network terminal, based on the corresponding relationship, send a registration acceptance message for the first registration request to the private network terminal, and the registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when located in the first area.

[0319] In an embodiment of the present application, the public network architecture further includes a public network network slice selection function network element NSSF, and a second identifier of the private network AMF is registered in the public NSSF; the AMF that provides services for the private network slice is determined not to be the public AMF in the following manner:

[0320] Send a second message to the public NSSF, where the second message is used to query the second identifier of the private network AMF, so that the public NSSF sends the second identifier to the public AMF in response to the second message; the public AMF determines whether the second identifier is its own identifier, and if the second identifier is not its own identifier, it is determined that the AMF that provides services for the private network slice is not the public AMF.

[0321] In an embodiment of the present application, the sending the context information of the private network terminal and the second registration request to the private network AMF includes:

[0322] Directly send a third message to the private network AMF, where the third message contains the context information of the private network terminal and the second registration request; or

[0323] Send a fourth message to the first base station to which the private network terminal is currently connected, where the fourth message contains the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request, so that the first base station sends the fourth message to the private network AMF corresponding to the second identifier.

[0324] In an embodiment of the present application, the public network architecture further includes a public network network repository function network element NRF, and a uniform resource identifier URI of the private network AMF is registered in the public NRF. The directly sending the third message to the private network AMF includes:

[0325] Obtain the URI of the private network AMF from the public NRF, and send the third message to the private network AMF through the URI.

[0326] In one embodiment of the present application, the first registration request is sent by the private network terminal after moving from outside the first region to inside the first region, or is sent by the private network terminal inside the first region when the temporary identifier of the private network terminal becomes invalid.

[0327] In one embodiment of the present application, the method further includes:

[0328] Receiving a third registration request sent by a private network terminal, where the third registration request includes a first identifier of the region where the private network terminal is currently located. When it is determined based on the first identifier that the private network terminal is currently outside the first region, completing the registration of the private network terminal based on the third registration request, and sending a registration reception message for the third registration request to the private network terminal, where the registration reception message indicates that the private network terminal is allowed to access the public network slice, and indicates that the private network terminal refuses to be accessed to the private network slice when it is located in the first region served by the private network slice.

[0329] Corresponding to the foregoing hybrid networking terminal registration method, an embodiment of the present application further provides a hybrid networking terminal registration method applied to a public network PCF.

[0330] See Figure 8 , which is a flowchart of the fourth hybrid networking terminal registration method provided by an embodiment of the present application, applied to a public network policy control function network element PCF. In the public network PCF, a correspondence relationship between a first slice identifier of a private network slice and at least one first region identifier is configured, and the at least one first region identifier corresponds one-to-one to at least one first region served by the private network slice. The public network PCF is included in a public network, the public network is included in a hybrid networking system, the hybrid networking system further includes a private network, network elements in the private network subscribe to the private network slice, and the private network includes a private network access and mobility management function network element AMF;

[0331] Network elements in the public network subscribe to the public network slice, and the public network includes a public network AMF;

[0332] The method includes the following steps S801 - step S802.

[0333] S801: Determine whether the private network terminal has subscribed to the above-mentioned private network slice.

[0334] The private network terminal is a terminal that sends a first registration request to the public network AMF. The private network terminal subscribes to the public network slice and the private network slice, and both the public network slice and the private network slice are default slices. The first registration request includes a first identifier of the region where the private network terminal is currently located;

[0335] S802: If it is determined that the above-mentioned private network terminal has subscribed to the above-mentioned private network slice, based on the configured corresponding relationship, send the above-mentioned at least one first area identifier to the public network AMF, so that the public network AMF determines whether the above-mentioned first identifier is included in the above-mentioned at least one first area identifier. If the above-mentioned first identifier is included in the above-mentioned at least one first area identifier, it is determined that the private network terminal is currently located in the first area served by the above-mentioned private network slice, and when it is determined that the AMF providing services for the above-mentioned private network slice is not the above-mentioned public network AMF, send a reregistration request to the above-mentioned private network terminal, and instruct the base station to which the above-mentioned private network terminal is currently connected to release its connection with the above-mentioned private network terminal; and enable the above-mentioned public network AMF to receive the second registration request sent by the above-mentioned private network terminal, send the context information of the above-mentioned private network terminal and the second registration request to the above-mentioned private network AMF, and enable the above-mentioned private network AMF to complete the registration of the above-mentioned private network terminal based on the received context information and second registration request sent by the above-mentioned public network AMF, and send a registration acceptance message for the above-mentioned second registration request to the above-mentioned private network terminal.

[0336] This registration acceptance message indicates that the above-mentioned private network terminal is allowed to access the above-mentioned private network slice, and indicates that the above-mentioned private network terminal is refused to access the above-mentioned public network slice when it is located in the first area served by the above-mentioned private network slice.

[0337] As can be seen from the above, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will also judge whether the private network terminal is located in the first area served by the private network slice based on the first identifier of the area where the private network terminal is currently located. If so, and after the public network AMF determines that it is not the AMF providing services for the private network slice, it will actively initiate a reregistration request for the private network terminal. And when the private network terminal resends the second registration request after reregistration, it will actively send information so that the private network AMF receives the context information and the second registration request of the private network terminal, and completes the registration process with the private network terminal. That is to say, even if the public network AMF can complete the registration of the private network terminal as the default AMF in this application, it will not cause the private network terminal to always register in the public network AMF. Instead, when the private network terminal is located in the first area served by the private network slice, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, the private network AMF will not only determine the public network slice as the default slice after receiving the context information and the second registration request of the private network terminal, causing the private network terminal to register to the public network AMF again, but will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), so that the private network terminal can register to the private network AMF and then access the private network for communication.

[0338] In one embodiment of the present application, the method further includes:

[0339] Receiving a first message sent by the public network AMF, where the first message is sent by the public network AMF after determining that the network terminal is currently located in the first area served by the private network slice, and the first message indicates that the private network terminal is currently located in the first area served by the private network slice;

[0340] Sending the correspondence between the first slice identifier and the at least one first area identifier to the public network AMF, so that if the public network AMF completes the registration of the private network terminal, based on the correspondence, a registration acceptance message for the first registration request is sent to the private network terminal, and the registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when located in the first area.

[0341] Corresponding to the foregoing hybrid networking terminal registration method, an embodiment of the present application further provides a communication device serving as a public network AMF.

[0342] See Figure 9 , which is a schematic structural diagram of the first communication device provided by an embodiment of the present application. The communication device includes:

[0343] A processor 901;

[0344] A memory 902 for storing instructions executable by the processor;

[0345] Wherein, the processor 901 is configured to execute the method steps of any of the hybrid networking terminal registration methods applied to the public network AMF according to the executable instructions.

[0346] As Figure 9 shown, the wireless access point may further include a communication bus 903. The processor 901 and the memory 902 communicate with each other through the communication bus 903. The communication bus 903 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus 903 may be divided into an address bus, a data bus, a control bus, etc.

[0347] The memory 902 may include a Random Access Memory (RAM), or may also include a Non-Volatile Memory (NVM), such as at least one disk memory. Additionally, the memory 902 may also be at least one storage device located far away from the aforementioned processor.

[0348] The processor 901 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0349] As can be seen from the above, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will determine whether the private network terminal is located within the first area of the private network slice service based on the first identifier of the area where the private network terminal is currently located. If so, and after the public network AMF determines that it is not the AMF providing services for the private network slice, it will actively initiate a re-registration request for the private network terminal. And in the case where the private network terminal re-sends the second registration request after re-registration, it will actively send information so that the private network AMF receives the context information and the second registration request of the private network terminal, and completes the registration process with the private network terminal. That is, in the present application, even if the public network AMF can complete the registration of the private network terminal as the default AMF, it will not cause the private network terminal to always be registered in the public network AMF. Instead, when the private network terminal is located within the first area of the private network slice service, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, after the private network AMF receives the context information and the second registration request of the private network terminal, it will not only determine the public network slice as the default slice, causing the private network terminal to be registered to the public network AMF again. Instead, it will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), enabling the private network terminal to be registered to the private network AMF and then access the private network for communication.

[0350] Corresponding to the aforementioned method for registering a hybrid networking terminal, an embodiment of the present application further provides a communication device acting as a private network AMF.

[0351] See Figure 10 , which is a schematic structural diagram of a second communication device provided by an embodiment of the present application. The communication device includes:

[0352] A processor 1001;

[0353] A memory 1002 for storing instructions executable by the processor;

[0354] Wherein, the processor 1001 is configured to execute any of the method steps of the hybrid networking terminal registration method applied to the private network AMF according to the executable instructions.

[0355] As Figure 10 shown, the wireless access point may further include a communication bus 1003. Communication between the processor 1001 and the memory 1002 is completed through the communication bus 1003. The communication bus 1003 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 1003 may be divided into an address bus, a data bus, a control bus, etc.

[0356] The memory 1002 may include a Random Access Memory (RAM), or may also include a Non-Volatile Memory (NVM), such as at least one disk memory. In addition, the memory 1002 may also be at least one storage device located far from the aforementioned processor.

[0357] The processor 1001 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0358] As can be seen from the above, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will determine whether the private network terminal is located within the first area of the private network slice service based on the first identifier of the area where the private network terminal is currently located. If so, and after the public network AMF determines that it is not the AMF providing services for the private network slice, it will actively initiate a re-registration request for the private network terminal. And when the private network terminal re-sends the second registration request after re-registration, it will actively send information so that the private network AMF receives the context information and the second registration request of the private network terminal, and completes the registration process with the private network terminal. That is, in this application, even if the public network AMF can complete the registration of the private network terminal as the default AMF, it will not cause the private network terminal to always register in the public network AMF. Instead, when the private network terminal is located within the first area of the private network slice service, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, after the private network AMF receives the context information and the second registration request of the private network terminal, it will not only determine the public network slice as the default slice, causing the private network terminal to register to the public network AMF again. Instead, it will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), enabling the private network terminal to register to the private network AMF and then access the private network for communication.

[0359] Corresponding to the aforementioned hybrid networking terminal registration method, an embodiment of the present application also provides a communication device as a public network PCF.

[0360] See Figure 11 , which is a schematic structural diagram of a third communication device provided by an embodiment of the present application. The communication device includes:

[0361] A processor 1101;

[0362] A memory 1102 for storing executable instructions of the processor;

[0363] Wherein, the processor is configured to execute the method steps of any one of the fourth aspect according to the executable instructions.

[0364] Such as Figure 11As shown, the wireless access point may further include a communication bus 1103. The processor 1101 and the memory 1102 communicate with each other through the communication bus 1103. The communication bus 1103 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 1103 may be divided into an address bus, a data bus, a control bus, etc.

[0365] The memory 1102 may include a Random Access Memory (RAM), and may also include a Non-Volatile Memory (NVM), such as at least one disk memory. Additionally, the memory 1102 may also be at least one storage device located far from the aforementioned processor.

[0366] The processor 1101 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0367] As can be seen from the above, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will still determine whether the private network terminal is located within the first area of the private network slice service based on the first identifier of the area where the private network terminal is currently located. If so, and after the public network AMF determines that it is not the AMF providing services for the private network slice, it will actively initiate a re-registration request for the private network terminal. And in the case where the private network terminal re-sends the second registration request after re-registration, it will actively send information so that the private network AMF can receive the context information and the second registration request of the private network terminal, and complete the registration process with the private network terminal. That is to say, in this application, even if the public network AMF can complete the registration of the private network terminal as the default AMF, it will not cause the private network terminal to always register in the public network AMF. Instead, when the private network terminal is located within the first area of the private network slice service, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, after the private network AMF receives the context information and the second registration request of the private network terminal, it will not only determine the public network slice as the default slice, causing the private network terminal to register to the public network AMF again. Instead, it will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), enabling the private network terminal to register to the private network AMF and then access the private network for communication.

[0368] Corresponding to the aforementioned hybrid networking terminal registration method, an embodiment of the present application further provides a hybrid networking system.

[0369] An embodiment of the present application provides a hybrid networking system, which includes a private network networking and a public network networking. The network elements in the private network networking subscribe to the private network slice, and the private network networking includes private network access and a mobility management function network element AMF;

[0370] The network elements in the public network networking subscribe to the public network slice, and the public network networking includes a public network AMF;

[0371] The public network AMF is configured to receive the first registration request sent by the private network terminal, where the first registration request includes the first identifier of the area where the private network terminal is currently located; when it is determined based on the first identifier that the private network terminal is currently located in the first area served by the private network slice and the AMF providing services for the private network slice is not the public network AMF, send a re-registration request to the private network terminal, and instruct the base station to which the private network terminal is currently connected to release its connection with the private network terminal; the private network terminal subscribes to the public network slice and the private network slice, and both the public network slice and the private network slice are default slices;

[0372] The public network AMF is further configured to receive a second registration request sent by the private network terminal, and send the context information of the private network terminal and the second registration request to the private network AMF;

[0373] The private network AMF is configured to complete the registration of the private network terminal based on the received context information and the second registration request sent by the public network AMF, and send a registration reception message for the second registration request to the private network terminal. The registration reception message indicates that the private network terminal is allowed to access the private network slice, and indicates that the private network terminal is denied access to the public network slice when it is located in the first area served by the private network slice.

[0374] As can be seen from the above, even if the public network AMF receives the first registration request sent by the private network terminal as the default AMF, the public network AMF will determine whether the private network terminal is located in the first area served by the private network slice based on the first identifier of the current area where the private network terminal is located. If so, and after the public network AMF determines that it is not the AMF serving the private network slice, it will actively initiate a re-registration request for the private network terminal. And in the case where the private network terminal re-sends the second registration request after re-registration, it will actively send information so that the private network AMF receives the context information and the second registration request of the private network terminal, and completes the registration process with the private network terminal. That is, in the present application, even if the public network AMF can complete the registration of the private network terminal as the default AMF, it will not cause the private network terminal to always register in the public network AMF. Instead, when the private network terminal is located in the first area served by the private network slice, it will send the context information and the second registration request of the private network terminal to the private network AMF, and actively initiate the registration of the private network terminal to the private network AMF. The private network AMF can re-autonomously decide the slice that the private network terminal can use. Since both the public network slice and the private network slice are default slices for the private network terminal, after the private network AMF receives the context information and the second registration request of the private network terminal, it will not only determine the public network slice as the default slice, causing the private network terminal to register to the public network AMF again. Instead, it will autonomously decide the slice that the private network terminal can use (the private network slice in the current scenario), so that the private network terminal can register to the private network AMF and then access the private network for communication.

[0375] In an embodiment of the present application, the public network architecture further includes: a public network policy control function network element PCF. In the public network PCF, the corresponding relationship between the first slice identifier of the private network slice and at least one first area identifier is configured, and the at least one first area identifier corresponds one-to-one to at least one first area served by the private network slice;

[0376] The public network PCF is configured to, after determining that the private network terminal has subscribed to the private network slice, send the at least one first area identifier to the public network AMF based on the configured corresponding relationship;

[0377] The public AMF is further configured to:

[0378] Determine whether the first identifier is included in the at least one first area identifier; if the first identifier is included in the at least one first area identifier, determine that the private network terminal is currently located in the first area served by the private network slice.

[0379] In one embodiment of the present application, the public AMF is further configured to:

[0380] After determining that the private network terminal is currently located in the first area served by the private network slice, send a first message to the public PCF, where the first message indicates that the private network terminal is currently located in the first area served by the private network slice;

[0381] The public PCF is configured to, after receiving the first message, send the corresponding relationship between the first slice identifier and the at least one first area identifier to the public AMF;

[0382] The public AMF is specifically configured to, if the public AMF completes the registration of the private network terminal, based on the corresponding relationship, send a registration acceptance message for the first registration request to the private network terminal, and the registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when located in the first area.

[0383] In one embodiment of the present application, the public network also includes a public network network slice selection function network element NSSF, and a second identifier of the private network AMF is registered in the public NSSF;

[0384] The public AMF is specifically configured to:

[0385] Send a second message to the public NSSF, where the second message is used to query the second identifier of the private network AMF;

[0386] The public NSSF is configured to, in response to the second message, send the second identifier to the public AMF;

[0387] The public AMF is specifically configured to determine whether the second identifier is its own identifier, and if the second identifier is not its own identifier, determine that the AMF providing services for the private network slice is not the public AMF.

[0388] In one embodiment of the present application, the public AMF is specifically configured to directly send a third message to the private network AMF, where the third message includes the context information of the private network terminal and the second registration request; or

[0389] The public network AMF is specifically configured to send a fourth message to the first base station to which the private network terminal is currently connected. The fourth message includes a second identifier of the private network AMF, context information of the private network terminal, and the second registration request.

[0390] The first base station is configured to send the fourth message to the private network AMF corresponding to the second identifier.

[0391] In an embodiment of the present application, the public network also includes a public network network repository function network element NRF. The uniform resource identifier URI of the private network AMF is registered in the public network NRF. The public network AMF is specifically configured to:

[0392] Obtain the URI of the private network AMF from the public network NRF, and send a third message to the private network AMF through the URI.

[0393] As can be seen from the above, if the public network AMF and the private network AMF can be directly redirected, the public network AMF can directly send a third message to the private network AMF.

[0394] In an embodiment of the present application, the first registration request is sent by the private network terminal after moving from outside the first area to inside the first area, or after the private network terminal is restarted inside the first area.

[0395] In an embodiment of the present application, the public network AMF is further configured to:

[0396] Receive a third registration request sent by the private network terminal. The third registration request includes a first identifier of the area where the private network terminal is currently located. When it is determined based on the first identifier that the private network terminal is currently outside the first area, complete the registration of the private network terminal based on the third registration request, and send a registration reception message for the third registration request to the private network terminal. The registration reception message indicates that the private network terminal is allowed to access the public network slice, and indicates that the private network terminal is refused access to the private network slice when it is located in the first area served by the private network slice.

[0397] As can be seen from the above, the solution provided by the embodiment of the present application also supports the private network terminal to access the public network AMF outside the first area served by the private network slice. Whether the private network terminal registers for the first time outside the first area, or the private network terminal moves from inside the first area to outside the first area, or the private network terminal is outside the first area and the temporary identifier of the private network terminal fails, it can ensure that the private network terminal completes the registration normally and realizes normal network access.

[0398] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0399] It should be noted that in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including", or any other variation thereof is intended to cover non-exclusive inclusion, so that a process, method, article, or device that includes a series of elements includes not only those elements but also other elements that are not explicitly listed, or also includes elements that are inherent to such process, method, article, or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article, or device that includes the element.

[0400] Each embodiment in this specification is described in a related manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the embodiment of the hybrid networking system, since it is basically similar to the method embodiment, the description is relatively simple, and reference can be made to the partial description of the method embodiment for the relevant parts.

[0401] The foregoing are only the preferred embodiments of the present application and are not intended to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application are all included in the protection scope of the present application.

Claims

1. A method for registering a hybrid networking terminal, characterized in that, Applied to a hybrid networking system, the hybrid networking system includes a private network networking and a public network networking. The network elements in the private network networking subscribe to private network slices, and the private network networking includes private network access and a mobility management function network element AMF; The network elements in the public network networking subscribe to public network slices, and the public network networking includes a public network AMF; The method includes: The public network AMF receives a first registration request sent by a private network terminal. The private network terminal subscribes to a public network slice and a private network slice, and both the public network slice and the private network slice are default slices. The first registration request includes a first identifier of the area where the private network terminal is currently located; When the public network AMF determines based on the first identifier that the private network terminal is currently located in a first area served by the private network slice and the AMF providing services for the private network slice is not the public network AMF, the public network AMF sends a re-registration request to the private network terminal and instructs the base station to which the private network terminal is currently connected to release its connection with the private network terminal; The public network AMF receives a second registration request sent by the private network terminal, and sends the context information of the private network terminal and the second registration request to the private network AMF; The private network AMF completes the registration of the private network terminal based on the received context information and the second registration request sent by the public network AMF, and sends a registration acceptance message for the second registration request to the private network terminal. The registration acceptance message indicates that the private network terminal is allowed to access the private network slice and indicates that the private network terminal is rejected from accessing the public network slice when it is located in the first area served by the private network slice.

2. The method according to claim 1, wherein The public network networking further includes: a public network policy control function network element PCF. In the public network PCF, the corresponding relationship between the first slice identifier of the private network slice and at least one first area identifier is configured. The at least one first area identifier corresponds one-to-one to at least one first area served by the private network slice; The method further includes: After the public network PCF determines that the private network terminal has subscribed to the private network slice, based on the configured corresponding relationship, the public network PCF sends the at least one first area identifier to the public network AMF; The public network AMF determines whether the first identifier is included in the at least one first area identifier; if the first identifier is included in the at least one first area identifier, it is determined that the private network terminal is currently located in the first area served by the private network slice.

3. The method according to claim 2, characterized in that, After determining that the private network terminal is currently located in the first area served by the private network slice, it further includes: The public network AMF sends a first message to the public network PCF, and the first message indicates that the private network terminal is currently located in the first area served by the private network slice; After receiving the first message, the public network PCF sends the corresponding relationship between the first slice identifier and the at least one first area identifier to the public network AMF; If the public network AMF completes the registration of the private network terminal, based on the corresponding relationship, a registration acceptance message for the first registration request is sent to the private network terminal, and the registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when located in the first area.

4. The method according to claim 1, wherein The public network networking also includes a public network network slice selection function network element NSSF, and a second identifier of the private network AMF is registered in the public network NSSF; The method further includes: The public network AMF sends a second message to the public network NSSF, and the second message is used to query the second identifier of the private network AMF; In response to the second message, the public network NSSF sends the second identifier to the public network AMF; The public network AMF determines whether the second identifier is its own identifier. If the second identifier is not its own identifier, it is determined that the AMF providing services for the private network slice is not the public network AMF.

5. The method according to claim 1, characterized in that, The sending the context information of the private network terminal and the second registration request to the private network AMF includes: The public network AMF directly sends a third message to the private network AMF, and the third message includes the context information of the private network terminal and the second registration request; or The public network AMF sends a fourth message to the first base station to which the private network terminal currently accesses, and the fourth message includes the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request; The first base station sends the fourth message to the private network AMF corresponding to the second identifier.

6. The method according to claim 5, wherein The public network networking also includes a public network network repository function network element NRF, and a uniform resource identifier URI of the private network AMF is registered in the public network NRF. The public network AMF directly sending a third message to the private network AMF includes: The public network AMF obtains the URI of the private network AMF from the public network NRF and sends the third message to the private network AMF through the URI.

7. The method according to any one of claims 1-6, characterized in that, The first registration request is sent by the private network terminal after moving from outside the first area to inside the first area, or is sent by the private network terminal inside the first area and after the temporary identifier of the private network terminal expires.

8. The method according to any one of claims 1-6, characterized in that, The method further includes: The public network AMF receives a third registration request sent by the private network terminal. The third registration request includes a first identifier of the area where the private network terminal is currently located. When it is determined based on the first identifier that the private network terminal is currently outside the first area, the public network AMF completes the registration of the private network terminal based on the third registration request, and sends a registration acceptance message for the third registration request to the private network terminal. The registration acceptance message indicates that the private network terminal is allowed to access the public network slice, and indicates that the private network terminal is refused access to the private network slice when located in the first area served by the private network slice.

9. A method for registering a hybrid networking terminal, characterized in that The Access and Mobility Management Function Network Element AMF applied to the hybrid networking system, where the hybrid networking system includes a private network networking and a public network networking, the network elements in the private network networking subscribe to the private network slice, and the private network networking includes a private network AMF; The network elements in the public network networking subscribe to the public network slice, and the public network networking includes a public network AMF; The method includes: Receiving the context information of the private network terminal and the second registration request; Wherein, the context information of the private network terminal and the second registration request are: sent by the public network AMF after receiving the second registration request sent by the private network terminal; the second registration request is: sent by the private network terminal after receiving the re-registration request sent by the public network AMF; the re-registration request is: sent by the public network AMF after receiving the first registration request sent by the private network terminal, and when it is determined based on the first identifier that the private network terminal is currently located in the first area served by the private network slice and the AMF providing services for the private network slice is not the public network AMF; the private network terminal subscribes to the public network slice and the private network slice, and both the public network slice and the private network slice are default slices, and the first registration request includes the first identifier of the area where the private network terminal is currently located; Completing the registration of the private network terminal based on the context information and the second registration request; Sending a registration acceptance message for the second registration request to the private network terminal, where the registration acceptance message indicates that the private network terminal is allowed to access the private network slice and indicates that the private network terminal is refused access to the public network slice when located in the first area served by the private network slice.

10. The method according to claim 9, wherein The receiving the context information of the private network terminal and the second registration request includes: Directly receiving a third message from the public network AMF, where the third message includes the context information of the private network terminal and the second registration request; Or Receiving a fourth message from the first base station, where the fourth message is: sent by the first base station to the private network AMF corresponding to the second identifier after receiving the fourth message, and the fourth message includes the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request.

11. The method according to claim 9 or 10, characterized in that, The first registration request is sent by the private network terminal after moving from outside the first area to inside the first area, or sent by the private network terminal when the temporary identifier of the private network terminal expires inside the first area.

12. A method for registering a hybrid networking terminal, characterized in that, The Access and Mobility Management Function Network Element AMF applied to the hybrid networking system, where the hybrid networking system includes a private network networking and a public network networking, the network elements in the private network networking subscribe to the private network slice, and the private network networking includes a private network AMF; The network elements in the public network networking subscribe to the public network slice, and the public network networking includes a public network AMF; The method includes: Receiving the first registration request sent by the private network terminal, where the private network terminal subscribes to the public network slice and the private network slice, and both the public network slice and the private network slice are default slices, and the first registration request includes the first identifier of the area where the private network terminal is currently located; When it is determined based on the first identifier that the private network terminal is currently located in the first area served by the private network slice and the AMF providing services for the private network slice is not the public network AMF, send a re-registration request to the private network terminal and instruct the base station to which the private network terminal is currently connected to release its connection with the private network terminal; Receive the second registration request sent by the private network terminal, and send the context information of the private network terminal and the second registration request to the private network AMF, so that the private network AMF completes the registration of the private network terminal based on the received context information and the second registration request sent by the public network AMF, and send a registration acceptance message for the second registration request to the private network terminal. This registration acceptance message indicates that the private network terminal is allowed to access the private network slice and indicates that the private network terminal is denied access to the public network slice when it is located in the first area served by the private network slice.

13. The method according to claim 12, wherein The public network also includes: a public network policy control function network element PCF. In the public network PCF, the corresponding relationship between the first slice identifier of the private network slice and at least one first area identifier is configured, and the at least one first area identifier corresponds one-to-one to at least one first area served by the private network slice; The determining that the private network terminal is currently located in the first area served by the private network slice based on the first identifier includes: Determine whether the first identifier is included in the at least one first area identifier, where the at least one first area identifier is sent by the public network PCF to the public network AMF based on the configured corresponding relationship after determining that the private network terminal has subscribed to the private network slice; If the first identifier is included in the at least one first area identifier, determine that the private network terminal is currently located in the first area served by the private network slice.

14. The method according to claim 13, wherein After determining that the private network terminal is currently located in the first area served by the private network slice, it further includes: Send a first message to the public network PCF, and the first message indicates that the private network terminal is currently located in the first area served by the private network slice, so that after receiving the first message, the public network PCF sends the corresponding relationship between the first slice identifier and the at least one first area identifier to the public network AMF; If the public network AMF completes the registration of the private network terminal, based on the corresponding relationship, send a registration acceptance message for the first registration request to the private network terminal. This registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when it is located in the first area.

15. The method according to claim 12, wherein The public network also includes a public network network slice selection function network element NSSF, and the second identifier of the private network AMF is registered in the public network NSSF; Determine that the AMF providing services for the private network slice is not the public network AMF in the following way: Send a second message to the public network NSSF, and the second message is used to query the second identifier of the private network AMF, so that the public network NSSF responds to the second message and sends the second identifier to the public network AMF; The public network AMF determines whether the second identifier is its own identifier. If the second identifier is not its own identifier, it is determined that the AMF providing services for the private network slice is not the public network AMF.

16. The method according to claim 12, wherein The sending the context information of the private network terminal and the second registration request to the private network AMF includes: directly sending a third message to the private network AMF, where the third message contains the context information of the private network terminal and the second registration request; or sending a fourth message to a first base station to which the private network terminal is currently connected, where the fourth message contains the second identifier of the private network AMF, the context information of the private network terminal, and the second registration request, so that the first base station sends the fourth message to the private network AMF corresponding to the second identifier.

17. The method according to claim 16, wherein The public network networking further includes a public network network repository function network element NRF, and the unified resource identifier URI of the private network AMF is registered in the public network NRF. The directly sending the third message to the private network AMF includes: obtaining the URI of the private network AMF from the public network NRF and sending the third message to the private network AMF through the URI.

18. The method according to any one of claims 12-17, wherein the first registration request is sent by the private network terminal after moving from outside the first region to inside the first region, or after the temporary identifier of the private network terminal expires inside the first region.

19. The method according to any one of claims 12 - 17, characterized in that, The method further includes: receiving a third registration request sent by the private network terminal, where the third registration request contains a first identifier of the region where the private network terminal is currently located. When it is determined based on the first identifier that the private network terminal is currently outside the first region, completing the registration of the private network terminal based on the third registration request, and sending a registration reception message for the third registration request to the private network terminal, where the registration reception message indicates that the private network terminal is allowed to access the public network slice and indicates that the private network terminal refuses to be accessed to the private network slice when located in the first region served by the private network slice.

20. A method for registering a hybrid networking terminal, characterized in that, Applied to a public network policy control function network element PCF, the first slice identifier of the private network slice and the corresponding relationship with at least one first region identifier are configured in the public network PCF. The at least one first region identifier corresponds one-to-one to at least one first region served by the private network slice. The public network PCF is included in the public network networking, the public network networking is included in the hybrid networking system, the hybrid networking system further includes a private network networking, network elements in the private network networking subscribe to the private network slice, and the private network networking includes a private network access and mobility management function network element AMF; Network elements in the public network networking subscribe to the public network slice, and the public network networking includes a public network AMF; The method includes: Determine whether the private network terminal has subscribed to the private network slice. The private network terminal is the terminal that sends a first registration request to the public network AMF. The private network terminal subscribes to both the public network slice and the private network slice, and both the public network slice and the private network slice are default slices. The first registration request contains a first identifier of the area where the private network terminal is currently located; If it is determined that the private network terminal has subscribed to the private network slice, then based on the configured corresponding relationship, send the at least one first area identifier to the public network AMF, so that the public network AMF determines whether the first identifier is included in the at least one first area identifier. If the first identifier is included in the at least one first area identifier, it is determined that the private network terminal is currently located in the first area served by the private network slice. And in the case where the AMF providing service for the private network slice is not the public network AMF, send a re-registration request to the private network terminal, and instruct the base station to which the private network terminal is currently connected to release its connection with the private network terminal; and enable the public network AMF to receive the second registration request sent by the private network terminal, send the context information of the private network terminal and the second registration request to the private network AMF, and enable the private network AMF to complete the registration of the private network terminal based on the received context information and the second registration request sent by the public network AMF, and send a registration acceptance message for the second registration request to the private network terminal. This registration acceptance message indicates that the private network terminal is allowed to access the private network slice, and indicates that the private network terminal is refused access to the public network slice when it is located in the first area served by the private network slice.

21. The method according to claim 20, wherein The method further includes: Receive a first message sent by the public network AMF. The first message is sent by the public network AMF after determining that the network terminal is currently located in the first area served by the private network slice. The first message indicates that the private network terminal is currently located in the first area served by the private network slice; Send the corresponding relationship between the first slice identifier and the at least one first area identifier to the public network AMF, so that if the public network AMF completes the registration of the private network terminal, then based on the corresponding relationship, send a registration acceptance message for the first registration request to the private network terminal. This registration acceptance message indicates that the private network terminal is allowed to access the private network slice and the public network slice when it is located in the first area.

22. A communication device, characterized in that, The communication device includes: A processor; A memory for storing processor-executable instructions; Wherein, the processor is configured to execute the method steps of any one of claims 9-11 according to the executable instructions.

23. A communication device, characterized in that, The communication device includes: A processor; A memory for storing processor-executable instructions; Wherein, the processor is configured to execute the method steps of any one of claims 12-19 according to the executable instructions.

24. A communication device, characterized in that, The communication device includes: A processor; A memory for storing processor-executable instructions; Wherein, the processor is configured to execute the method steps of claim 20 or 21 according to the executable instructions.

25. A hybrid networking system, characterized in that, The hybrid networking system includes a private network networking and a public network networking. The network elements in the private network networking subscribe to private network slices, and the private network networking includes a private network access and a mobility management function network element AMF; The network elements in the public network networking subscribe to public network slices, and the public network networking includes a public network AMF; The public network AMF is used to receive a first registration request sent by a private network terminal, and the first registration request includes a first identifier of the area where the private network terminal is currently located; In the case that it is determined based on the first identifier that the private network terminal is currently located in a first area served by the private network slice and the AMF providing services for the private network slice is not the public network AMF, a re-registration request is sent to the private network terminal, and it is instructed that the base station to which the private network terminal is currently connected releases its connection with the private network terminal; The private network terminal subscribes to a public network slice and a private network slice, and both the public network slice and the private network slice are default slices; The public network AMF is further used to receive a second registration request sent by the private network terminal, and send the context information of the private network terminal and the second registration request to the private network AMF; The private network AMF is used to complete the registration of the private network terminal based on the received context information and second registration request sent by the public network AMF, and send a registration acceptance message for the second registration request to the private network terminal. The registration acceptance message indicates that the private network terminal is allowed to access the private network slice, and indicates that the private network terminal is refused to access the public network slice when it is located in the first area served by the private network slice.

Images