CN113259924B

CN113259924B - Private network subscription information updating method and device

Info

Publication number: CN113259924B
Application number: CN202010091446.5A
Authority: CN
Inventors: 吴烨丹; 耿婷婷
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Filing date: 2020-02-13
Publication date: 2024-07-05
Anticipated expiration: 2040-02-13

Abstract

The application provides a private network subscription information updating method and device, which are used for perfecting a private network subscription information updating flow of terminal equipment. The method comprises the following steps: the core network device receives private network information from the first access network device, where the private network information includes an identifier of at least one private network supported by a cell used by the first access network device and the terminal device to recover radio resource control connection. The core network device performs verification based on private network information and private network subscription information of the terminal device. In the embodiment of the application, a solution is provided for updating the situation that the source cell and/or the target cell are not in the private network subscription information of the terminal equipment in the inactive state, so that the updating flow of the private network subscription information of the terminal equipment in the inactive state can be perfected.

Description

Private network subscription information updating method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a private network subscription information updating method and apparatus.

Background

In daily life, a public network is generally used for providing network services for terminal equipment. Public networks, i.e. public land mobile networks (public land mobile network, PLMNs), are networks established and operated by the government or its approved operators for the purpose of providing land mobile services to the public. Besides public networks, operators or private persons can build some private networks (NPNs) to meet the demands of users. Private networks may also be referred to as non-public networks, meaning networks that are open to a particular user, such as internal networks built by a company, school, or factory. Terminal equipment not subscribed to the private network is not allowed to access the private network. After signing a contract with a private network, the core network side and the terminal equipment side record the signing information of the terminal equipment, wherein the signing information refers to user access information signed by the terminal equipment with an operator or other private network building companies. If the terminal device signs up, the corresponding network can be accessed according to the network identification in the sign-up information, and the network resource can be used. If the subscription information changes, the core network initiates a User Equipment (UE) configuration update procedure (UE configuration update) to notify the terminal device of the updated subscription information.

For a terminal device in an inactive state (inactive), for updated subscription information, the source cell and/or the target cell may or may not be in the new subscription cell list, and if the source cell and/or the target cell is not in the new subscription cell list, how to update the subscription information in the terminal device is not a good solution at present. In particular, when the target cell is not in the new subscription cell list, the actions of the target base station and the AMF are not related in the current communication protocol, which is a common problem in private network communication.

Disclosure of Invention

The application provides a private network subscription information updating method and device, which are used for perfecting a private network subscription information updating flow of terminal equipment.

In a first aspect, an embodiment of the present application provides a private network subscription information updating method, including: the core network device receives private network information from the first access network device, the private network information including an identity of at least one private network supported by a cell used by the first access network device and the terminal device to recover a radio resource control (radio resource control, RRC) connection. The core network device verifies based on private network information and private network subscription information of the terminal device, wherein the private network subscription information is stored by the core network device. In the embodiment of the application, a solution is provided for updating the situation that the source cell and/or the target cell are not in the private network subscription information of the INACTIVE-state UE, so that the updating flow of the private network subscription information of the terminal equipment in the INACTIVE state can be perfected.

In one possible design, at least one private network depends on a first public network, which is the public network on which the target network selected by the terminal device depends, the network identification of the first public network being a PLMN ID. In the above design, the first access network device may 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 the at least one private network identifier that depends on the first public network.

In one possible design, the identification of the private network comprises a network identification PLMN ID of the public network and an identification CAG ID of the closed access group.

In one possible design, the identification 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 private network information and private network subscription information of the terminal device, including: if at least one private network identifier in the private network information belongs to private network subscription information, the verification is passed; or if the private network identification in the private network information does not belong to the private network subscription information, the verification is not passed. In the above design, the private network identifier in the private network information does not belong to private network subscription information, and the core network device may determine that the first access network device does not have an access condition of a subscription cell of the terminal device, so as to determine that the first access network device fails to verify.

In one possible design, after the core network device receives the private network information from the first access network device, the method further includes: and if the private network identifier in the private network information does not belong to private network subscription information, the core network equipment sends a release message to the first access network equipment, wherein the release message is used for indicating the first access network equipment to release the RRC connection with the terminal equipment. According to the design, when the first access network equipment fails to pass verification, resources can be timely released through the release message, so that the resource utilization rate can be improved.

In one possible design, the release message carries first indication information, where the first indication information is used to indicate that a reason for releasing the terminal device and/or a reason for a path conversion failure is related to private network subscription information. Through the design, the first access network equipment can acquire the reason of the path conversion failure, so that the data statistics can be facilitated.

In one possible design, the first indication information includes at least one of: invalid private network identification; a private network identity that is not supported; is not in the private network signing range; unreasonable private network access. Through the design, the first access network equipment can obtain the reason of the path conversion failure more accurately.

In a second aspect, an embodiment of the present application provides a private network subscription information updating method, including: the first access network equipment restores the RRC connection with the terminal equipment; the first access network device sends private network information to the core network device, wherein the private network information comprises an identifier of at least one private network supported by a cell of which the first access network device and the terminal device recover RRC connection. In the embodiment of the application, a solution is provided for updating the situation that the source cell and/or the target cell are not in the private network subscription information of the INACTIVE-state UE, so that the updating flow of the private network subscription information of the terminal equipment in the INACTIVE state can be perfected.

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

In one possible design, the identification of the private network 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 private network subscription information of the terminal device. In the above design, the first access network device may acquire private network subscription information of the terminal device after the verification is passed.

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 being used to instruct the first access network device to release the RRC connection with the terminal device. According to the design, when the first access network equipment fails to pass verification, resources can be timely released through the release message, so that the resource utilization rate can be improved.

In a third aspect, an embodiment of the present application provides a private network subscription information updating method, including: the second access network device receives a third message from the first access network device, where the third message is used to request 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 subscription cell indicated by the private network subscription information, the second access network device sends a fourth message to the first access network device, wherein the fourth message is used for indicating that the first access network device fails to acquire the context information, the fourth message carries indication information, and the indication information is used for indicating that the reason of the failure to acquire the context information is related to the private network subscription information.

The embodiment of the application introduces a solution, and when the first access network equipment fails to acquire the context from the second access network equipment, the first access network equipment triggers the RRC establishment process. Or the first access network equipment acquires the context successfully and triggers an RRC recovery process. The integrity of the communication protocol is supplemented, so that the problem that updating cannot be completed in private network subscription information can be solved.

In a fourth aspect, an embodiment of the present application provides a private network subscription information updating method, including: the first access network equipment sends a third message to the second access network equipment, wherein the third message is used for requesting context information of the terminal equipment from the second access network equipment; the first access network equipment receives a fourth message from the second access network equipment, wherein the fourth message is used for indicating that the first access network equipment fails to acquire the context information, the fourth message carries indication information, and the indication information is used for indicating that the reason of the failure to acquire the context information is related to private network subscription information. The embodiment of the application introduces a solution, and when the first access network equipment fails to acquire the context from the second access network equipment, the first access network equipment triggers the RRC establishment process. Or the first access network equipment acquires the context successfully and triggers an RRC recovery process. The integrity of the communication protocol is supplemented, so that the problem that updating cannot be completed in private network subscription information can be solved.

In a fifth aspect, an embodiment of the present application provides a private network subscription information updating method, including: the core network equipment determines that the second access network equipment does not belong to a subscription cell of the terminal equipment, and the second access network equipment is the access network equipment which finally provides service for the terminal equipment before the terminal equipment enters an inactive state; the core network device sends a first message to the second access network device, where the first message is used to instruct the second access network device to release the context information of the terminal device.

The embodiment of the application introduces a solution: the AMF initiates RRC release when the first access network equipment does not belong to private network subscription information, so that the INACTIVE UE can complete NPN subscription information updating, and the resource utilization rate can be improved.

In one possible design, the first message carries first indication information, where the first indication information is used to indicate that a cause of releasing the context information is related to private network subscription information. Through the design, the first access network equipment can acquire the reason of the path conversion failure, so that the data statistics can be facilitated.

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 being used to instruct the terminal device to access network based notification area (RAN-Based notification area, RNA) information. In the above design, the second access network device passes through the RNA of the UE, so that the AMF initiates CN paging in the RNA, which saves a lot of overhead compared to paging in a tracking area identity (TRACKING AREA IDENTITY, TAI List).

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

In one possible design, before the core network device sends the first message to the access network device, the method further comprises: the core network device receives a second message from the access network device, where the second message is used to indicate that the terminal device is in an inactive state.

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

The embodiment of the application provides a solution: the second access network device performs differential treatment on the cells still in the new private network subscription information and the cells not in the new private network subscription information, so that the cells not in the new private network subscription information can trigger the UE to initiate an RRC establishment process, and the INACTIVE UE can complete private network subscription information updating.

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

In one possible design, the non-access stratum user identity 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 private network subscription information updating method, including: the first access network equipment receives a first paging message from the second access network equipment, wherein the first paging message carries indication information, and the indication information is used for indicating that the first access network equipment does not belong to a subscription cell indicated by private network subscription information. The first access network equipment sends a second paging message, and the second paging message is used for triggering the terminal equipment to establish RRC connection with the first access network equipment.

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

In an eighth aspect, an embodiment of the present application provides a private network subscription information updating method, including: the access network equipment receives a first message from the core network equipment, wherein the first message carries private network subscription information updated by the terminal equipment; the access network equipment sends a second message, wherein the second message is used for triggering the terminal equipment to recover the radio resource control connection; the access network equipment receives a third message from the terminal equipment, wherein the third message is used for requesting to recover the RRC connection; the access network equipment determines that the access network equipment does not belong to a subscription cell indicated by private network subscription information; the access network equipment restores or reestablishes the RRC connection with the terminal equipment; the access network device sends private network subscription information to the terminal device.

The embodiment of the application introduces a solution for the case that the source cell and the target cell are the same base station and the target cell is not in the new private network subscription information: the base station ignores the new private network subscription information, so that the UE completes RRC recovery and completes the update of the new private network subscription information.

In a ninth aspect, the present application provides a private network subscription information updating apparatus, where the apparatus may be a core network device, or may be a chip or a chipset in the core network device. The apparatus may include a processing unit and a transceiving unit. When the apparatus is a core network device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the apparatus may further include a storage unit, which may be a memory; the storage unit is configured 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. When the apparatus 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, a circuit, or the like; the processing unit executes instructions stored in a storage unit, which may be a storage unit (e.g. a register, a cache, etc.) in the chip or the chipset, or may be a storage unit (e.g. a read only memory, a random access memory, etc.) in the communication device that is located outside the chip or the chipset, so that the core network device performs the corresponding functions in the first aspect or the fifth aspect.

In a tenth aspect, the present application provides a private network subscription information updating apparatus, where the apparatus may be an access network device, or may be a chip or a chipset in the access network device. The apparatus may include a processing unit and a transceiving unit. When the apparatus is an access network device, the processing unit may be a processor and the transceiver unit may be a transceiver; the apparatus may further include a storage unit, which may be a memory; the storage unit is configured to store instructions, and the processing unit executes the instructions stored by the storage unit, so that the access network device performs the corresponding functions in the second aspect, the third aspect, the fourth aspect, the sixth aspect, the seventh aspect, or the eighth aspect. When the apparatus is a chip or a 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, a circuit, or the like; the processing unit executes instructions stored in a storage unit, which may be a storage unit (e.g. a register, a cache, etc.) in the chip or the chipset, or may be a storage unit (e.g. a read only memory, a random access memory, etc.) in the communication device, which is located outside the chip or the chipset, to cause 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.

In an eleventh aspect, there is provided an apparatus comprising: a processor, a communication interface, and a memory. The communication interface is used to transfer information, and/or messages, and/or data between the device and other devices. The memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the method of any of the first or fifth aspects described above.

In a twelfth aspect, there is provided an apparatus comprising: a processor, a communication interface, and a memory. The communication interface is used to transfer information, and/or messages, and/or data between the device and other devices. The memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the method according to any of the second or third or fourth or sixth or seventh or eighth aspects described above.

In a thirteenth aspect, the present application also provides a communication system, the system comprising a core network device according to any of the embodiments of the first aspect, and a first access network device according to any of the embodiments of the second aspect.

In a fourteenth aspect, the present application also provides a communication system comprising a second access network device according to any of the embodiments of the third aspect, and a first access network device according to any of the embodiments of the fourth aspect.

In a fifteenth aspect, the present application also provides a communication system, the system comprising a core network device in any one of the embodiments of the fifth aspect.

In a sixteenth aspect, the present application also provides a communication system comprising a second access network device according to any of the embodiments of the sixth aspect, and a first access network device according to any of the embodiments of the seventh aspect.

In a seventeenth aspect, the present application further provides a communication system, which includes an access network device in any embodiment of the eighth aspect.

In an eighteenth aspect, the present application also provides a computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the method of the first or fifth aspect described above.

In a nineteenth aspect, the present application also provides a computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the method of the second or third or fourth or sixth or seventh or eighth aspects described above.

In a twentieth aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first or fifth aspect described above.

In a twenty-first aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the second or third or fourth or sixth or seventh or eighth aspects described above.

Drawings

Fig. 1 is a schematic diagram of three states of a terminal device according to an embodiment of the present application;

fig. 2 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of an access network device according to an embodiment of the present application;

Fig. 4 is a schematic structural diagram of an access network device according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an access network device according to an embodiment of the present application;

Fig. 6 is a flow chart of a private network subscription information updating method according to an embodiment of the present application;

fig. 7 is a schematic diagram of a private network subscription information updating process according to an embodiment of the present application;

fig. 8 is a schematic diagram of a private network subscription information updating process according to an embodiment of the present application;

Fig. 9 is a schematic diagram of a private network subscription information updating process according to an embodiment of the present application;

fig. 10 is a schematic diagram of a private network subscription information update procedure according to an embodiment of the present application;

Fig. 11 is a schematic diagram of a private network subscription information updating process according to an embodiment of the present application;

Fig. 12 is a schematic diagram of a private network subscription information update procedure according to an embodiment of the present application;

fig. 13 is a schematic diagram of a private network subscription information update procedure according to an embodiment of the present application;

Fig. 14 is a schematic diagram of a private network subscription information updating device according to an embodiment of the present application;

fig. 15 is a schematic diagram of a private network subscription information updating apparatus according to an embodiment of the present application.

Detailed Description

To facilitate an understanding of embodiments of the present application, the following terms relating to embodiments of the present application are presented:

1. Public network

In daily life, a public network is generally used for providing network services for terminal equipment. Public networks, i.e. public land mobile networks (public land mobile network, PLMNs), are networks established and operated by the government or its approved operators for the purpose of providing land mobile services to the public. The network is typically interconnected with a public switched telephone network (public switched telephone network, PSTN) to form a communications network on a regional or national scale.

Different PLMN networks may be distinguished by different PLMN Identities (IDs). The PLMN identity consists of a mobile country number (mobile contrary code, MCC) and a mobile network number (MNC). Where MCC uniquely indicates the country to which the mobile subscriber belongs, e.g. chinese MCC 460.MNC uniquely represents a network in that country, e.g. MNC for chinese movement is 00 and MNC for chinese communication is 01.

2. Private network

In addition to public networks, operators or private persons may also build some private networks (NPN) to meet the needs of users for some purposes. Private networks may also be referred to as non-public networks, meaning networks that are open to a particular user, such as internal networks built by a company, school, or factory. Terminal equipment not subscribed to the private network is not allowed to access the private network. The private network is divided into a dependent private network and an independent private network.

(1) Dependent private network

Network resources used by a non-independent private network (NSA-NPN, or public network integrated non-public network, PNI-NPN) are part of a public network. It can also be said that the dependent private network relies on (rely on) the public network, also called closed access group (closed access group, CAG). The identification of the non-independent private network comprises two parts, namely PLMN ID and CAG ID, wherein the PLMN ID of the non-independent private network is consistent with the relied public network. The CAG ID of each of the dependent private networks is unique to the plurality of dependent private networks under the same public network, that is, the plurality of dependent private networks under the same public network can be distinguished only by the CAG ID.

For example, the identity of the dependent private network #1 may be expressed as: plmn#1cag#1;

The identity of the dependent private network #2 can be expressed as: PLMN#1CAG#2.

That is, the dependent private network #1 and the dependent private network #2 are private networks built depending on the public network identified as PLMN # 1. In some cases, the two private networks may be distinguished by only cag#1 and cag#2.

According to the current communication protocol, since the CAG network uses public network resources, the terminal device can be handed over and cell reselected between the CAG network and the public network. The switching means that the terminal equipment in the connection state disconnects from the current service cell and connects with the target cell under the control of the base station. Cell reselection refers to the process of cell reselection where after a terminal device in idle/deactivated state resides in one cell, the terminal device may need to be changed to another higher priority or better signaling cell residence as the terminal device moves.

(2) Independent private network

The stand-alone private Network (SNPN) refers to a private Network that may not rely on the Network functions of a public Network. Similarly, the identity of the independent private network is also divided into two parts, PLMN ID and NID. For an independent private network that relies on a public network, its PLMN ID is consistent with the public network relied on, and for an independent private network that does not rely on a public network (e.g., may be an enterprise's own deployment), its MCC for PLMN ID is 999. Whereas the NID of each non-independent private network is unique for a plurality of independent private networks that depend on the same public network, i.e. it can be distinguished only by NID for a plurality of independent private networks that depend on the same public network.

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

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

The identity of independent private network #3 can be expressed as: plmn#3 (mcc=999) nid#1.

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

The MCC of the PLMN ID of the independent private network #3 is 999, which indicates that the independent private network #3 is an independent private network deployed by an enterprise or the like without an operator.

As a possible way, the independent private network does not support the switching and cell reselection of the terminal device between the independent private network and the public network, the non-independent private network and other independent private networks, i.e. the terminal device in a connected state cannot be switched 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; an idle/deactivated state terminal device cannot reselect from an independent private network cell to a public network cell and vice versa. It is to be appreciated that as another possible implementation, the independent private network may support handover and cell reselection of the terminal device between the independent private network and the public network, the non-independent private network, and other independent private networks.

3. RRC state of terminal equipment

In NR, the RRC state of the UE includes a CONNECTED state (rrc_connected), a deactivated state or a third state (rrc_inactive), an IDLE state (rrc_idle), where when the UE is in the rrc_connected state, the UE has established a link with both the base station and the core network, and when data arrives in the network, the data can be directly transmitted to the UE; when the UE is in an RRC_INACTIVE state, the UE establishes a link with the base station and the core network before, but the link from the UE to the base station is released, the base station stores the context of the UE although the link is released, and when data needs to be transmitted, the base station can recover the link in time; when the UE is in rrc_idle state, there is no link between the UE and the base station and between the UE and the network, and when there is data to be transmitted, a link between the UE and the base station and between the UE and the core network needs to be established. The three state transition is shown in fig. 1.

4. Subscription information

The subscription information refers to user admission information signed by the terminal device with an operator or other network-building company. If the terminal device signs up, the corresponding network can be accessed according to the network identification in the sign-up information, and the network resource can be used. If the subscription information is stored in the core network side and the terminal equipment side, the core network initiates a UE configuration update flow (UE configuration update) to inform the terminal equipment side.

It should be noted that, as the technology is continuously developed, the terms of the embodiments of the present application may be changed, but all the terms are within the protection scope of the present application.

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

The architecture of the communication system can comprise network opening function network elements, strategy control function network elements, data management network elements, application function network elements, core network access and mobility management function network elements, session management function network elements, terminal equipment, access network equipment, user plane function network elements and data networks. Wherein fig. 2 shows a possible example of architecture of the communication system, specifically comprising: a network opening function (network exposure function, NEF) network element, a policy control function network element (policy control function, PCF) network element, a data management network element (unified DATA MANAGEMENT, UDM) network element, AN application function network element (application function, AF) network element, AN AMF network element, a session management function network element (session management function, SMF) network element, a UE, AN Access Network (AN) device, a user plane function (user plane function, UPF) network element, and a Data Network (DN). The AMF network element and the terminal equipment can be connected through AN N1 interface, the AMF and the AN equipment can be connected through AN N2 interface, the AN equipment and the UPF can be connected through AN N3 interface, the SMF and the UPF can be connected through AN N4 interface, and the UPF and the DN can be connected through AN N6 interface. The interface name is merely an example, and embodiments of the present application are not particularly limited in this respect. It should be understood that the embodiments of the present application are not limited to the communication system shown in fig. 2, and the names of the network elements shown in fig. 2 are only illustrated herein as an example, and are not limiting of the network elements included in the architecture of the communication system to which the method of the present application is applicable. The functions of the various network elements or devices in the communication system are described in detail below:

The terminal device, which may also be referred to as a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device that provides voice and/or data connectivity to a user. For example, the terminal device may include a handheld device having a wireless connection function, an in-vehicle device, and the like. Currently, the terminal device may be: a mobile phone, a tablet, a notebook, a palm, a mobile internet device (mobile INTERNET DEVICE, MID), a wearable device, a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (self-driving), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), or the like. The terminal device shown in fig. 2 is shown as a UE, and is merely exemplary and not limited thereto.

The radio access network may be AN Access Network (AN) shown in fig. 2, and provides radio access services to the terminal device. The access network device is a device for accessing the terminal device to a wireless network in the communication system. The access network device is a node in a radio access network, which may also be referred to as a base station, and may also be referred to as a radio access network (radio access network, RAN) node (or device). Currently, some access network devices are exemplified by: a gNB, a transmission reception point (transmission reception point, TRP), an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), or a wireless fidelity (WIRELESS FIDELITY, wifi) Access Point (AP), etc.

The radio access network device in the embodiment of the present application may split the radio access network device into two parts according to the protocol stack function: a centralized unit (centralized unit, CU) and a Distributed Unit (DU). Wherein a radio access network device may comprise a CU and at least one DU, as shown in fig. 3. The CU is connected to at least one DU and may be used to manage or control the at least one DU. This structure can disassemble the protocol layers of the radio access network device in the communication system, wherein part of the protocol layer functions are implemented in the CU, and the rest or all of the protocol layer functions are distributed in the DU, so that the CU centrally controls the DU. Taking the radio access network device as the gNB, protocol layers of the gNB include a radio resource control (radio resource control, RRC) layer, a service data adaptation protocol (SERVICE DATA adaptation protocol, SDAP) layer, a packet data convergence protocol (PACKET DATA convergence protocol, PDCP) layer, a radio link control (radio link control, RLC) layer, a medium access control (MEDIA ACCESS control, MAC) layer, and a physical layer. Among them, a CU may be used to implement functions of an RRC layer, an SDAP layer, and a PDCP layer, and a DU may be used to implement functions of an RLC layer, a MAC layer, and a physical layer. The embodiment of the application does not specifically limit the protocol stacks included in the CU and the DU. The CU and the DU may be connected by using an F1 interface, where the CU is connected to other radio access network devices by using an Xn interface, and the CU is connected to a 5G core network (5G core,5 gc) by using an NG interface, as shown in fig. 4.

Illustratively, a CU in an embodiment of the present application may be further divided into a control plane (CU-CP) network element and at least one user plane (CU-UP) network element. Wherein the CU-CP may be used for control plane management and the CU-UP may be used for user plane data transmission. The interface between CU-CP and CU-UP may be the E1 port. The interface between the CU-CP and the 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. And the CU-UP can be connected through an Xn-U port to carry out user plane data transmission. For example, taking the gNB as an example, the structure of the gNB may be as shown in fig. 5.

The data network, such as the Data Network (DN) shown in fig. 2, may be the Internet (Internet), an IP multimedia service (IP Multi-MEDIA SERVICE, IMS) network, a regional network (i.e., a local network, such as a mobile edge computing (mobile edge computing, MEC) network), or the like. The data network comprises an application server, and the application server provides business service for the terminal equipment through data transmission with the terminal equipment.

The core network is used for accessing the terminal equipment to DN which can realize the service of the terminal equipment. The following describes the functions of the various network elements in the core network:

The core network access and mobility management function network element can be used for managing the access control and mobility of the terminal equipment, in practical application, the core network access and mobility management function network element comprises a mobility management function in a Mobility MANAGEMENT ENTITY (MME) in a network frame in long term evolution (long term evolution, LTE), and is added with an access management function, and can be particularly responsible for registration, mobility management, tracking area update flow, reachability detection, selection of session management function network elements, mobility state transition management and the like of the terminal equipment. For example, in 5G, the core network access and mobility management function element may be an AMF (ACCESS AND mobility management function) element, for example, as shown in fig. 2, and in future communications, such as 6G, the core network access and mobility management function element may still be an AMF element, or have other names, which is not limited by the present application. When the core network access and mobility management function network element is an AMF network element, the AMF may provide Namf services.

The session management function network element can be used for being responsible for session management (including session establishment, modification and release) of the terminal equipment, selection and reselection of user plane function network elements, internet protocol (internet protocol, IP) address allocation, quality of service (quality of service, qoS) control of the terminal equipment, and the like. For example, in 5G, the session management function element may be a SMF (session management function) element, such as shown in fig. 2, and in future communications, such as 6G, the session management function element may still be an SMF element, or have other names, which is not limited by the present application. The SMF may provide Nsmf services when the SMF network element is the session management function network element.

The policy control function network element can be used for taking charge of policy control decision, providing functions such as service data flow based and application detection, gating, qoS, flow based charging control and the like. For example, in 5G, the policy control function element may be a PCF (policy control function) element, such as shown in fig. 2, and in future communications, such as 6G, the policy control function element may still be a PCF element, or have other names, which is not limited by the present application. When the policy control function network element is a PCF network element, the PCF network element may provide Npcf services.

The application function network element has the main functions of interacting with a third generation partnership project (the 3rd generation partnership project,3GPP) core network to provide services so as to influence service flow routing, access network capability opening, policy control and the like. For example, in 5G, the application function network element may be an AF network element, for example, as shown in fig. 2, and in future communications, such as 6G, the application function network element may still be an AF network element, or have other names, which is not limited by the present 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 for managing subscription data of the terminal equipment, registration information related to the terminal equipment and the like. For example, in 5G, the data management network element may be a unified data management network element (unified DATA MANAGEMENT, UDM), such as shown in fig. 2, and in future communications, such as 6G, the data management network element may still be a UDM network element, or have other names, which is not limited by the present application. When the data management network element is a UDM network element, the UDM network element may provide Nudm services.

The network open function network element may be used to enable the 3GPP to securely provide network service capabilities to an AF (e.g., service capability Server (Services Capability Server, SCS), application Server (Application Server, AS), etc.) of a third party, etc. For example, in 5G, the network element may be a NEF, such as shown in fig. 2, and in future communications, such as 6G, the network element may still be a NEF element, or have other names, which is not limited by the present application. When the network open function element is a NEF, the NEF may provide Nnef services to other network function elements.

The above network elements in the core network may also be referred to as functional entities, which may be network elements implemented on dedicated hardware, software instances running on dedicated hardware, or instances of virtualized functions on a suitable platform, for example, the above virtualized platform may be a cloud platform.

It should be noted that the architecture of the communication system shown in fig. 2 is not limited to only including the network elements shown in the drawing, but may also include other devices not shown in the drawing, and the specific embodiments of the present application are not listed here.

It should be noted that, the embodiment of the present application is not limited to the distribution form of each network element in the core network, and the distribution form shown in fig. 2 is only exemplary, and the present application is not limited thereto.

For convenience of explanation, the network elements shown in fig. 2 are taken as examples in the following description, and XX network elements are directly and simply referred to as XX, for example, AMF network elements are simply referred to as AMF. It should be understood that the names of all network elements in the present application are merely examples, and may be called other names in future communications, or the network elements involved in the present application may be replaced by other entities or devices having the same functions in future communications, and the present application is not limited to this. The description is unified, and the following description is omitted.

Note that the communication system shown in fig. 2 does not limit the communication system to which the embodiment of the present application is applicable. The communication system architecture shown in fig. 2 is a 5G system architecture, and optionally, the method of the embodiment of the present application is also applicable to various future communication systems, such as a 6G or other communication networks.

Taking CAG as an example, the description about subscription information in the protocol is:

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

A list of allowed access CAG cells, meaning that the terminal device can access these CAG cells, and the remaining non-mentioned CAG cells cannot.

Only access to the CAG indication is allowed, which if taken means that the terminal device cannot access the public network.

Alternatively, the CAG information may be configured for each PLMN.

For the terminal device in Inactive, as a possible implementation manner, the AMF sends downlink non-access stratum (NAS) transmission (DOWNLINK NAS TRANSPORT) to the source base station when triggering the configuration update procedure, where the downlink NAS transmission carries NAS-protocol data units (protocol data unit, PDUs) and a mobility constraint list (Mobility Restriction List), where the NAS-PDUs are sent to the terminal device by the AMF, and the base station transparently transmits the NAS-PDUs to the terminal device when receiving the NAS-PDUs. Mobility Restriction List is that AMF sends to base station, NAS-PDU and Mobility Restriction List both carry updated private network subscription information. The source base station is the last service base station before the terminal equipment enters the inactive state from the connected state. The source base station sends paging messages to the base stations in the RNA of the terminal equipment, the base stations are transmitted to all the UE connected with the source base station, the UE which monitors the paging messages checks whether the UE contains the I-RNTI of the source base station or not, and if so, an RRC recovery request is initiated to the base station to which the current service cell belongs. If the base station to which the current serving cell belongs is the source base station, the terminal device can receive updated private network subscription information sent by the source base station. If the base station to which the current serving cell belongs is a target base station different from the source base station, the terminal device may receive updated private network subscription information at the target base station. The target base station may obtain updated private network subscription information of the terminal device from the source base station or from the core network device, which is not limited in the embodiment of the present application.

Taking the example that the target base station acquires updated private network subscription information of the UE from the core network device AMF, for the terminal device at INACTIVE, if the source base station receives DOWNLINK NAS TRANSPORT sent from the AMF, the source base station initiates paging of the corresponding INACTIVE UE. If the target base station to which the INACTIVE UE initiates access is not the source base station (i.e., the last serving base station (LAST SERVING g nb)), the source cell may send indication information to the AMF, where the indication information is used to indicate that the source base station cannot send updated subscription information to the UE. And the AMF sends DOWNLINK NAS TRANSPORT containing updated private network subscription information to the target base station after finishing path switching (PATH SWITCH) by the target base station, and the target base station forwards the NAS-PDU to the UE.

For updated subscription information, the source base station and the target base station may or may not be in the new subscription cell list, and if the source base station and the target base station are not in the new subscription cell list, how the AMF updates the subscription information in the terminal device does not have a good solution at present.

Based on the above, the application provides a private network subscription information updating method and device, which are used for perfecting the updating flow of private network subscription information of terminal equipment in an INACTIVE state. The method and the device are based on the same inventive concept, and because the principles of solving the problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repetition is not repeated.

The plural numbers referred to in the embodiments of the present application mean two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. Also, it should be understood that in the description of embodiments of the present application, the words "first," "second," and the like are used merely for distinguishing between the descriptions and not be construed as indicating or implying a relative importance or order.

Embodiments of the present application will be described in detail with reference to specific scenarios.

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

Referring to fig. 6, a flowchart of a private network subscription information updating method provided by the present application is shown. The method comprises the following steps:

s601, the first access network device resumes the RRC connection with the terminal device.

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

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

The private network information comprises an identifier of at least one private network supported by a cell for recovering RRC connection of the first access network device and the terminal device. Correspondingly, the core network device may receive private network information sent by the first access network device.

The core network device may determine an identity 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 through a path switching request message.

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

The embodiment of the application is not limited to the type of the 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 naming, and may be named otherwise in future communication developments, and the private network in the embodiments of the present application may be understood as the private network in the embodiments of the present application as long as the functions of the private network in the embodiments of the present application can be implemented.

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

If the private network is a non-independent private network, the private network identifier may include two parts, namely a PLMN ID and a CAG ID, where the PLMN ID is consistent with the depending public network ID. The CAG ID for each of the dependent private networks is unique to a plurality of dependent private networks under the same public network. For example, the identity of the dependent private network #1 may be expressed as: plmn#1cag#1; the identity of the dependent private network #2 can be expressed as: PLMN#1CAG#2. The non-independent private network #1 and the non-independent private network #2 are private networks built depending on the public network identified as PLMN # 1.

If the private network is an independent private network, the private network identifier may include two parts, namely a PLMN ID and a NID, for example, the private network identifier may be plmn#1. For an independent private network that relies on a public network, its PLMN ID is consistent with the public network relied on, and for an independent private network that does not rely on a public network (e.g., may be self-deployed by the enterprise), its MCC for PLMN ID is a fixed value, such as 999. For example, the identity of independent private network #1 may be expressed as: PLMN#1NID#1; the identity of independent private network #2 can be expressed as: PLMN#1NID#2; the identity of independent private network #3 can be expressed as: plmn#3 (mcc=999) nid#1. Wherein, the independent private network #1 and the independent private network #2 are private networks built depending on the public network identified as PLMN #1.

In one exemplary illustration, the first access network device may be an access network device that is accessed by the terminal device when the RRC connection is restored from the INACTIVE state.

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

And S603, the core network equipment verifies based on private network information and private network subscription information of the terminal equipment.

Optionally, private network subscription information is stored for the core network device.

In the embodiment of the application, a solution is provided for updating the situation that the source cell and/or the target cell are not in the private network subscription information of the INACTIVE-state UE, so that the updating flow of the private network subscription information of the terminal equipment in the INACTIVE state can be perfected.

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

By way of example, assuming that the private network subscription information includes plmn#1cag#1, plmn#1cag#2, and plmn#2cag#2, the private network information transmitted 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 subscription information of the terminal device, it may be determined that authentication is passed.

If the private network identification in the private network information does not belong to the updated private network subscription information, the verification fails or fails.

By way of example, assuming that the private network subscription information includes plmn#1cag#1, plmn#1cag#2, and plmn#2cag#2, the private network information transmitted by the first access network device includes plmn#1cag#5, plmn#1cag#3, and plmn#1cag#4, and neither plmn#1cag#5, plmn#1cag#3, and plmn#1cag#4 in the private network information is included in the private network subscription information of the terminal device, it may be determined that the authentication is not passed.

Further, if the verification is passed, the core network device may send private network subscription information of the terminal device to the first access network device. It can be appreciated that the private network subscription information may be the latest private network subscription information. Or the private network subscription information may be updated private network subscription information.

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

Or the first indication information is used for indicating that the reason of the path conversion failure is related to private network subscription information.

Or the first indication information is used for indicating that the reason for releasing the terminal equipment and the reason for the failure of path conversion are related to private network subscription information.

In a possible embodiment, the first indication information may include, but is not limited to, at least one of: invalid private network identification; a private network identity that is not supported; is not in the private network signing range; unreasonable private network access.

In another possible implementation manner, if the verification is not passed, the core network device may send first notification information to the first access network device, where the first notification information is used to notify the first access network device that the terminal device accesses through the public network.

In some embodiments, before the core network device may send the release message to the first access network device, the core network device may send NAS-PDUs carrying private network subscription information to the first access network device, and the NAS-PDUs are transparently transmitted to the terminal device by the first access network device. By the mode, the terminal equipment can update private network subscription information in time, so that on one hand, the updating time can be saved, and on the other hand, the resource utilization rate can be improved.

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

In a possible implementation manner, before the core network device receives the path conversion request from the first access network device, the core network device may trigger the private network subscription information update procedure. For example, the core network device may send private network subscription information to the second access network device, where the second access network device is the access network device to which the terminal device is connected before entering the INACTIVE state.

After the core network device triggers the private network subscription information updating process, the core network device may receive second indication information from the second access network device, where the second indication information is used to instruct the core network device to send the private network subscription information to the first access network device after receiving the private network information of 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 subscription information to the terminal device.

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

In an exemplary illustration, the first access network device and the second access network device may be the same access network device, and a cell (hereinafter referred to as a source cell for descriptive convenience) to which the terminal device accesses before entering the INACTIVE state and a cell (hereinafter referred to as a target cell for descriptive convenience) to which the terminal device accesses when recovering the RRC connection from the INACTIVE state are the same cell.

In another exemplary illustration, 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 illustration, 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 by the embodiment of the present application, the private network subscription information updating process is described in detail below in conjunction with a specific scenario. For convenience in description, the following description will take a core network device as an AMF, a private network as a CAG, and a public network as a PLMN as an example.

Scene one: the UE1 accesses a first cell of a source base station before entering an INACTIVE state, and accesses a second cell of a target base station when the UE1 resumes RRC connection from the INACTIVE state, wherein the source base station and the target base station are different base stations.

The private network subscription information update flow may be as shown in fig. 7:

s701, the AMF sends private network subscription information of the UE1 to the source base station. The private network subscription information may be stored in the AMF. S702 is performed.

In one exemplary illustration, the private network subscription information may be updated private network subscription information for UE 1. For example, the private network subscription information updated by UE1 may not be identical to the private network subscription information before updating.

By way of example, suppose that the pre-update private network subscription information includes plmn#1cag#1, plmn#1cag#2, and plmn#2cag#2, and the updated private network subscription information includes plmn#1cag#1, plmn#1cag#3, and plmn#2cag#2.

In one implementation, the AMF may send DOWNLINK NAS TRANSPORT to the source base station, and the DOWNLINK NAS TRANSPORT may carry private network subscription information for UE 1.

S702, the source base station sends second indication information to the AMF. S703 is performed.

The second indication information is used for indicating that the UE1 is in an INACTIVE state, or the second indication information may also indicate that the AMF sends the private network subscription information to the target base station after receiving the private network information of the target base station, or the second indication information may also indicate that the AMF sends the private network subscription information to the target base station after receiving a path conversion request of the target base station, or the second indication information is used for indicating that the second access network device of the core network device cannot send the latest private network subscription information to the terminal device.

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

S703, the source base station sends a paging message (paging) to the target base station. This paging may be used to inform UE1 to resume RRC connection. S704 is performed.

Illustratively, the range of the paging may be the RNA of UE 1.

S704, the target base station sends paging to UE 1. This paging may be used to inform UE1 to resume RRC connection. S705 is performed.

Illustratively, the paging may be based on the RNA of UE 1.

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

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

The RRC resume request may be used for a target cell of the UE under the target base station to request to resume RRC connection.

S706, the target base station sends a resume context request to the source base station (RETRIEVE UE CONTEXT REQUEST). S707 is performed.

The resume context request may be used for the target base station to request the source base station to send the context of UE1, where the context is used for the target base station to resume RRC connection with UE 1.

It will be appreciated that, as another implementation, the UE may perform step 701, and after steps 703 to 706, perform step 702.

S707, the source base station sends a recovery context response to the target base station (RETRIEVE UE CONTEXT RESPONSE). S708 is performed.

The resume context response may carry the context of UE 1.

S708, RRC recovery (RRC RESUME) is performed between the target base station and UE 1. S709 is performed.

Illustratively, the target base station may resume the RRC connection with UE1 according to the context of UE1.

S709, the UE1 transmits an RRC restoration complete message to the target base station (RRC RESUME COMPLETE). S710 is performed.

In one implementation, the RRC recovery complete message may carry a public network identification, such as a PLMN ID, of the target network selected by UE 1. Suppose that the public network is identified as PLMN 1.

In addition, if the target network is a private network, the RRC connection recovery complete message may carry third indication information, where 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 an identifier of a public network on which the target network depends.

If the target network is a public network, the RRC connection request 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 appreciated that in the embodiment of the present application, the target network is a private network, so that the RRC recovery complete message may carry the third indication information.

S710, the target base station sends private network information to the AMF, wherein the private network information comprises the ID of at least one CAG supported by the second cell. Further, the private network information includes an ID of at least one CAG under the PLMN supported by the second cell selected by the terminal device. For example, the terminal device accesses through PLMN1 of the second cell, the ID of the at least one CAG may be understood as an ID of a CAG depending on PLMN1 or an ID of a CAG under PLMN 1. Wherein PLMN1 is a public network on which the target network selected by UE1 depends. S711 is performed.

The at least one CAG is dependent on PLMN1, which is also understood to mean that the PLMN ID of the at least one CAG is PLMN1. The public network on which the target network selected by the UE1 depends is PLMN1, and it may also be understood that the PLMN ID of the public network on which the target network selected by the UE1 depends is PLMN1.

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

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

By way of illustration, suppose that the private network supported by the target base station has: 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 the UE1 in the RRC recovery complete message is PLMN #1. The private network information reported to the AMF by the target base station may include plmn#1cag#1; plmn#1cag#2; PLMN#1CAG#3.

In another embodiment, the private network information may be carried in the RRC recovery complete message, that is, the 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, which PATH SWITCH REQUEST may carry private network information. The path switch request may be used to request the AMF to transfer the data reception point of the interface and/or data channel between the AMF and the target base station to the target base station. It will be understood that when the core network transmits data to the UE1, the data may be first transmitted to the target base station, and then forwarded to the UE1 by the target base station.

S711, the AMF performs authentication based on the private network information and the private network subscription information of the UE 1. If the verification passes, step S712 is performed; if the verification fails, step S716 is performed.

If at least one CAG ID in the private network information belongs to private network subscription information of the UE1, the verification is passed.

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

S712, the AMF sends a path switch response (PATH SWITCH acknowledge) to the target base station. S713 is performed.

The path switch response may be used to inform the target base station: the core network device has transferred the data reception point of the UE1 to the target base station.

S713, the target base station transmits a UE context release message to the source base station (UE CONTEXT RELEASE). S714 is performed.

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

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

In one implementation, the AMF may send DOWNLINK NAS TRANSPORT to the target base station, and the DOWNLINK NAS TRANSPORT may carry private network subscription information for UE 1.

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

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

In some embodiments, the target base station may pass DOWNLINK NAS TRANSPORT the AMF transmission through to UE1.

S716, the 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 with UE 1.

Further, the target base station may send the release message to UE 1. The UE1 may transition from the RRC CONNECTED state to the RRC IDLE state or RRC INATIVE state or 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 a cause of the path conversion failure is related to private network subscription information.

The first indication information may include, but is not limited to, at least one of: invalid private network identification; a private network identity that is not supported; is not in the private network signing range; unreasonable private network access.

In a possible implementation manner, after step S711, before step S716, the AMF may send the private network subscription information of UE1 to the target base station, the target base station may send the private network subscription information of UE1 to UE1, and the specific process may refer to steps S714 and S715, and the repetition is omitted.

In another possible implementation, the AMF may also carry private network subscription information of the UE1 in the release message, for example, may carry NAS-PDU in the release message, where the NAS-PDU carries the private network subscription information of the UE 1. The private network subscription information of UE1 is then sent to UE1 by the target base station, and the specific process may refer to step S715, and the repetition is not repeated.

Scene II: the UE1 accesses the first cell of the source base station before entering the INACTIVE state, and accesses the second cell of the source base station when the UE1 resumes RRC connection from the INACTIVE state, namely the source base station and the target base station are the same base station.

The private network subscription information updating flow of the second scene is similar to the private network subscription information updating flow of the first scene, and the difference is that the same base station executes the actions of the source base station and the target base station in the private network subscription information updating flow of the second scene, and the repeated parts are not repeated.

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

Scene III: the UE1 accesses the first cell of the source base station before entering the INACTIVE state, and when the UE1 resumes RRC connection from the INACTIVE state, the first cell of the source base station is accessed, namely the source cell and the target cell are the same cell.

In one implementation manner, the private network subscription information updating flow of the third scenario is similar to the private network subscription information updating flow of the second scenario, and the difference is that the information of the second cell is replaced by the information of the first cell in the private network subscription information updating flow of the second scenario, and the repetition is omitted. Alternatively, in scenario three, the information interaction between the source base station and the target base station may not be performed. The information interaction between the source cell and the target cell may not be performed.

In another implementation manner, for the third scenario, the private network subscription information updating method provided by the embodiment of the present application may not be adopted.

In one possible implementation, in the above-mentioned scenarios one to three, the private network subscription information update procedure may be triggered by the AMF, that is, the above-mentioned steps S0701 to S708 may be performed before the step S709, as shown in fig. 7.

In another possible implementation, in the above-mentioned scenarios one to three, the private network subscription information update procedure may be triggered by the UE1, that is, the above-mentioned steps S0705 to S708 may be performed before the step S709, as shown in fig. 8.

Embodiment two: the application provides another private network subscription information updating method.

In one aspect, the method includes: when the first access network device acquires the context of the UE from the second access network device, the second access network device may verify the first access network device based on private network subscription information sent by the core network device. If the verification fails, the second access network equipment sends a failure of restoring the UE context to the first access network equipment, and the first access network equipment triggers an RRC establishment process with the UE. If the verification is successful, the second access network device sends the UE context to the first access network device, and the first access network device triggers an RRC recovery process with the UE.

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 which is accessed before the terminal device enters the INACTIVE state, and the target cell is the cell which is accessed when the terminal device resumes the RRC connection from the INACTIVE state.

The first access network device, the second access network device, and the core network device are specifically referred to the related descriptions of the first access network device, the second access network device, and the core network device in the first embodiment, which are not described herein.

In order to better understand the method provided in the first aspect, the following description uses the core network device as an AMF as an example, and as shown in fig. 9, the private network subscription information update flow may be:

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

S902, the source cell initiates RAN paging for the UE.

In one embodiment, the paging message may be addressed to all base stations within the UE's RNA.

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

Illustratively, the target cell may page the UE with an inactive radio network temporary identity (inactive radio network temporary identifier, I-RNTI).

S904, after the UE residing in the target cell hears the paging message, an RRC recovery request message is sent 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 the source base station information according to the I-RNTI.

S906, the source cell verifies the target cell according to private network subscription information sent by the AMF. If the verification is not passed, S907 is executed.

If the verification is passed, the source cell may send the UE context to the target cell.

Optionally, if the target cell belongs to the subscription cell indicated in the private network subscription information, the verification is passed, otherwise, the verification is not passed.

S907, the source cell fails to restore the UE context to the target cell.

Optionally, the failure to recover the UE context may carry first indication information, where the first indication information is used to indicate that a reason for acquiring the UE context is related to private network subscription information. The first indication information may be specifically referred to the description related to the first indication information in the first embodiment, which is not repeated here.

S908, RRC establishment is carried out between the target cell and the UE.

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

Illustratively, 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, the AMF sends an initial context setup request to the target cell. The initial context establishment request message may carry private network subscription information of the UE.

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

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

S914, the UE transmits uplink information forwarding to the target cell, wherein the downlink information forwarding message can be used for indicating that updating of private network subscription information is completed.

S915, the target cell sends uplink NAS transmission to the AMF, wherein the uplink NAS transmission message can be used for indicating that the private network subscription information updating is completed.

It may be appreciated that the above-mentioned actions of the source cell may be performed by the access network device where the source cell is located, i.e. the second access network device, and the above-mentioned actions of the target cell may be performed by the access network device where the target cell is located, i.e. the first access network device.

Scheme II: the method comprises the following steps: when the first access network device acquires the context of the UE from the second access network device, the second access network device may send UE context information to the first access network device. The method comprises the steps that a first access network device triggers an RRC recovery process between the first access network device and the UE, and private network subscription information is sent to the UE after RRC connection between the first access network device and the UE is recovered.

In order to better understand the method provided in the third embodiment, the following description uses the core network device as an AMF as an example, and the private network subscription information update procedure may be:

the steps A1 to A5 can be specifically referred to S901 to S905, and will not be described herein.

And A6, the source cell sends a UE context to the target cell, wherein the UE context contains new private network subscription information.

And A7, the target cell sends an RRC recovery message to the UE.

A8, the UE sends RRC recovery completion information to the target cell.

And 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, wherein the configuration completion message is used for indicating that the private network subscription information updating is completed.

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

The second embodiment of the application introduces a solution, and when the target cell fails to acquire the context from the source cell, the target cell triggers the RRC establishment procedure. Or the target cell successfully acquires the context and triggers an RRC recovery process. The integrity of the communication protocol is supplemented, so that the problem that updating cannot be completed in private network subscription information can be solved.

Embodiment III: the application provides another private network subscription information updating method. Taking the core network device as an AMF as an example, as shown in fig. 10, the private network subscription information update flow may be:

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

In one possible implementation, the downlink NAS transport message may carry the new private network subscription information only in NAS-PDUs.

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

For another example, the downlink NAS transport message includes a NAS-PDU, excluding Mobility Restriction List, where the NAS-PDU carries new private network subscription information.

S1002 to S1005 can refer to S902 to S905, and are not described here again.

S1006, the source cell may send a resume UE context response to the target cell, where the resume UE context response carries new subscription information, e.g., NAS-PDU sent by the AMF.

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

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

Illustratively, the message may flag that the UE completes the RRC resume message on the target cell side.

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

S1010, the UE sends uplink information forwarding to the target cell, wherein the downlink information forwarding message can be used for indicating that updating of private network subscription information is completed.

And S1011, the target cell sends uplink NAS transmission to the AMF, wherein the uplink NAS transmission message can be used for indicating that the private network subscription information updating is completed.

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

It may be appreciated that the above-mentioned actions of the source cell may be performed by the access network device where the source cell is located, i.e. the second access network device, and the above-mentioned actions of the target cell may be performed by the access network device where the target cell is located, i.e. the first access network device. The first access network device, the second access network device, and the core network device are specifically referred to the related descriptions of the first access network device, the second access network device, and the core network device in the first embodiment, which are not described herein.

The third embodiment of the application introduces a solution: the AMF sends the new subscription information twice to inform the UE and the base station respectively, so that the source base station can be prevented from further judging. Thus, the behavior of the base station side is basically the same as the existing flow, and the protocol change is relatively small.

Embodiment four: the application provides another private network subscription information updating method. Taking the core network device as an AMF as an example, as shown in fig. 11, the private network subscription information update procedure may be:

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

Optionally, the source cell may report to the AMF after the UE is in INACTIVE state.

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

Optionally, the release message may carry first indication information, where the first indication information is used to indicate that a reason for acquiring the UE context is related to private network subscription information. The first indication information may be specifically referred to the description related to the first indication information in the first embodiment, which is not repeated here.

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

By executing step S1103, the AMF need not be within the TAI list range but need only be within the RNA range, and in general, the RNA is smaller than the TAI list range at the time of initiating the page. E.g. TAI list is all cells under base station 1-base station 10, while the RNA of the UE may be all cells under base station 1-base station 5. So if the source base station gives the AMF an RNA range, the AMF can page only in the RNA range, so that much signalling and resources can be saved.

Step S1103 is optional, and may or may not be performed.

S1104, the AMF initiates CN paging.

If step S1103 is performed, the AMF may initiate CN paging within the RNA range.

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

Illustratively, paging initiated by a core network device (e.g., an AMF) may be referred to as CN Paging. The CN paging can be initiated by AMF of 5G core network, sending paging message base station, base station transmitting to all UE connected with its related cell, UE monitoring paging message checking if it contains its ID, if yes, RRC establishing request can be initiated to connect with network; if not, this paging request may be ignored.

S1105, the target cell sends CN page.

S1106, after receiving the CN paging, the UE in INACTIVE state establishes RRC with the target cell.

S1107 to S1112 can refer to S910 to S915, and are not described here.

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

Fifth embodiment: the application provides another private network subscription information updating method. The method comprises the following steps:

When receiving new private network subscription information sent by AMF, a source cell performs differential treatment on cells in RNA:

For cell transmissions RAN PAGING still in the new private network subscription, the cells still in the new private network subscription are performed RAN PAGING in the cells. And if the UE receives the paging message in the cell still in the new private network subscription information, the UE initiates RRC recovery. Optionally RAN PAGING may carry an I-RNTI.

And for the cells which are not in the new private network subscription information range, sending Paging carrying indication information, wherein the indication information is used for indicating that the cells do not belong to the subscription cells indicated by the private network subscription information. And carrying out CN paging in the cell which is not in the new private network subscription information range. If the UE receives the CN paging in the cell which is not in the new private network subscription information range, the RRC establishment request is initiated in the cell. Alternatively, the indication information may be S-TMSI. In addition, the Paging may also carry an I-RNTI.

In order to better understand the solution provided in the fifth embodiment of the present application, taking the core network device as an AMF as an example, as shown in fig. 12, the private network subscription information update flow may be:

S1201, refer to S901, and will not be described here again.

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

The paging message may carry an I-RNTI and/or an S-TMSI. Optionally, the above-mentioned I-RNTI or S-TMSI may be indicated by the per cell, so that the target base station may determine the UE identifier that needs to be carried in the paging message sent by the corresponding cell. Or the paging message may also carry indication information, where the indication information is used to instruct the target base station to send a paging message containing the I-RNTI or the S-TMSI in the corresponding cell, or the indication information is used to instruct whether the cell under the target base station is still in the new private network subscription 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 the paging message carrying the I-RNTI in the cell based on the paging message.

(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 the paging message carrying the S-TMSI in the cell based on the paging message.

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

S1204, establishing RRC connection between the UE and the target cell.

S1205 to S1210 can refer to S910 to S915, and are not described here.

It may be appreciated that the above-mentioned actions of the source cell may be performed by the access network device where the source cell is located, i.e. the second access network device, and the above-mentioned actions of the target base station and/or the target cell may be performed by the access network device where the target cell is located, i.e. the first access network device. The first access network device, the second access network device, and the core network device are specifically referred to the related descriptions of the first access network device, the second access network device, and the core network device in the first embodiment, which are not described herein.

The fifth embodiment of the application provides a solution: the source cell performs differential treatment on the cell still in the new private network subscription information and the cell not in the new private network subscription information, so that the cell not in the new private network subscription information can trigger the UE to initiate the RRC establishment process, and the INACTIVE UE can complete the update of the private network subscription information.

Example six: the application provides another private network subscription information updating method. The method can be applied to the scene that the source cell and the target cell are the same base station, and comprises the following steps:

The source cell discovers that the target cell is not in the new private network subscription information and does not release the UE when receiving the new private network subscription information sent by the AMF, and sends RRC establishment to the UE, so that the behavior of the UE in the INACTIVE state is consistent with that of the UE in the IDLE state.

Or because the base station where the source cell and the target cell are located has the context of the UE and new private network subscription information, the UE can be triggered to perform RRC recovery, and update of the private network subscription information is completed.

In order to better understand the solution provided in the sixth embodiment of the present application, taking the core network device as an AMF as an example, as shown in fig. 13, the private network subscription information update flow may be:

S1301 to S1304 can refer to S901 to S904, and are not described here again.

S1305, the target cell determines that it is not in the new private network subscription information.

S1306 to S1313 can refer to S908 to S915, and are not described here.

It will be appreciated that the actions described above for the source cell and the target cell may be performed by the same access network device, i.e. 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 case that the source cell and the target cell are the same base station, and the target cell is not in the new private network subscription information: the base station ignores the new private network subscription information, so that the UE completes RRC recovery and completes the update of the new private network subscription information.

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

In a specific implementation manner, the apparatus may be specifically configured to implement a method performed by the core network device in the embodiments illustrated in fig. 6 to fig. 7, where the apparatus may be the core network device itself, or may be a chip or a chipset in the core network device, or a part of a chip or a chip for performing a function of a related method. The communication unit 1401 is configured to receive private network information from a first access network device, where the private network information includes an identifier of at least one private network supported by a cell used by the first access network device and a terminal device to restore a radio resource control RRC connection. The processing unit 1402 is configured to verify based on private network information and private network subscription information of the terminal device, where the private network subscription information is stored in the core network device.

Optionally, the processing unit 1402 may perform verification based on private network information and private network subscription information of the terminal device: if at least one private network identifier in the private network information belongs to private network subscription information, the verification is passed; or if the private network identification in the private network information does not belong to the private network subscription information, the verification is not passed.

The communication unit 1401 may be further configured to, after receiving the private network information from the first access network device, send a release message to the first access network device, where the release message is used to instruct the first access network device to release the RRC connection with the terminal device, where the private network identifier in the private network information does not belong to private network subscription information.

The release message carries first indication information, where the first indication information is used to indicate that a cause of the path conversion failure is related to private network subscription information.

Illustratively, the first indication information is an identification of an invalid private network.

In a specific implementation manner, the apparatus may be specifically configured to implement a method performed by the core network device in the embodiments illustrated in fig. 6 to fig. 7, where the apparatus may be the core network device itself, or may be a chip or a chipset in the core network device, or a part of a chip or a chip for performing a function of a related method. A processing unit 1402, configured to restore a radio resource control RRC connection with the terminal device; a communication unit 1401 is configured to send private network information to the core network device, where the private network information includes an identifier of at least one private network supported by a cell where the first access network device and the terminal device recover the radio resource control RRC connection.

The communication unit 1401 may be further configured 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 may be further configured to receive a release message from the core network device after sending the private network information to the core network device, where the release message is used to instruct the first access network device to release the RRC connection with the terminal device.

The release message carries first indication information, where the first indication information is used to indicate a reason for releasing the terminal device and/or a reason for a path conversion failure.

Illustratively, the first indication information includes at least one of: invalid private network identification; a private network identity that is not supported; is not in the private network signing range; unreasonable private network access.

In a specific implementation manner, the apparatus may be specifically configured to implement a method performed by the second access network device in the embodiment illustrated in fig. 8, where the apparatus may be the second access network device itself, or may be a chip or a chipset in the second access network device, or a part of a chip or a chip for performing a function of a related method. Wherein, the communication unit 1401 is used for receiving and transmitting signals; a processing unit 1402 for executing, through the communication unit 1401: receiving a third message from the first access network device, wherein the third message is used for requesting 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 subscription cell indicated by the private network subscription information, sending a fourth message to the first access network device, where the fourth message is used to indicate that the first access network device fails to acquire the context information, and the fourth message carries indication information, where the indication information is used to indicate that a reason for failure to acquire the context information is related to the private network subscription information.

In a specific implementation manner, the apparatus may be specifically configured to implement a method performed by the first access network device in the embodiment illustrated in fig. 8, where the apparatus may be the first access network device itself, or may be a chip or a chipset in the first access network device, or a part of a chip or a chip for performing a function of a related method. Wherein, the communication unit 1401 is used for receiving and transmitting signals; a processing unit 1402 for executing, through the communication unit 1401: sending a third message to the second access network device, wherein the third message is used for requesting context information of the terminal device from the second access network device; and receiving a fourth message from the second access network equipment, wherein the fourth message is used for indicating that the first access network equipment fails to acquire the context information, the fourth message carries indication information, and the indication information is used for indicating that the reason of the failure to acquire the context information is related to private network subscription information.

In a specific implementation manner, the apparatus may be specifically configured to implement a method performed by the core network device in the embodiment illustrated in fig. 11, where the apparatus may be the core network device itself, or a chip or a chipset in the core network device, or a part of a chip or a chip for performing a function of a related method. The processing unit 1402 is configured to determine that the second access network device does not belong to a subscription cell of the terminal device, where the second access network device is an access network device that provides services for the terminal device last before the terminal device enters an inactive state; a communication unit 1401 is configured to send a first message to the second access network device, where the first message is used to instruct the second access network device to release the context information of the terminal device.

The communication unit 101 may be further configured to: after the first message is sent to the second access network device, second information from the second access network device is received, where the second information is used to instruct the terminal device to notify the area RNA information based on the access network.

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

The division of the units in the embodiments of the present application is schematically shown, which is merely a logic function division, and may have another division manner when actually implemented, and in addition, each functional unit in each embodiment of the present application may be integrated in one processor, or may exist separately and physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units. It will be appreciated that the function or implementation of each unit in the embodiments of the present application may further refer to the relevant description of the method embodiments.

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

The processor 1501 may be a central processing unit (central processing unit, CPU), or a digital processing unit, or the like. The communication interface 1502 may be a transceiver, or may be an interface circuit such as a transceiver circuit, or may be a transceiver chip, or the like. The communication device further includes: a memory 1503 for storing a program executed by the processor 1502. The memory 1503 may be a nonvolatile memory such as a hard disk (HARD DISK DRIVE, HDD) or a Solid State Disk (SSD), or may be a volatile memory (RAM). Memory 1503 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such.

The processor 1501 is configured to execute the program code stored in the memory 1503, and specifically configured to execute the actions of the processing unit 1402, which are not described herein.

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 the embodiment of the present application, the memory 1503, the processor 1502 and the communication interface 1501 are connected through the bus 15014 in fig. 15, the bus is shown by a thick line in fig. 15, and the connection manner between other components is only schematically illustrated, but not limited thereto. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 15, but not only one bus or one type of bus.

The embodiment of the invention also provides a computer readable storage medium for storing computer software instructions required to be executed by the processor, and the computer readable storage medium contains a program required to be executed by the processor.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the available medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (Solid STATE DISK, SSD)), etc.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. The private network subscription information updating method is characterized by comprising the following steps:

The core network equipment receives second indication information from second access network equipment, wherein the second indication information is used for indicating that the second access network equipment cannot send private network subscription information to terminal equipment, the terminal equipment is in an inactive state, and the second access network equipment is access network equipment connected before the terminal equipment enters the inactive state;

the core network device receives private network information from first access network device, the first access network device initiates a Radio Resource Control (RRC) connection recovery request for the terminal device, the private network information comprises 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 a first public network;

the core network equipment verifies based on the private network information and the private network subscription information of the terminal equipment;

And if the verification is passed, the core network equipment sends private network subscription information of the terminal equipment to the first access network equipment.

2. The method of claim 1, wherein the core network device performs authentication based on the private network information and private network subscription information of the terminal device, comprising:

If at least one private network identifier in the private network information belongs to the private network subscription information, the verification is passed;

Or if the private network identification in the private network information does not belong to the private network subscription information, the verification is not passed.

3. The method of claim 1 or 2, further comprising, after the core network device receives the private network information from the first access network device:

and if the verification is not passed, the core network equipment sends a release message to the first access network equipment, wherein the release message is used for indicating the first access network equipment to release the RRC connection with the terminal equipment.

4. A method as claimed in claim 3, wherein the release message carries first indication information indicating that the reason for releasing the terminal device and/or the reason for failure of path switching is related to private network subscription information.

5. The method of claim 4, wherein the first indication information comprises at least one of: invalid private network identification; a private network identity that is not supported; is not in the private network signing range; unreasonable private network access.

6. A private network subscription information updating apparatus, characterized in that the apparatus comprises a processing unit and a transceiver unit, the transceiver unit being configured to perform the actions of transceiving signals in the method according to any one of claims 1 to 5; the processing unit is configured to perform actions other than transceiving signals in the method according to any of claims 1 to 5.

7. The private network subscription information updating device is characterized by comprising a processor and a communication interface, wherein the communication interface is used for receiving computer program codes or instructions and transmitting the computer program codes or instructions to the processor; the processor runs the computer program code or instructions to cause the apparatus to implement the method of any one of claims 1-5.

8. A computer readable storage medium, wherein a program is stored in the computer readable storage medium, which program, when read and executed by one or more processors, implements the method of any of claims 1-5.

9. A communication system, comprising: the apparatus as recited in claim 6.

10. A communication system, comprising: the apparatus as recited in claim 7.