CN113259924B - Private network subscription information updating method and device - Google Patents

Abstract

The present application provides a method and device for updating private network contract information, which are used to improve the private network contract information update process of terminal devices. The method includes: a core network device receives private network information from a first access network device, and the private network information includes the identifier of at least one private network supported by the cell used by the first access network device and the terminal device to restore the wireless resource control connection. The core network device performs verification based on the private network information and the private network contract information of the terminal device. In an embodiment of the present application, a solution is provided for the situation in which the source cell and/or the target cell are not in the private network contract information when an inactive terminal device updates the private network contract information, so that the update process of the private network contract information of the inactive terminal device can be improved.

Description

A private network contract information updating method and device

Technical Field

The present application relates to the field of communication technology, and in particular to a method and device for updating private network contract information.

Background technique

In daily life, the public network generally provides network services for terminal devices. The public network, namely the public land mobile network (PLMN), is a network established and operated by the government or its approved operators for the purpose of providing land mobile communication services to the public. In addition to the public network, operators or individuals will also build some private networks (NPN) to meet the needs of users. Private networks can also be called non-public networks, which refer to networks open to specific users, such as internal networks built by companies, schools or factories. Terminal devices that have not signed contracts with private networks are not allowed to access private networks. After the terminal device signs a contract with the private network, the core network side and the terminal device side record the contract information of the terminal device. The contract information refers to the user access information signed by the terminal device with the operator or other company that builds the private network. If the terminal device signs a contract, it can access the corresponding network according to the network identifier in the contract information and use the network resources. If the contract information changes, the core network will initiate a user equipment (UE) configuration update process (UE configuration update) to notify the terminal device side of the updated contract information.

For an inactive terminal device, for the updated subscription information, the source cell and/or the target cell may or may not be in the new subscription cell list. If the source cell and/or the target cell is not in the new subscription cell list, there is currently no good solution for how to update the subscription information in the terminal device. In particular, when the target cell is not in the new subscription cell list, the behavior of the target base station and AMF is not covered in the current communication protocol, which is a common problem in private network communications.

Summary of the invention

The present application provides a private network contract information updating method and device, which are used to improve the private network contract information updating process of a terminal device.

In the first aspect, an embodiment of the present application provides a method for updating private network contract information, including: a core network device receives private network information from a first access network device, the private network information includes at least one private network identifier supported by a cell used by the first access network device and the terminal device to restore a radio resource control (RRC) connection. The core network device performs verification based on the private network information and the private network contract information of the terminal device, and the private network contract information is saved by the core network device. In an embodiment of the present application, a solution is provided for the situation in which an INACTIVE state UE encounters a situation in which the source cell and/or the target cell are not in the private network contract information when updating the private network contract information, thereby improving the update process of the private network contract information of the terminal device in the INACTIVE state.

In one possible design, at least one private network depends on a first public network, the first public network is a public network on which a target network selected by a terminal device depends, and the network identifier of the first public network is a PLMN ID. In the above design, the first access network device can enable the core network device to verify the first access network device according to the first public network identifier and the private network identifier by reporting the first public network identifier and at least one private network identifier that depends on the first public network.

In a possible design, the private network identifier includes the public network network identifier PLMN ID and the closed access group identifier CAG ID.

In a possible design, the identifier of the private network includes a PLMN ID and a network identification code (network identification, NID).

In one possible design, the core network device performs verification based on the private network information and the private network contract information of the terminal device, including: if at least one private network identifier in the private network information belongs to the private network contract information, the verification is successful; or, if the private network identifier in the private network information does not belong to the private network contract information, the verification fails. In the above design, if the private network identifier in the private network information does not belong to the private network contract information, the core network device can determine that the first access network device does not have the access conditions for the contracted cell of the terminal device, and thus can determine that the first access network device fails the verification.

In one possible design, after the core network device receives the private network information from the first access network device, it also includes: if the private network identifier in the private network information does not belong to the private network contract information, the core network device sends a release message to the first access network device, and the release message is used to instruct the first access network device to release the RRC connection between the first access network device and the terminal device. In the above design, when the first access network device fails the verification, the resources can be released in time through the release message, thereby improving resource utilization.

In one possible design, the release message carries first indication information, and the first indication information is used to indicate that the reason for releasing the terminal device and/or the reason for the path switching failure is related to the private network contract information. Through the above design, the first access network device can obtain the reason for the path switching failure, which can be beneficial to data statistics.

In one possible design, the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the private network contract scope; unreasonable private network access. Through the above design, the first access network device can more accurately obtain the reason for the path conversion failure.

On the second aspect, an embodiment of the present application provides a method for updating private network contract information, including: a first access network device restores an RRC connection with a terminal device; the first access network device sends private network information to a core network device, the private network information including an identifier of at least one private network supported by a cell in which the first access network device and the terminal device restore an RRC connection. In an embodiment of the present application, a solution is provided for a situation in which an INACTIVE UE encounters a situation in which the source cell and/or the target cell are not in the private network contract information when updating private network contract information, thereby improving the process of updating private network contract information for a terminal device in an INACTIVE state.

In one possible design, at least one private network depends on a first public network, and the first public network is a public network on which a target network selected by a terminal device depends. In the above design, the first access network device reports a private network identifier under the first public network, so that the core network device can verify the first access network device according to the private network identifier.

In a possible design, the private network identifier includes the public network network identifier PLMN ID and the closed access group identifier CAG ID.

In one possible design, the private network identifier includes a PLMN ID and a NID.

In one possible design, after the first access network device sends the private network information to the core network device, the method further includes: the first access network device receives the private network subscription information of the terminal device. In the above design, the first access network device can obtain the private network subscription information of the terminal device after verification.

In one possible design, after the first access network device sends the private network information to the core network device, the method further includes: the first access network device receives a release message from the core network device, the release message is used to instruct the first access network device to release the RRC connection between the first access network device and the terminal device. In the above design, when the first access network device fails the verification, the release message can release the resources in time, thereby improving the resource utilization.

In one possible design, the release message carries first indication information, and the first indication information is used to indicate that the reason for releasing the terminal device and/or the reason for the path switching failure is related to the private network contract information. Through the above design, the first access network device can obtain the reason for the path switching failure, which can be beneficial to data statistics.

In one possible design, the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the private network contract scope; unreasonable private network access. Through the above design, the first access network device can more accurately obtain the reason for the path conversion failure.

In a third aspect, an embodiment of the present application provides a method for updating private network contract information, including: a second access network device receives a third message from a first access network device, and the third message is used to request context information of a terminal device from the second access network device. If at least one of the second access network device and the first access network device does not belong to a contracted cell indicated by the private network contract information, the second access network device sends a fourth message to the first access network device, and the fourth message is used to indicate that the first access network device fails to obtain the context information. The fourth message carries indication information, and the indication information is used to indicate that the reason for the failure to obtain the context information is related to the private network contract information.

The embodiment of the present application introduces a solution. When the first access network device fails to obtain the context from the second access network device, the first access network device triggers the RRC establishment process. Or the first access network device successfully obtains the context and triggers the RRC recovery process. The integrity of the communication protocol is supplemented, so that the problem that the private network contract information cannot be updated can be solved.

In one possible design, the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the private network contract scope; unreasonable private network access. Through the above design, the first access network device can more accurately obtain the reason for the path conversion failure.

In the fourth aspect, an embodiment of the present application provides a method for updating private network contract information, comprising: a first access network device sends a third message to a second access network device, the third message is used to request context information of a terminal device from the second access network device; the first access network device receives a fourth message from the second access network device, the fourth message is used to indicate that the first access network device has failed to obtain context information, and the fourth message carries indication information, and the indication information is used to indicate that the reason for the failure to obtain context information is related to the private network contract information. An embodiment of the present application introduces a solution, when the first access network device fails to obtain context from the second access network device, the first access network device triggers an RRC establishment process. Or the first access network device successfully obtains the context and triggers an RRC recovery process. The integrity of the communication protocol is supplemented, so that the problem that the update of private network contract information cannot be completed can be solved.

In one possible design, the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the private network contract scope; unreasonable private network access. Through the above design, the first access network device can more accurately obtain the reason for the path conversion failure.

In the fifth aspect, an embodiment of the present application provides a method for updating private network contract information, including: the core network device determines that the second access network device does not belong to the contract cell of the terminal device, and the second access network device is the access network device that last provided services to the terminal device before entering an inactive state; the core network device sends a first message to the second access network device, and the first message is used to instruct the second access network device to release the context information of the terminal device.

An embodiment of the present application introduces a solution: AMF initiates RRC release when the first access network device does not belong to the private network subscription information, so that the INACTIVE UE can complete the NPN subscription information update and improve resource utilization.

In a possible design, the first message carries first indication information, and the first indication information is used to indicate that the reason for releasing the context information is related to the private network contract information. Through the above design, the first access network device can obtain the reason for the failure of the path conversion, which can be beneficial to data statistics.

In one possible design, the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the private network contract scope; unreasonable private network access. Through the above design, the first access network device can more accurately obtain the reason for the path conversion failure.

In one possible design, after the core network device sends the first message to the second access network device, the method further includes: the core network device receives second information from the second access network device, the second information is used to indicate the access network-based notification area (RAN-Based notification area, RNA) information of the terminal device. In the above design, the second access network device uses the RNA of the UE to facilitate the AMF to initiate CN paging in the RNA, which saves a lot of overhead compared to paging in the tracking area identity (TAI) list (TAI List).

In one possible design, after the core network device receives the second information from the second access network device, the method further includes: the core network device sends a paging message within the RNA range indicated by the second information.

In one possible design, before the core network device sends a first message to the access network device, the method also includes: the core network device receives a second message from the access network device, and the second message is used to indicate that the terminal device is in an inactivated state.

In the sixth aspect, an embodiment of the present application provides a method for updating private network contract information, including: a second access network device receives a first message from a core network device, the first message carries the updated private network contract information of the terminal device; the second access network device sends a paging message to the first access network device, the paging message carries indication information, and the indication information is used to indicate that the first access network device does not belong to the contracted cell indicated by the private network contract information.

An embodiment of the present application provides a solution: the second access network device treats cells that are still in the new private network contract information and cells that are not in the new private network contract information differently, so that the cells that are not in the new private network contract information can trigger the UE to initiate the RRC establishment process, so that the INACTIVE UE can complete the update of the private network contract information.

In one possible design, the indication information is a non-access layer user identifier of the terminal device.

In a possible design, the non-access stratum user identifier is an S-temporary mobile subscriber identity (SAE-temporary mobile subscriber identity, S-TMSI).

In a seventh aspect, an embodiment of the present application provides a method for updating private network contract information, including: a first access network device receives a first paging message from a second access network device, the first paging message carries indication information, and the indication information is used to indicate that the first access network device does not belong to a contract cell indicated by the private network contract information. The first access network device sends a second paging message, and the second paging message is used to trigger the terminal device to establish an RRC connection with the first access network device.

An embodiment of the present application provides a solution: the second access network device treats cells that are still in the new private network contract information and cells that are not in the new private network contract information differently, so that the cells that are not in the new private network contract information can trigger the UE to initiate the RRC establishment process, so that the INACTIVE UE can complete the update of the private network contract information.

In one possible design, the indication information is a non-access layer user identifier of the terminal device.

In one possible design, the non-access stratum user identifier is S-TMSI.

In an eighth aspect, an embodiment of the present application provides a method for updating private network contract information, including: an access network device receives a first message from a core network device, the first message carrying the updated private network contract information of a terminal device; the access network device sends a second message, the second message is used to trigger the terminal device to restore the wireless resource control connection; the access network device receives a third message from the terminal device, the third message is used to request restoration of the RRC connection; the access network device determines that the access network device does not belong to the contracted cell indicated by the private network contract information; the access network device restores or re-establishes the RRC connection with the terminal device; the access network device sends the private network contract information to the terminal device.

In an embodiment of the present application, a solution is introduced for the situation where the source cell and the target cell are the same base station and the target cell is not in the new private network contract information: the base station ignores the new private network contract information, allows the UE to complete RRC recovery, and completes the update of the new private network contract information.

In the ninth aspect, the present application provides a private network subscription information update device, which may be a core network device, or a chip or chipset in the core network device. The device may include a processing unit and a transceiver unit. When the device is a core network device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the device may also include a storage unit, and the storage unit may be a memory; the storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit so that the core network device performs the corresponding functions in the first aspect or the fifth aspect above. When the device is a chip or chipset in a core network device, or a chip or chipset in a network device, the processing unit may be a processor, and the transceiver unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage unit so that the core network device performs the corresponding functions in the first aspect or the fifth aspect above, and the storage unit may be a storage unit in the chip or chipset (for example, a register, a cache, etc.), or a storage unit in the communication device located outside the chip or chipset (for example, a read-only memory, a random access memory, etc.).

In the tenth aspect, the present application provides a private network contract information update device, which may be an access network device, or a chip or chipset in the access network device. The device may include a processing unit and a transceiver unit. When the device is an access network device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the device may also include a storage unit, which may be a memory; the storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the access network device to perform the corresponding functions in the second aspect or the third aspect or the fourth aspect or the sixth aspect or the seventh aspect or the eighth aspect. When the device is a chip or chipset in an access network device, the processing unit may be a processor, and the transceiver unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes instructions stored in the storage unit so that the access network device performs the corresponding functions in the second aspect or the third aspect or the fourth aspect or the sixth aspect or the seventh aspect or the eighth aspect mentioned above, and the storage unit may be a storage unit in the chip or chipset (for example, a register, a cache, etc.), or may be a storage unit in the communication device that is located outside the chip or chipset (for example, a read-only memory, a random access memory, etc.).

In an eleventh aspect, a device is provided, comprising: a processor, a communication interface, and a memory. The communication interface is used to transmit information, and/or messages, and/or data between the device and other devices. The memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory, so that the device executes the method as described in any one of the first aspect or the fifth aspect.

In a twelfth aspect, a device is provided, comprising: a processor, a communication interface and a memory. The communication interface is used to transmit information, and/or messages, and/or data between the device and other devices. The memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory, so that the device executes the method described in any one of the second aspect, the third aspect, the fourth aspect, the sixth aspect, the seventh aspect or the eighth aspect.

In a thirteenth aspect, the present application also provides a communication system, which includes a core network device in any embodiment of the above-mentioned first aspect, and a first access network device in any embodiment of the above-mentioned second aspect.

In a fourteenth aspect, the present application also provides a communication system, which includes the second access network device in any embodiment of the third aspect mentioned above, and the first access network device in any embodiment of the fourth aspect mentioned above.

In a fifteenth aspect, the present application also provides a communication system, which includes a core network device in any embodiment of the fifth aspect above.

In the sixteenth aspect, the present application also provides a communication system, which includes the second access network device in any embodiment of the above-mentioned sixth aspect, and the first access network device in any embodiment of the above-mentioned seventh aspect.

In the seventeenth aspect, the present application also provides a communication system, which includes the access network device in any embodiment of the above-mentioned eighth aspect.

In the eighteenth aspect, the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when executed on a computer, enables the computer to execute the method described in the first aspect or the fifth aspect above.

In the nineteenth aspect, the present application also provides a computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, which, when executed on a computer, enables the computer to execute the method described in the second aspect, the third aspect, the fourth aspect, the sixth aspect, the seventh aspect, or the eighth aspect above.

In the twentieth aspect, the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the first or fifth aspect above.

In the twenty-first aspect, the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the second aspect, the third aspect, the fourth aspect, the sixth aspect, the seventh aspect, or the eighth aspect above.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the transition between three states of a terminal device provided in an embodiment of the present application;

FIG2 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

FIG3 is a schematic diagram of the structure of an access network device provided in an embodiment of the present application;

FIG4 is a schematic diagram of the structure of an access network device provided in an embodiment of the present application;

FIG5 is a schematic diagram of the structure of an access network device provided in an embodiment of the present application;

FIG6 is a flow chart of a method for updating private network contract information provided in an embodiment of the present application;

FIG7 is a schematic diagram of a private network contract information update process provided in an embodiment of the present application;

FIG8 is a schematic diagram of a private network contract information update process provided in an embodiment of the present application;

FIG9 is a schematic diagram of a private network contract information update process provided in an embodiment of the present application;

FIG10 is a schematic diagram of a private network contract information update process provided in an embodiment of the present application;

FIG11 is a schematic diagram of a private network contract information update process provided in an embodiment of the present application;

FIG12 is a schematic diagram of a private network contract information update process provided in an embodiment of the present application;

FIG13 is a schematic diagram of a private network contract information update process provided in an embodiment of the present application;

FIG14 is a schematic diagram of a private network contract information updating device provided in an embodiment of the present application;

FIG15 is a schematic diagram of a private network contract information updating device provided in an embodiment of the present application.

Detailed ways

To facilitate understanding of the embodiments of the present application, the following terms related to the embodiments of the present application are introduced:

1. Public network

In daily life, the public network generally provides network services for terminal devices. The public network, namely the public land mobile network (PLMN), is a network established and operated by the government or its approved operators to provide land mobile communication services to the public. This network is usually interconnected with the public switched telephone network (PSTN) to form a communication network on a regional or national scale.

Different PLMN networks can be distinguished by different PLMN identifications (IDs). PLMN identifications consist of a mobile country code (MCC) and a mobile network code (MNC). MCC uniquely indicates the country to which the mobile user belongs, for example, China's MCC is 460. MNC uniquely indicates the network in that country, for example, China Mobile's MNC is 00 and China Unicom's MNC is 01.

2. Private network

In addition to the public network, for some purposes, operators or individuals will also build some private networks (non-public networks, NPN) to meet the needs of users. Private networks can also be called non-public networks, which refer to networks open to specific users, such as internal networks built by companies, schools or factories. Terminal devices that have not signed contracts with private networks are not allowed to access private networks. Private networks are divided into non-independent private networks and independent private networks.

(1) Non-independent private network

The network resources used by the non-stand-alone non-public network (NSA-NPN, or public network integrated non-public network, PNI-NPN) are part of the public network. It can also be said that the non-stand-alone private network depends on the public network. The non-stand-alone private network is also called a closed access group (CAG). The identification of the non-stand-alone private network includes two parts, namely the PLMN ID and the CAG ID. The PLMN ID of the non-stand-alone private network is consistent with the public network it depends on. For multiple non-stand-alone private networks that rely on the same public network, the CAG ID of each non-stand-alone private network is unique. In other words, multiple non-stand-alone private networks that rely on the same public network can be distinguished only by the CAG ID.

For example, the identifier of the non-independent private network #1 may be represented as: PLMN #1 CAG #1;

The identifier of the non-independent private network #2 can be expressed as: PLMN#1CAG#2.

That is, both the non-independent private network #1 and the non-independent private network #2 are private networks built by relying on the public network identified as PLMN #1. In some cases, the two private networks can be distinguished only by CAG #1 and CAG #2.

According to the current communication protocol, because the CAG network uses public network resources, the terminal device can switch between the CAG network and the public network and reselect the cell. Switching means that the terminal device in the connected state disconnects from the current service cell and connects to the target cell under the control of the base station. Cell reselection means that when the terminal device in the idle state/deactivated state resides in a cell, as the terminal device moves, the terminal device may need to switch to another cell with higher priority or better signal to reside. This is the cell reselection process.

(2) Independent private network

A stand-alone non-public network (SNPN) refers to a private network that does not rely on the network functions of the public network. Similarly, the identification of an independent private network is also divided into two parts, namely the PLMN ID and the NID. For an independent private network that relies on the public network, its PLMN ID is consistent with the public network it relies on. For an independent private network that does not rely on the public network (for example, it can be deployed by the enterprise itself), the MCC of its PLMN ID is 999. For multiple independent private networks that rely on the same public network, the NID of each non-independent private network is unique. In other words, multiple independent private networks that rely on the same public network can be distinguished only by the NID.

For example, the identifier of the independent private network #1 can be expressed as: PLMN #1 NID #1;

The identifier of the independent private network #2 can be expressed as: PLMN#1NID#2;

The identifier of the independent private network #3 can be expressed as: PLMN #3 (MCC=999) NID #1.

That is, both the independent private network #1 and the independent private network #2 are private networks built by relying on the public network identified as PLMN #1. In some cases, the two private networks can be distinguished only by NID #1 and NID #2.

In addition, the MCC of the PLMN ID of the independent private network #3 is 999, indicating that the independent private network #3 is an independent private network deployed by the enterprise itself without the help of an operator.

As a possible way, the independent private network does not support the switching and cell reselection of terminal devices between the independent private network and the public network, the non-independent private network and other independent private networks, that is, the terminal devices in the connected state cannot switch from the independent private network cell to the public network cell, the non-independent private network cell and other independent private network cells, and vice versa; the terminal devices in the idle state/deactivated state cannot reselect from the independent private network cell to the public network cell, and vice versa. It can be understood that as another possible implementation method, the independent private network can support the switching and cell reselection of terminal devices between the independent private network and the public network, the non-independent private network and other independent private networks.

3. RRC status of terminal equipment

In NR, the RRC state of UE includes connected state (RRC_CONNECTED), deactivated state or the third state (RRC_INACTIVE), and idle state (RRC_IDLE). When the UE is in the RRC_CONNECTED state, the UE has established links with the base station and the core network. When data arrives at the network, it can be directly transmitted to the UE; when the UE is in the RRC_INACTIVE state, it means that the UE has previously established links with the base station and the core network, but the link from the UE to the base station has been released. Although the link has been released, the base station will store the UE's context. When there is data to be transmitted, the base station can restore this link in time; when the UE is in the RRC_IDLE state, there is no link between the UE and the base station and the network. When there is data to be transmitted, it is necessary to establish a link from the UE to the base station and the core network. The transition of the three states is shown in Figure 1.

4. Contract information

Contract information refers to the user access information signed between the terminal device and the operator or other company that builds the network. If the terminal device has signed the contract, it can access the corresponding network and use the network resources according to the network identifier in the contract information. The contract information is stored on the core network side and the terminal device side. If there is a change, the core network will initiate the UE configuration update process (UE configuration update) to notify the terminal device side.

It should be noted that with the continuous development of technology, the terms of the embodiments of the present application may change, but they are all within the scope of protection of the present application.

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

The private network contract information update method provided in the embodiment of the present application is applicable to a possible communication system architecture, and the architecture of the communication system may include a network exposure function network element, a policy control function network element, a data management network element, an application function network element, a core network access and mobility management function network element, a session management function network element, a terminal device, an access network device, a user plane function network element and a data network. Among them, Figure 2 shows a possible example of the architecture of the communication system, specifically including: a network exposure function (NEF) network element, a policy control function network element (PCF) network element, a data management network element (UDM) network element, an application function network element (AF) network element, an AMF network element, a session management function network element (SMF) network element, a UE, an access network (AN) device, a user plane function (UPF) network element and a data network (DN). Among them, the AMF network element and the terminal device can be connected through the N1 interface, the AMF and the AN device can be connected through the N2 interface, the AN device and the UPF can be connected through the N3 interface, the SMF and the UPF can be connected through the N4 interface, and the UPF and the DN can be connected through the N6 interface. The interface name is only an example, and the embodiment of the present application does not specifically limit this. It should be understood that the embodiment of the present application is not limited to the communication system shown in Figure 2. The name of the network element shown in Figure 2 is used here only as an example, and is not used as a limitation on the network elements included in the communication system architecture to which the method of the present application is applicable. The functions of each network element or device in the communication system are described in detail below:

The terminal device, which can also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device that provides voice and/or data connectivity to users. For example, the terminal device may include a handheld device with wireless connection function, a vehicle-mounted device, etc. At present, the terminal device may be: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile Internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, or a wireless terminal in smart home, etc. Among them, the terminal device described in FIG2 is shown as UE, which is only used as an example and does not limit the terminal device.

The wireless access network may be the access network (AN) shown in FIG2, which provides wireless access services to the terminal device. The access network device is a device in the communication system that connects the terminal device to the wireless network. The access network device is a node in the wireless access network, which may also be called a base station, or a radio access network (RAN) node (or device). At present, some examples of access network devices are: gNB, transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wifi) access point (AP), etc.

Exemplarily, the wireless access network device in the embodiment of the present application can be divided into two parts according to the protocol stack function: a centralized unit (CU) and a distributed unit (DU). Among them, a wireless access network device may include a CU and at least one DU, as shown in Figure 3. The CU is connected to at least one DU and can be used to manage or control the at least one DU. This structure can separate the protocol layer of the wireless access network device in the communication system, wherein some protocol layer functions are implemented in the CU, and the remaining part or all of the protocol layer functions are distributed in the DU, and the DU is centrally controlled by the CU. Taking the wireless access network device as a gNB as an example, the protocol layer of the gNB includes a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control sublayer (MAC) layer, and a physical layer. Among them, exemplarily, the CU can be used to implement the functions of the RRC layer, the SDAP layer and the PDCP layer, and the DU can be used to implement the functions of the RLC layer, the MAC layer and the physical layer. The embodiment of the present application does not specifically limit the protocol stack included in the CU and the DU. The CU and the DU can be connected using the F1 interface, the CU and other wireless access network devices are connected using the Xn interface, and the CU and the 5G core network (5G Core, 5GC) are connected using the NG interface, as shown in Figure 4.

Exemplarily, the CU in the embodiment of the present application can be further divided into a control plane (CU-control plane, CU-CP) network element and at least one user plane (CU-user plane, CU-UP) network element. Among them, CU-CP can be used for control plane management, and CU-UP can be used for user plane data transmission. The interface between CU-CP and CU-UP can be an E1 port. The interface between CU-CP and DU can be F1-C, which is used for the transmission of control plane signaling. The interface between CU-UP and DU can be F1-U, which is used for user plane data transmission. CU-UP and CU-UP can be connected through the Xn-U port for user plane data transmission. For example, taking gNB as an example, the structure of gNB can be shown in Figure 5.

The data network, such as the data network (DN) shown in FIG2 , may be the Internet, an IP Multimedia Service (IMS) network, a regional network (i.e., a local network, such as a mobile edge computing (MEC) network), etc. The data network includes an application server, and the application server provides business services to the terminal device by performing data transmission with the terminal device.

The core network is used to connect the terminal device to the DN that can realize the service of the terminal device. The functions of each network element in the core network are described below:

The core network access and mobility management function network element can be used to manage the access control and mobility of the terminal device. In actual applications, it includes the mobility management function in the mobility management entity (MME) in the network framework in long term evolution (LTE), and adds the access management function, which can be responsible for the registration of the terminal device, mobility management, tracking area update process, reachability detection, selection of session management function network element, mobile state transition management, etc. For example, in 5G, the core network access and mobility management function network element can be an AMF (access and mobility management function) network element, such as shown in Figure 2. In future communications, such as 6G, the core network access and mobility management function network element can still be an AMF network element, or have other names, which are not limited in this application. When the core network access and mobility management function network element is an AMF network element, the AMF can provide Namf services.

The session management function network element can be used to be responsible for the session management of the terminal device (including the establishment, modification and release of the session), the selection and reselection of the user plane function network element, the allocation of the Internet Protocol (IP) address of the terminal device, and the quality of service (QoS) control. For example, in 5G, the session management function network element can be an SMF (session management function) network element, such as shown in Figure 2. In future communications, such as 6G, the session management function network element can still be an SMF network element, or have other names, which are not limited in this application. When the session management function network element is an SMF network element, the SMF can provide Nsmf services.

The policy control function network element can be used to be responsible for policy control decisions, provide functions such as service data flow and application detection, gating, QoS and flow-based charging control, etc. For example, in 5G, the policy control function network element can be a PCF (policy control function) network element, as shown in Figure 2. In future communications, such as 6G, the policy control function network element can still be a PCF network element, or have other names, which are not limited in this application. When the policy control function network element is a PCF network element, the PCF network element can provide Npcf services.

The main function of the application function network element is to interact with the 3rd generation partnership project (3GPP) core network to provide services, to affect service flow routing, access network capability opening, policy control, etc. For example, in 5G, the application function network element may be an AF network element, as shown in Figure 2. In future communications, such as 6G, the application function network element may still be an AF network element, or have other names, which are not limited in this application. When the application function network element is an AF network element, the AF network element may provide Naf services.

The data management network element can be used to manage the contract data of the terminal device, the registration information related to the terminal device, etc. For example, in 5G, the data management network element can be a unified data management network element (UDM), as shown in Figure 2. In future communications, such as 6G, the data management network element can still be a UDM network element, or have other names, which are not limited in this application. When the data management network element is a UDM network element, the UDM network element can provide Nudm services.

The network open function network element can be used to enable 3GPP to securely provide network service capabilities, etc. to third-party AFs (e.g., service capability servers (SCS), application servers (AS), etc.). For example, in 5G, the network open function network element may be an NEF, as shown in FIG2 . In future communications, such as 6G, the network open function network element may still be an NEF network element, or have other names, which are not limited in this application. When the network open function network element is an NEF, the NEF may provide Nnef services to other network function network elements.

The above network elements in the core network can also be called functional entities, which can be network elements implemented on dedicated hardware, software instances running on dedicated hardware, or instances of virtualized functions on an appropriate platform. For example, the above virtualization platform can be a cloud platform.

It should be noted that the architecture of the communication system shown in FIG. 2 is not limited to including only the network elements shown in the figure, but may also include other devices not shown in the figure, which will not be listed one by one in this application.

It should be noted that the embodiments of the present application do not limit the distribution form of each network element in the core network. The distribution form shown in Figure 2 is only exemplary and is not limited in this application.

For the convenience of explanation, this application will be described later using the network element shown in Figure 2 as an example, and the XX network element will be directly referred to as XX, such as the AMF network element will be referred to as AMF. It should be understood that the names of all network elements in this application are only examples, and they can also be called other names in future communications, or the network elements involved in this application can also be replaced by other entities or devices with the same functions in future communications, and this application does not limit this. A unified explanation is given here, and no further elaboration will be given later.

It should be noted that the communication system shown in Figure 2 does not constitute a limitation on the communication system to which the embodiments of the present application can be applied. The communication system architecture shown in Figure 2 is a 5G system architecture. Optionally, the method of the embodiments of the present application is also applicable to various future communication systems, such as 6G or other communication networks.

Taking CAG as an example, the description of contract information in the agreement is:

The terminal device will pre-configure or reconfigure the following CAG information, which is part of the mobility restriction:

-The list of CAG cells that are allowed to be accessed means that the terminal device can access these CAG cells, and the other CAG cells not mentioned cannot be accessed.

-Only CAG indication is allowed. If this indication is present, it means that the terminal device cannot access the public network.

Optionally, the above CAG information can be configured for each PLMN.

For the terminal device in Inactive state, as a possible implementation method, AMF will send a downlink non-access stratum (NAS) transmission (DOWNLINK NAS TRANSPORT) to the source base station when triggering the configuration update process. The downlink NAS transmission carries a NAS-protocol data unit (PDU) and a mobility restriction list (Mobility Restriction List), wherein the NAS-PDU is sent by AMF to the terminal device, and the base station transparently transmits it to the terminal device after receiving the NAS-PDU. The Mobility Restriction List is sent by AMF to the base station, and both the NAS-PDU and the Mobility Restriction List carry the updated private network contract information. The source base station is the last serving base station before the terminal device enters the inactive state from the connected state. The source base station sends a paging message to the base stations in the RNA of the terminal device, and these base stations then transparently transmit it to all UEs connected to themselves. The UE that monitors the paging message will check whether it contains its own I-RNTI. If so, it will initiate an RRC recovery request to the base station to which the current serving cell belongs. If the base station to which the current service cell belongs is the source base station, the terminal device can receive the updated private network contract information sent by the source base station. If the base station to which the current service cell belongs is a target base station different from the source base station, the terminal device can receive the updated private network contract information at the target base station. The target base station can obtain the updated private network contract information of the terminal device from the source base station or from the core network device, which is not limited in the embodiments of the present application.

Taking the example of the target base station obtaining the UE's updated private network contract information from the core network device AMF, for the terminal device in INACTIVE, if the source base station receives the DOWNLINK NAS TRANSPORT sent by AMF, it initiates paging of the corresponding inactive UE. If the target base station initiated by the inactive UE is not the source base station (that is, the last serving gNB, the base station that disconnects the air interface connection and enters INACTIVE), the source cell can send an indication message to the AMF, which is used to indicate that the source base station cannot send the updated contract information to the UE. The AMF waits for the target base station to complete the path switch and then sends the DOWNLINK NAS TRANSPORT containing the updated private network contract information to the target base station, and the target base station forwards the NAS-PDU to the UE.

For the updated contract information, the source base station and the target base station may or may not be in the new contract cell list. If the source base station and the target base station are not in the new contract cell list, there is currently no good solution for how AMF updates the contract information in the terminal device.

Based on this, the present application provides a private network contract information update method and device, which are used to improve the update process of the private network contract information of the terminal device in the INACTIVE state. The method and the device are based on the same invention concept. Since the principles of solving the problem by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

It should be noted that the multiple involved in the embodiments of the present application refers to two or more. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the previous and next associated objects are in an "or" relationship. At the same time, it should be understood that in the description of the embodiments of the present application, words such as "first" and "second" are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

The embodiments of the present application are described in detail below in conjunction with specific scenarios.

It is understandable that in the embodiment of the present application, the terminal device and/or the network device can perform some or all of the steps in the embodiment of the present application, and these steps or operations are only examples. The embodiment of the present application can also perform other operations or variations of various operations. In addition, each step can be performed in a different order presented in the embodiment of the present application, and it is possible not to perform all the operations in the embodiment of the present application.

See Figure 6, which is a flow chart of a method for updating private network contract information provided by this application. The method includes:

S601, the first access network device restores the RRC connection with the terminal device.

The terminal device may be an inactive UE, and the first access network device is the access network device that initiates a recovery request for the terminal device.

S602, the first access network device sends private network information to the core network device.

The private network information includes at least one private network identifier supported by the cell used by the first access network device and the terminal device to restore the RRC connection. Accordingly, the core network device can receive the private network information sent by the first access network device.

The core network device can determine the identifier of at least one private network supported by the first access network device based on the private network information.

Optionally, the first access network device may send the private network information to the core network device via a path switching request message.

In one implementation, at least one private network depends on a first public network, and the first public network is a public network on which a target network selected by a terminal device depends.

The embodiments of the present application are not limited to the type of private network, and the private network can be an independent private network or a non-independent private network. It should be understood that "private network" is only an exemplary name, and it can also be named as other in the future development of communications. As long as the function of the private network in the embodiments of the present application can be realized, it can be understood as the private network in the embodiments of the present application.

The public network may also be referred to as a public land mobile network, or PLMN. It should be understood that "public network" is only an exemplary name, and may also be named otherwise in future communication developments. As long as the functions of the public network in the embodiments of the present application can be realized, it can be understood as the public network in the embodiments of the present application.

If the private network is a non-independent private network, the identifier of the private network may include two parts, namely the PLMN ID and the CAG ID, wherein the PLMN ID is consistent with the public network ID on which it depends. For multiple non-independent private networks that depend on the same public network, the CAG ID of each non-independent private network is unique. For example, the identifier of non-independent private network #1 can be expressed as: PLMN#1CAG#1; the identifier of non-independent private network #2 can be expressed as: PLMN#1CAG#2. Among them, non-independent private network #1 and non-independent private network #2 are both private networks built based on the public network identified as PLMN#1.

If the private network is an independent private network, the identifier of the private network may include two parts, namely, PLMN ID and NID. For example, the identifier of the private network may be PLMN#1. For an independent private network that relies on a public network, its PLMN ID is consistent with the public network it relies on. For an independent private network that does not rely on a public network (for example, it may be deployed by an enterprise itself), the MCC of its PLMN ID is a fixed value, such as 999. For example, the identifier of independent private network #1 may be expressed as: PLMN#1NID#1; the identifier of independent private network #2 may be expressed as: PLMN#1NID#2; the identifier of independent private network #3 may be expressed as: PLMN#3(MCC＝999)NID#1. Among them, both independent private network #1 and independent private network #2 are private networks that rely on the public network identified as PLMN#1.

In an exemplary description, the first access network device may be an access network device to which the terminal device accesses when restoring the RRC connection from an INACTIVE state.

In an exemplary description, the core network device may be an AMF.

S603, the core network device performs verification based on the private network information and the private network contract information of the terminal device.

Optionally, private network contract information is stored in the core network device.

In an embodiment of the present application, a solution is provided for the situation where the source cell and/or target cell is not in the private network contract information when the INACTIVE state UE updates the private network contract information, thereby improving the update process of the private network contract information of the terminal device in the INACTIVE state.

In one possible implementation, when the core network device performs verification based on the private network information and the private network contract information of the terminal device, if at least one private network identifier in the private network information belongs to the updated private network contract information, the verification is successful, or the verification passes.

As an example, assuming that the private network contract information includes PLMN#1CAG#1, PLMN#1CAG#2 and PLMN#2CAG#2, the private network information sent by the first access network device includes PLMN#1CAG#1, PLMN#1CAG#3 and PLMN#1CAG#4, and PLMN#1CAG#1 in the private network information is included in the private network contract information of the terminal device, so it can be determined that the verification is passed.

If the private network identifier in the private network information does not belong to the updated private network contract information, the verification fails or the verification is not passed.

As an example, assuming that the private network contract information includes PLMN#1CAG#1, PLMN#1CAG#2 and PLMN#2CAG#2, and the private network information sent by the first access network device includes PLMN#1CAG#5, PLMN#1CAG#3 and PLMN#1CAG#4, PLMN#1CAG#5, PLMN#1CAG#3 and PLMN#1CAG#4 in the private network information are not included in the private network contract information of the terminal device, so it can be determined that the verification failed.

Further, if the verification is successful, the core network device may send the private network contract information of the terminal device to the first access network device. It is understandable that the private network contract information may be the latest private network contract information. Alternatively, the private network contract information may be the updated private network contract information.

If the verification fails, the core network device may send a release message to the first access network device, and the release message is used to instruct the first access network device to release the connection between the first access network device and the core network device of the terminal device. Optionally, the first access network device may also send an RRC (connection) release message to the terminal device to release the RRC connection of the terminal. Exemplarily, the release message may carry first indication information, and the first indication information is used to indicate the reason for the release, for example, it may indicate that the reason for releasing the terminal device is related to the private network contract information.

Alternatively, the first indication information is used to indicate that the reason for the path switching failure is related to the private network contract information.

Alternatively, the first indication information is used to indicate that the reason for releasing the terminal device and the reason for the path switching failure are related to the private network contract information.

In a possible implementation, the first indication information may include but is not limited to at least one of the following: invalid private network identification; unsupported private network identification; not within the scope of the private network contract; unreasonable private network access.

In another possible implementation, if the verification fails, the core network device may send a first notification message to the first access network device, where the first notification message is used to notify the first access network device that the terminal device accesses the public network.

In some embodiments, before the core network device sends a release message to the first access network device, the core network device may send a NAS-PDU carrying private network contract information to the first access network device, which is transparently transmitted to the terminal device by the first access network device. In the above manner, the terminal device can update the private network contract information in a timely manner, which can save update time on the one hand and improve resource utilization on the other hand.

In other embodiments, the core network device may also carry a NAS-PDU in the release message, where the NAS-PDU carries private network subscription information, so that the first access network device may transparently transmit the NAS-PDU to the terminal device when receiving the release message.

In one possible implementation, before the core network device receives the path switching request from the first access network device, the core network device may trigger the private network subscription information update process. For example, the core network device may send the private network subscription information to the second access network device, where the second access network device is the access network device connected before the terminal device enters the INACTIVE state.

After the core network device triggers the private network contract information update process, it can receive a second indication information from the second access network device. The second indication information is used to instruct the core network device to send the private network contract information to the first access network device after receiving the private network information from the first access network device, or the second indication information is used to instruct the core network device that the second access network device cannot send the latest private network contract information to the terminal device.

In another possible implementation, before the core network device receives the path switching request from the first access network device, the terminal device may trigger the RRC connection recovery process. For example, the terminal device sends an RRC recovery request to the first access network device.

In an exemplary description, the first access network device and the second access network device may be the same access network device, and the cell accessed by the terminal device before entering the INACTIVE state (for the convenience of description, referred to as the source cell below) and the cell accessed by the terminal device when restoring the RRC connection from the INACTIVE state (for the convenience of description, referred to as the target cell below) are the same cell.

In another exemplary description, the first access network device and the second access network device may be the same access network device, and the source cell of the terminal device and the target cell of the terminal device are different cells.

In one exemplary description, the first access network device and the second access network device may be different access network devices.

In order to better understand the method provided in the embodiment of the present application, the private network subscription information update process is described in detail below in combination with a specific scenario. For the convenience of description, the following description is based on the core network device as AMF, the private network as CAG, and the public network as PLMN as an example.

Scenario 1: UE1 accesses the first cell of the source base station before entering the INACTIVE state, and accesses the second cell of the target base station when UE1 recovers the RRC connection from the INACTIVE state, wherein the source base station and the target base station are different base stations.

The private network contract information update process can be shown in Figure 7:

S701, AMF sends the private network subscription information of UE1 to the source base station. The private network subscription information can be stored in AMF. Execute S702.

In an exemplary description, the private network subscription information may be the private network subscription information updated by UE1. For example, the subscription cell indicated by the private network subscription information updated by UE1 may not be completely the same as that of the private network subscription information before the update.

As an example, it is assumed that the private network subscription information before updating includes PLMN#1CAG#1, PLMN#1CAG#2 and PLMN#2CAG#2, and the private network subscription information after updating includes PLMN#1CAG#1, PLMN#1CAG#3 and PLMN#2CAG#2.

In one implementation, the AMF may send a DOWNLINK NAS TRANSPORT to the source base station, and the DOWNLINK NAS TRANSPORT may carry the private network subscription information of UE1.

S702: The source base station sends second indication information to the AMF. Execute S703.

The second indication information is used to indicate that UE1 is in the INACTIVE state, or the second indication information may also instruct the AMF to send the private network contract information to the target base station after receiving the private network information of the target base station, or the second indication information may also instruct the AMF to send the private network contract information to the target base station after receiving the path switching request of the target base station, or the second indication information is used to indicate that the core network device and the second access network device cannot send the latest private network contract information to the terminal device.

In one implementation, the second indication information may be a UE context transmission indication, or may be a serving base station change indication.

S703: The source base station sends a paging message to the target base station. The paging message can be used to notify UE1 to restore the RRC connection. Execute S704.

Exemplarily, the scope of the paging may be the RNA of UE1.

S704: The target base station sends a paging to UE1. The paging may be used to notify UE1 to restore the RRC connection. S705 is executed.

Exemplarily, the paging may be based on the RNA of UE1.

In one implementation manner, the target base station may forward the paging sent by the source base station to UE1.

S705, UE1 sends an RRC recovery request (RRC RESUME REQUEST) to the target base station through the second cell. Execute S706.

The RRC recovery request can be used by the UE to request the target cell under the target base station to restore the RRC connection.

S706: The target base station sends a restore context request (RETRIEVE UE CONTEXT REQUEST) to the source base station. Execute S707.

The context restoration request may be used by the target base station to request the source base station to send the context of UE1, where the context is used by the target base station to restore the RRC connection with UE1.

It can be understood that, as another implementation manner, the UE may execute step 701, steps 703 to 706, and then execute step 702.

S707: The source base station sends a restore context response (RETRIEVE UE CONTEXTRESPONSE) to the target base station. Then, S708 is executed.

The restore context response may carry the context of UE1.

S708: The target base station performs RRC recovery (RRC RESUME) with UE1. Then, S709 is executed.

Exemplarily, the target base station may restore the RRC connection with UE1 according to the context of UE1.

S709, UE1 sends an RRC recovery complete message (RRC RESUME COMPLETE) to the target base station. Execute S710.

In one implementation, the RRC recovery complete message may carry the public network identifier of the target network selected by UE1, such as PLMN ID. Assume that the public network identifier is PLMN 1.

In addition, if the target network is a private network, the RRC recovery completion message may carry third indication information, and the third indication information is used to indicate that the target network is a private network, or may also be used to indicate that the public network identifier is the identifier of the public network on which the target network depends.

If the target network is a public network, the RRC recovery completion message may carry third indication information, where the third indication information is used to indicate that the target network is a network.

It can be understood that in the embodiment of the present application, the target network is a private network, and therefore, the RRC recovery completion message can carry the third indication information.

S710, the target base station sends private network information to the AMF, and the private network information includes the ID of at least one CAG supported by the second cell. Furthermore, the private network information includes the ID of at least one CAG under the PLMN supported by the second cell selected by the terminal device. For example, if the terminal device accesses through PLMN1 of the second cell, the ID of the at least one CAG can be understood as the ID of the CAG that depends on PLMN 1, or the ID of the CAG under PLMN1. Among them, PLMN 1 is the public network that the target network selected by UE1 depends on. Execute S711.

The at least one CAG depends on PLMN 1, which can also be understood as the PLMN ID of the at least one CAG is PLMN 1. The public network on which the target network selected by UE1 depends is PLMN 1, which can also be understood as the PLMN ID of the public network on which the target network selected by UE1 depends is PLMN 1.

For example, UE1 reports the selected target network to the target base station, and the PLMN ID of the target network is PLMN 1. The target base station sends the CAG ID of the CAG whose PLMN ID is PLMN 1 among all CAGs supported by the second cell to the AMF.

In one implementation, PLMN 1 may be the PLMN ID of the selected network carried by UE1 in the RRC recovery complete message.

As an example, assume that the private networks supported by the target base station are: PLMN#1CAG#1; PLMN#1CAG#2; PLMN#1CAG#3; PLMN#2CAG#1; PLMN#2CAG#2; PLMN#2CAG#3. The PLMN ID of the selected network carried by UE1 in the RRC recovery complete message is PLMN#1. The private network information reported by the target base station to the AMF may include PLMN#1CAG#1; PLMN#1CAG#2; PLMN#1CAG#3.

In another implementation, the private network information may be carried in the RRC recovery complete message, that is, UE1 may report the private network information to the target base station through the RRC recovery complete message. The target base station may forward the private network information carried in the RRC recovery complete message to the AMF.

In one implementation, the target base station may send a path switch request (PATH SWITCH REQUEST) to the AMF, and the PATH SWITCH REQUEST may carry private network information. The path switch request may be used to request the AMF to transfer the data receiving point of the interface and/or data channel between the AMF and the target base station to the target base station. It can be understood that when the core network sends data to UE1, it may be sent to the target base station first, and then forwarded to UE1 by the target base station.

S711, AMF performs verification based on the private network information and the private network subscription information of UE1. If the verification passes, execute step S712; if the verification fails, execute step S716.

Among them, if at least one CAG ID in the private network information belongs to the private network contract information of UE1, the verification is successful.

If the CAG ID in the private network information does not belong to the private network contract information of UE1, the verification fails or the verification fails.

S712, AMF sends a path switch acknowledgement to the target base station. Execute S713.

The path switching response may be used to notify the target base station that the core network device has transferred the data receiving point of the UE1 to the target base station.

S713: The target base station sends a UE CONTEXT RELEASE message to the source base station. Then, S714 is executed.

The UE context release message may be used to instruct the source base station to release the context of UE1, so that the source base station may no longer store the context of UE1.

S714, AMF sends the private network subscription information of UE1 to the target base station. Execute S715.

In one implementation, the AMF may send a DOWNLINK NAS TRANSPORT to the target base station, and the DOWNLINK NAS TRANSPORT may carry the private network subscription information of UE1.

S715, the target base station sends private network subscription information to UE1.

In one implementation, the target base station may send a downlink information forwarding message to UE1, and the downlink information forwarding message may carry the private network subscription information of UE1.

In some embodiments, the target base station may transparently transmit the DOWNLINK NAS TRANSPORT sent by the AMF to UE1.

S716, AMF sends a release message to the target base station.

The release message may be used to instruct the target base station to release the RRC connection between the target base station and UE1.

Further, the target base station may send the release message to UE 1. UE 1 may convert from the RRC CONNECTED state to the RRC IDLE state or the RRC INATIVE state, or convert from the RRC INATIVE state to the RRC IDLE state according to the type of the release message.

In some embodiments, the release message may carry first indication information, where the first indication information is used to indicate that the reason for the path switching failure is related to the private network subscription information.

The first indication information may include but is not limited to at least one of the following: invalid private network identification; unsupported private network identification; not within the scope of the private network contract; unreasonable private network access.

In a possible implementation, after step S711 and before step S716, AMF may send UE1's private network subscription information to the target base station, and the target base station may send UE1's private network subscription information to UE1. The specific process may refer to steps S714 and S715, and the repeated parts will not be repeated.

In another possible implementation, the AMF may also carry the private network subscription information of UE1 in the release message, for example, the release message may carry a NAS-PDU, and the NAS-PDU carries the private network subscription information of UE1. The target base station then sends the private network subscription information of UE1 to UE1. For the specific process, please refer to step S715, and the repeated parts will not be repeated.

Scenario 2: UE1 accesses the first cell of the source base station before entering the INACTIVE state. When UE1 recovers the RRC connection from the INACTIVE state, it accesses the second cell of the source base station, that is, the source base station and the target base station are the same base station.

The private network contract information update process of scenario two is similar to that of scenario one. The difference is that in the private network contract information update process of scenario two, the same base station performs the actions of the source base station and the target base station in the private network contract information update process of scenario one, and the repeated parts are not repeated here.

Optionally, in scenario 2, information interaction between the source base station and the target base station may not be performed.

Scenario three: UE1 accesses the first cell of the source base station before entering the INACTIVE state. When UE1 recovers the RRC connection from the INACTIVE state, it accesses the first cell of the source base station, that is, the source cell and the target cell are the same cell.

In one implementation, the private network contract information update process of scenario three is similar to the private network contract information update process of scenario two, except that in the private network contract information update process of scenario two, the information of the second cell is replaced by the information of the first cell, and the repeated parts are not repeated. Optionally, in scenario three, the information exchange between the source base station and the target base station may not be performed. The information exchange between the source cell and the target cell may also not be performed.

In another implementation, for scenario three, the private network contract information update method provided in the embodiment of the present application may not be adopted.

In a possible implementation, in the above scenarios 1 to 3, the private network contract information update process may be triggered by AMF, that is, the above steps S0701 to S708 may be executed before step S709, as shown in FIG. 7 .

In another possible implementation, in the above scenarios 1 to 3, the private network subscription information update process may be triggered by UE1, that is, the above steps S0705 to S708 may be executed before step S709, as shown in FIG. 8 .

Embodiment 2: This application provides another method for updating private network contract information.

Solution 1, the method includes: when the first access network device obtains the context of the UE from the second access network device, the second access network device can verify the first access network device based on the private network contract information sent by the core network device. If the verification fails, the second access network device sends a message to the first access network device that the UE context recovery has failed, and the first access network device triggers the RRC establishment process with the UE. If the verification succeeds, the second access network device sends the UE context to the first access network device, and the first access network device triggers the RRC recovery process with the UE.

Among them, the first access network device is the access network device where the target cell is located, the second access network device is the access network device where the source cell is located, the source cell is the first cell accessed by the terminal device before entering the INACTIVE state, and the target cell is the cell accessed when the terminal device restores the RRC connection from the INACTIVE state.

For the first access network device, the second access network device, and the core network device, please refer to the relevant descriptions of the first access network device, the second access network device, and the core network device in Embodiment 1, which will not be repeated here.

In order to better understand the method provided by Solution 1, the following takes the core network device as AMF as an example for explanation. As shown in Figure 9, the private network contract information update process can be:

S901, AMF sends a downlink NAS transmission message to the source cell, in which the NAS-PDU and MobilityRestriction List both carry new private network subscription information.

S902: The source cell initiates RAN paging to the UE.

In one implementation, the paging message may be sent to all base stations within the RNA of the UE.

S903: After receiving the paging message, the target cell initiates RAN paging to the UE.

Exemplarily, the target cell may use an inactive radio network temporary identifier (I-RNTI) to page the UE.

S904: After hearing the paging message, the UE residing in the target cell sends an RRC recovery request message in the target cell.

S905: The target cell sends a UE context acquisition request message to the source cell.

Optionally, the target cell may obtain source base station information according to the I-RNTI.

S906: The source cell verifies the target cell based on the private network subscription information sent by the AMF. If the verification fails, execute S907.

If the verification is successful, the source cell can send the UE context to the target cell.

Optionally, if the target cell belongs to the contracted cell indicated in the private network contract information, the verification passes; otherwise, the verification fails.

S907: The source cell sends a message to the target cell indicating that the UE context recovery has failed.

Optionally, the failure to restore the UE context may carry first indication information, where the first indication information is used to indicate that the reason for obtaining the UE context is related to the private network subscription information. For the first indication information, please refer to the related description of the first indication information in the above embodiment 1, which will not be repeated here.

S908: RRC is established between the target cell and the UE.

S909, the UE sends an RRC completion message to the target cell.

Exemplarily, the message may indicate that the UE completes RRC access on the target cell side.

S910, the target cell sends an initial UE message to the AMF.

S911, AMF sends an initial context establishment request to the target cell. The initial context establishment request message may carry the private network subscription information of the UE.

S912, the target cell sends an initial context establishment response to the AMF.

S913, the target cell sends a downlink information forwarding message to the UE, wherein the downlink information forwarding message carries the private network subscription information of the UE.

S914, the UE sends an uplink information forwarding message to the target cell, wherein the downlink information forwarding message can be used to indicate that the private network subscription information update is complete.

S915, the target cell sends an uplink NAS transmission to the AMF, wherein the uplink NAS transmission message can be used to indicate that the private network contract information update is complete.

It can be understood that the above-mentioned source cell action can be performed by the access network device where the source cell is located, that is, the second access network device, and the above-mentioned target cell action can be performed by the access network device where the target cell is located, that is, the first access network device.

Solution 2: The method includes: when the first access network device obtains the context of the UE from the second access network device, the second access network device can send the UE context information to the first access network device. The first access network device triggers the RRC recovery process between the first access network device and the UE, and sends the private network subscription information to the UE after the RRC connection between the first access network device and the UE is restored.

Among them, the first access network device is the access network device where the target cell is located, the second access network device is the access network device where the source cell is located, the source cell is the first cell accessed by the terminal device before entering the INACTIVE state, and the target cell is the cell accessed when the terminal device restores the RRC connection from the INACTIVE state.

For the first access network device, the second access network device, and the core network device, please refer to the relevant descriptions of the first access network device, the second access network device, and the core network device in Embodiment 1, which will not be repeated here.

In order to better understand the method provided in Example 3, the following takes the core network device as AMF as an example for explanation, and the private network subscription information update process may be:

For steps A1 to A5, please refer to S901 to S905 for details, which will not be described again here.

A6: The source cell sends a UE context to the target cell, where the UE context includes new private network subscription information.

A7: The target cell sends an RRC recovery message to the UE.

A8. The UE sends an RRC recovery complete message to the target cell.

A9: The target cell sends new private network subscription information to the UE.

A10, the UE sends a configuration completion message to the target cell, where the configuration completion message is used to indicate that the private network subscription information update is complete.

A11, the target cell forwards the UE's configuration completion message to the AMF.

It can be understood that the above-mentioned source cell action can be performed by the access network device where the source cell is located, that is, the second access network device, and the above-mentioned target cell action can be performed by the access network device where the target cell is located, that is, the first access network device.

The second embodiment of the present application introduces a solution. When the target cell fails to obtain the context from the source cell, the target cell triggers the RRC establishment process. Or the target cell successfully obtains the context and triggers the RRC recovery process. The integrity of the communication protocol is supplemented, so as to solve the problem that the private network contract information cannot be updated.

Embodiment 3: This application provides another method for updating private network contract information. Taking the core network device as AMF as an example, as shown in FIG10 , the private network contract information update process may be:

S1001, AMF sends a downlink NAS transmission message to the source cell, in which the NAS-PDU carries new private network subscription information.

In a possible implementation manner, the downlink NAS transmission message may carry new private network subscription information only in the NAS-PDU.

For example, the downlink NAS transmission message includes NAS-PDU and Mobility Restriction List, wherein the NAS-PDU carries new private network subscription information, and the Mobility Restriction List does not carry new private network subscription information.

For another example, the downlink NAS transmission message includes NAS-PDU but does not include Mobility Restriction List, wherein the NAS-PDU carries new private network subscription information.

S1002~S1005 can refer to S902~S905, which will not be repeated here.

S1006. The source cell may send a restore UE context response to the target cell, wherein the restore UE context response carries new subscription information, for example, carries the NAS-PDU sent by the AMF.

S1007, the target cell and the UE perform RRC recovery.

S1008, the UE sends an RRC recovery complete message to the target cell.

Exemplarily, the message may indicate that the UE completes the RRC recovery message on the target cell side.

S1009, the target cell sends a downlink information forwarding message to the UE, wherein the downlink information forwarding message carries the private network subscription information of the UE.

S1010, the UE sends an uplink information forwarding message to the target cell, wherein the downlink information forwarding message can be used to indicate that the private network subscription information update is complete.

S1011, the target cell sends an uplink NAS transmission to the AMF, wherein the uplink NAS transmission message can be used to indicate that the private network contract information update is complete.

S1012, AMF sends a downlink NAS transmission to the target cell, in which the Mobility Restriction List carries the new private network subscription information.

It can be understood that the above-mentioned source cell action can be performed by the access network device where the source cell is located, that is, the second access network device, and the above-mentioned target cell action can be performed by the access network device where the target cell is located, that is, the first access network device. For the first access network device, the second access network device, and the core network device, please refer to the relevant description of the first access network device, the second access network device, and the core network device in Embodiment 1, which will not be repeated here.

The third embodiment of the present application introduces a solution: AMF sends new subscription information twice, notifying UE and base station respectively, so as to avoid further judgment by the source base station. In this way, the behavior of the base station side is basically the same as the existing process, and the protocol is slightly changed.

Embodiment 4: This application provides another method for updating private network contract information. Taking the core network device as AMF as an example, as shown in FIG11 , the private network contract information update process may be:

S1101, AMF determines that the UE is in the INACTIVE state and the source cell is not in the new subscription information.

Optionally, the source cell can be reported to the AMF after the UE is in the INACTIVE state.

S1102, AMF sends a release message to the source cell.

Optionally, the release message may carry first indication information, and the first indication information is used to indicate that the reason for acquiring the UE context is related to the private network subscription information. For the first indication information, please refer to the relevant description of the first indication information in the above embodiment 1, which will not be repeated here.

Optionally, S1103, the source cell sends the RNA range of the UE to the AMF.

By executing step S1103, when AMF initiates paging, it does not need to be within the TAI list range, but only within the RNA range. Generally speaking, the RNA range is smaller than the TAI list range. For example, the TAI list is all cells under base station 1 to base station 10, and the RNA of the UE may be all cells under base station 1 to base station 5. Therefore, if the source base station gives the RNA range to the AMF, the AMF can only page within the RNA range, thereby saving a lot of signaling and resources.

Among them, step S1103 is optional and may be executed or not.

S1104, AMF initiates CN paging.

Among them, if step S1103 is executed, the AMF can initiate CN paging within the RNA range.

If step S1103 is not performed, the AMF can initiate CN paging within the TAI list.

For example, paging initiated by core network equipment (such as AMF) can be called CN Paging. CN paging can be initiated by the AMF of the 5G core network, sending a paging message to the base station, which then transparently transmits it to all UEs connected to its related cells. The UE that monitors the paging message will check whether it contains its own ID. If so, it can initiate an RRC establishment request to connect to the network; if not, it can ignore the paging request.

S1105, the target cell sends a CN paging.

S1106: After receiving the CN paging, the UE in the INACTIVE state establishes an RRC connection with the target cell.

S1107~S1112 can refer to S910~S915, which will not be repeated here.

It can be understood that the above-mentioned source cell action can be performed by the access network device where the source cell is located, that is, the second access network device, and the above-mentioned target cell action can be performed by the access network device where the target cell is located, that is, the first access network device. For the first access network device, the second access network device, and the core network device, please refer to the relevant description of the first access network device, the second access network device, and the core network device in Embodiment 1, which will not be repeated here.

In the fourth embodiment of the present application, a solution is introduced: AMF initiates RRC release with NPN-related reasons, and the source base station sends the RNA of the UE to AMF, so that AMF can initiate CN paging in RNA, which saves a lot of overhead compared to paging in TAI List. Moreover, through the solution of the fourth embodiment, INACTIVE UE can complete the NPN subscription information update.

Embodiment 5: This application provides another method for updating private network contract information. The method includes:

When the source cell receives the new private network subscription information sent by AMF, it treats the cells in RNA differently:

For cells that are still in the new private network subscription information, RAN paging is sent, and cells that are still in the new private network subscription information perform RAN paging in the cells. If the UE receives a paging message in a cell that is still in the new private network subscription information, RRC recovery is initiated. Optionally, RAN paging can carry I-RNTI.

For cells that are not within the scope of the new private network contract information, a Paging carrying indication information is sent, and the indication information is used to indicate that the cell does not belong to the contracted cell indicated by the private network contract information. Cells that are not within the scope of the new private network contract information perform CN paging within the cell. If the UE receives CN paging in a cell that is not within the scope of the new private network contract information, an RRC establishment request is initiated in the cell. Optionally, the indication information can be S-TMSI. In addition, the Paging can also carry I-RNTI.

In order to better understand the solution provided in Embodiment 5 of the present application, taking the core network device as AMF as an example, as shown in FIG12, the private network subscription information update process may be:

For S1201, please refer to S901, which will not be repeated here.

S1201, the source base station sends a paging message to the target base station.

The paging message may carry I-RNTI and/or S-TMSI. Optionally, the above-mentioned I-RNTI or S-TMSI may be indicated per cell, so that the target base station can determine the UE identifier that needs to be carried in the paging message sent by the corresponding cell. Alternatively, the paging message may also carry indication information, which is used to indicate whether the target base station sends a paging message containing I-RNTI or S-TMSI in the corresponding cell, or the indication information is used to indicate whether the cell under the target base station is still within the new private network contract information.

Specifically, (a) if the cell under the target base station is still in the new private network subscription information, the target base station determines, based on the above paging message, a paging message carrying the I-RNTI in the cell.

(b) If the cell under the target base station is not in the new private network subscription information, the target base station determines to send a paging message carrying the S-TMSI in the cell based on the above paging message.

S1203: The target base station sends a paging message carrying the I-RNTI or S-TMSI in the target cell based on the paging message.

S1204: An RRC connection is established between the UE and the target cell.

S1205~S1210 can refer to S910~S915, which will not be repeated here.

It can be understood that the above-mentioned source cell action can be performed by the access network device where the source cell is located, that is, the second access network device, and the above-mentioned target base station and/or target cell action can be performed by the access network device where the target cell is located, that is, the first access network device. For the first access network device, the second access network device, and the core network device, please refer to the relevant description of the first access network device, the second access network device, and the core network device in Embodiment 1, which will not be repeated here.

Embodiment 5 of the present application provides a solution: the source cell treats cells that are still in the new private network contract information and cells that are not in the new private network contract information differently, so that the cells that are not in the new private network contract information can trigger the UE to initiate the RRC establishment process, so that the INACTIVE UE can complete the update of the private network contract information.

Embodiment 6: This application provides another method for updating private network subscription information. This method can be applied to a scenario where the source cell and the target cell are the same base station, and the method includes:

When the source cell receives the new private network subscription information sent by AMF and finds that the target cell is not in the new private network subscription message, it does not release the UE, but sends an RRC establishment to the UE to make the behavior of the UE in the INACTIVE state consistent with that in the IDLE state.

Alternatively, because the base stations where the source cell and the target cell are located have the UE's context and new private network subscription information, the UE can be triggered to perform RRC recovery to complete the update of the private network subscription information.

In order to better understand the solution provided in Embodiment 6 of the present application, taking the core network device as AMF as an example, as shown in FIG13, the private network subscription information update process may be:

S1301~S1304 can refer to S901~S904, which will not be repeated here.

S1305: The target cell determines that it is not included in the new private network contract information.

S1306~S1313, please refer to S908~S915, which will not be repeated here.

It can be understood that the above-mentioned actions of the source cell and the target cell can be executed by the same access network device, that is, the access network device where the source cell and the target cell are located.

In the fifth embodiment of the present application, a solution is introduced for the situation where the source cell and the target cell are the same base station and the target cell is not in the new private network contract information: the base station ignores the new private network contract information, allows the UE to complete RRC recovery, and completes the update of the new private network contract information.

Based on the same inventive concept as the method embodiment, the embodiment of the present application provides a private network contract information updating device. The structure of the device may be as shown in FIG. 14 , including a communication unit 1401 and a processing unit 402 .

In a specific implementation, the device can be specifically used to implement the method executed by the core network device in the embodiments described in Figures 6 to 7. The device can be the core network device itself, or it can be a chip or chipset in the core network device or a chip or a part of the chip used to execute the function of the relevant method. Among them, the communication unit 1401 is used to receive private network information from the first access network device, and the private network information includes the identifier of at least one private network supported by the cell used by the first access network device and the terminal device to restore the radio resource control RRC connection. The processing unit 1402 is used to perform verification based on the private network information and the private network contract information of the terminal device, and the private network contract information is saved by the core network device.

Optionally, when processing unit 1402 performs verification based on the private network information and the private network contract information of the terminal device: if at least one private network identifier in the private network information belongs to the private network contract information, the verification is successful; or, if the private network identifier in the private network information does not belong to the private network contract information, the verification fails.

Communication unit 1401 can also be used to send a release message to the first access network device after receiving private network information from the first access network device, if the private network identifier in the private network information does not belong to the private network contract information, and the release message is used to instruct the first access network device to release the RRC connection between the first access network device and the terminal device.

Exemplarily, the release message carries first indication information, and the first indication information is used to indicate that the reason for the path switching failure is related to the private network contract information.

Exemplarily, the first indication information is an identifier of an invalid private network.

In a specific implementation, the device can be specifically used to implement the method executed by the core network device in the embodiments described in Figures 6 to 7. The device can be the core network device itself, or it can be a chip or chipset in the core network device or a chip or a part of the chip used to execute the function of the related method. Among them, the processing unit 1402 is used to restore the radio resource control RRC connection with the terminal device; the communication unit 1401 is used to send private network information to the core network device, and the private network information includes at least one private network identifier supported by the cell where the first access network device and the terminal device restore the radio resource control RRC connection.

The communication unit 1401 may also be used to receive private network subscription information of the terminal device after sending the private network information to the core network device.

The communication unit 1401 can also be used to receive a release message from the core network device after sending private network information to the core network device, and the release message is used to instruct the first access network device to release the RRC connection between the first access network device and the terminal device.

Exemplarily, the release message carries first indication information, and the first indication information is used to indicate the reason for releasing the terminal device and/or the reason for the path switching failure.

Exemplarily, the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the scope of the private network contract; unreasonable private network access.

In a specific implementation, the device can be specifically used to implement the method executed by the second access network device in the embodiment described in FIG8 . The device can be the second access network device itself, or a chip or chipset in the second access network device or a part of a chip or a chip used to execute the function of the related method. Among them, the communication unit 1401 is used to send and receive signals; the processing unit 1402 is used to execute through the communication unit 1401: receiving a third message from the first access network device, the third message is used to request the context information of the terminal device from the second access network device; if at least one of the second access network device and the first access network device does not belong to the contracted cell indicated by the private network contract information, a fourth message is sent to the first access network device, the fourth message is used to indicate that the first access network device failed to obtain the context information, and the fourth message carries indication information, and the indication information is used to indicate that the reason for the failure to obtain the context information is related to the private network contract information.

In a specific implementation, the device can be specifically used to implement the method executed by the first access network device in the embodiment described in FIG. 8 . The device can be the first access network device itself, or it can be a chip or chipset in the first access network device or a part of a chip or a chip used to execute the function of the related method. Among them, the communication unit 1401 is used to send and receive signals; the processing unit 1402 is used to execute through the communication unit 1401: sending a third message to the second access network device, the third message is used to request the context information of the terminal device from the second access network device; receiving a fourth message from the second access network device, the fourth message is used to indicate that the first access network device failed to obtain the context information, and the fourth message carries indication information, and the indication information is used to indicate that the reason for the failure to obtain the context information is related to the private network contract information.

Exemplarily, the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the scope of the private network contract; unreasonable private network access.

In a specific implementation, the device can be specifically used to implement the method executed by the core network device in the embodiment described in FIG. 11. The device can be the core network device itself, or a chip or chipset in the core network device or a part of a chip or a chip used to execute the function of the related method. Among them, the processing unit 1402 is used to determine that the second access network device does not belong to the contracted cell of the terminal device, and the second access network device is the access network device that last provided services to the terminal device before the terminal device entered the inactive state; the communication unit 1401 is used to send a first message to the second access network device, and the first message is used to instruct the second access network device to release the context information of the terminal device.

Exemplarily, the release message carries first indication information, and the first indication information is used to indicate that the reason for the path switching failure is related to the private network contract information.

Exemplarily, the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the scope of the private network contract; unreasonable private network access.

The communication unit 101 may also be used to: after sending the first message to the second access network device, receive second information from the second access network device, where the second information is used to indicate access network-based notification area RNA information of the terminal device.

The processing unit 10402 may also be configured to: after the communication unit 1401 receives the second information from the second access network device, send a paging message within the RNA range indicated by the second information.

The division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit. It is understood that the functions or implementations of each unit in the embodiments of the present application may further refer to the relevant description of the method embodiment.

In a possible manner, the communication device may be as shown in FIG15, and the communication device may be a terminal device or a chip in the terminal device, or may be a network or a chip in the network. The communication device may include a processor 1501, a communication interface 1502, and a memory 1503. Among them, the processing unit 1402 may be the processor 1501. The communication unit 1401 may be a communication interface 1502.

The processor 1501 may be a central processing unit (CPU) or a digital processing unit, etc. The communication interface 1502 may be a transceiver, an interface circuit such as a transceiver circuit, etc., or a transceiver chip, etc. The communication device also includes: a memory 1503 for storing programs executed by the processor 1502. The memory 1503 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory 1503 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

The processor 1501 is used to execute the program code stored in the memory 1503, specifically to execute the actions of the above-mentioned processing unit 1402, which will not be described in detail in this application.

The specific connection medium between the communication interface 1501, the processor 1502 and the memory 1503 is not limited in the embodiment of the present application. In FIG. 15 , the memory 1503, the processor 1502 and the communication interface 1501 are connected via a bus 15014, and the bus is represented by a bold line in FIG. 15 . The connection mode between other components is only for schematic illustration and is not limited thereto. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in FIG. 15 , but it does not mean that there is only one bus or one type of bus.

An embodiment of the present invention further provides a computer-readable storage medium for storing computer software instructions required to be executed by the above-mentioned processor, which includes a program required to be executed by the above-mentioned processor.

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 process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

The present application is described with reference to the flowchart and/or block diagram of the method, device (system), and computer program product according to the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the process and/or box in the flowchart and/or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims (10)

1. A method for updating private network contract information, comprising: The core network device receives second indication information from the second access network device, where the second indication information is used to indicate that the second access network device cannot send private network subscription information to the terminal device, the terminal device is in an inactive state, and the second access network device is the access network device to which the terminal device is connected before entering the inactive state; The core network device receives private network information from a first access network device, where the first access network device is an access network device that initiates a radio resource control (RRC) connection recovery request for the terminal device, and the private network information includes an identifier of at least one private network supported by a cell for recovering the RRC connection of the terminal device, and the at least one private network depends on the first public network; The core network device performs verification based on the private network information and the private network subscription information of the terminal device; If the verification is successful, the core network device sends the private network signing information of the terminal device to the first access network device. 2. The method according to claim 1, wherein the core network device performs verification based on the private network information and the private network contract information of the terminal device, comprising: If at least one private network identifier in the private network information belongs to the private network contract information, the verification is successful; Alternatively, if the private network identifier in the private network information does not belong to the private network contract information, the verification fails. 3. The method according to claim 1 or 2, characterized in that after the core network device receives the private network information from the first access network device, it also includes: If the verification fails, the core network device sends a release message to the first access network device, and the release message is used to instruct the first access network device to release the RRC connection between the first access network device and the terminal device. 4. The method as claimed in claim 3 is characterized in that the release message carries first indication information, and the first indication information is used to indicate that the reason for releasing the terminal device and/or the reason for the path conversion failure is related to the private network contract information. 5. The method as claimed in claim 4 is characterized in that the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the scope of the private network contract; unreasonable private network access. 6. A private network contract information updating device, characterized in that the device comprises a processing unit and a transceiver unit, the transceiver unit is used to perform the action of sending and receiving signals in the method as described in any one of claims 1 to 5; the processing unit is used to perform the actions other than sending and receiving signals in the method as described in any one of claims 1 to 5. 7. A private network contract information updating device, characterized in that the device includes a processor and a communication interface, the communication interface is used to receive computer program code or instructions and transmit them to the processor; the processor runs the computer program code or instructions so that the device implements the method described in any one of claims 1-5. 8. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a program, and when the program is read and executed by one or more processors, it can implement the method described in any one of claims 1 to 5. 9. A communication system, comprising: the device as claimed in claim 6. 10. A communication system, comprising: the device as claimed in claim 7.