CN113259924A

CN113259924A - Private network subscription information updating method and device

Info

Publication number: CN113259924A
Application number: CN202010091446.5A
Authority: CN
Inventors: 吴烨丹; 耿婷婷
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-02-13
Filing date: 2020-02-13
Publication date: 2021-08-13
Also published as: WO2021160096A1

Abstract

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

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 (PLMNs), are networks established and operated by governments or operators approved by them for the purpose of providing land mobile communications services to the public. In addition to public networks, operators or private persons may also build some private networks (NPN) to meet the needs of users. A private network may also be referred to as a non-public network and refers to a network that is open to a particular user, such as an internal network built in a company, school, or factory. Terminal devices not subscribed to the private network are not allowed to access the private network. After the terminal device signs a contract with the private network, the core network side and the terminal device side record the signing information of the terminal device, wherein the signing information refers to the user access information signed by the terminal device with an operator or other companies building the private network. If the terminal equipment signs a contract, the corresponding network can be accessed according to the network identification in the signing information, and the network resource is used. If the subscription information changes, the core network initiates a User Equipment (UE) configuration update procedure (UE configuration update) to notify the terminal equipment side of the updated subscription information.

For a terminal device in an inactive state (inactive), for updated subscription information, a source cell and/or a target cell may or may not be in a new subscribed cell list, and if the source cell and/or the target cell is not in the new subscribed cell list, how to update the subscription information in the terminal device does not have a good solution at present. Especially, when the target cell is not in the new contracted cell list, the behaviors 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 process of terminal equipment.

In a first aspect, an embodiment of the present application provides a method for updating private network subscription information, including: 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 (RRC) connection. The core network equipment verifies based on the private network information and the private network subscription information of the terminal equipment, and the private network subscription information is stored by the core network equipment. In the embodiment of the application, a solution is provided for the situation that the source cell and/or the target cell is not in the private network subscription information when the INACTIVE state UE updates the private network subscription information, so that the updating process of the private network subscription information of the terminal device in the INACTIVE state can be completed.

In one possible embodiment, the at least one private network is dependent on a first public network, the first public network being a public network on which the target network selected by the terminal device is dependent, the network identity of the first public network being a PLMN ID. In the above design, the first access network device may verify, by reporting the first public network identifier and the at least one private network identifier dependent on the first public network, the first access network device according to the first public network identifier and the private network identifier.

In one possible design, the identification of the private network includes 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 (NID).

In one possible design, the verifying, by the core network device, based on the private network information and the private network subscription information of the terminal device includes: if at least one private network identifier in the private network information belongs to the private network signing information, the verification is passed; or if the private network identifier 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 the private network subscription information, and the core network device may determine the access condition of the subscription cell in which the first access network device does not have the terminal device, so that it may be determined that the first access network device fails in verification.

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 the private network subscription information, the core network device sends a release message to the first access network device, wherein the release message is used for indicating the first access network device to release the RRC connection with the terminal device. By the design, when the first access network equipment fails to pass the verification, the resources can be released in time 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 the reason for releasing the terminal device and/or the reason for the path switching failure are related to the private network subscription information. Through the design, the first access network equipment can acquire the reason of the path switching failure, so that data statistics can be facilitated.

In one possible design, the first indication information includes at least one of: an invalid private network identity; an unsupported private network identifier; not within the private network subscription range; unreasonable private network access. Through the design, the first access network equipment can accurately acquire the reason of the path switching failure.

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

In one possible design, the at least one private network is dependent on a first public network, which is a public network on which the target network selected by the terminal device is dependent. 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 equipment receives private network subscription information of the terminal equipment. In the above design, the first access network device may obtain the private network subscription information of the terminal device after the verification passes.

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 equipment receives a release message from the core network equipment, wherein the release message is used for indicating the first access network equipment to release the RRC connection with the terminal equipment. By the design, when the first access network equipment fails to pass the verification, the resources can be released in time 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 method for updating private network subscription information, including: and the second access network equipment receives a third message from the first access network equipment, wherein the third message is used for requesting the context information of the terminal equipment from the second access network equipment. 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, and the fourth message carries indication information, and the indication information is used for indicating that the reason for acquiring the context information failure is related to the private network subscription information.

The embodiment of the application introduces a solution, when a first access network device fails to acquire a context from a second access network device, the first access network device triggers an RRC establishment process. Or the first access network equipment successfully acquires the context and triggers the RRC recovery process. The integrity of the communication protocol is supplemented, so that the problem that the private network subscription information cannot be updated is 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, and the third message is used for requesting the 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, and the fourth message carries indication information which is used for indicating that the reason for acquiring the context information failure is related to private network subscription information. The embodiment of the application introduces a solution, when a first access network device fails to acquire a context from a second access network device, the first access network device triggers an RRC establishment process. Or the first access network equipment successfully acquires the context and triggers the RRC recovery process. The integrity of the communication protocol is supplemented, so that the problem that the private network subscription information cannot be updated is 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 signed 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 equipment sends a first message to the second access network equipment, wherein the first message is used for indicating the second access network equipment to release the context information of the terminal equipment.

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

In one possible design, the first message carries first indication information, and the first indication information is used to indicate that a reason for releasing the context information is related to the private network subscription information. Through the design, the first access network equipment can acquire the reason of the path switching failure, so that 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 a second access network device, where the second information is used to indicate that the terminal device is Based on access network-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 (TAI) List (TAI List).

In one possible design, after the core network device receives the second information from the second access network device, the method further includes: the core network equipment sends the paging message in the range of the RNA 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 includes: and the core network equipment receives a second message from the access network equipment, wherein the second message is used for indicating that the terminal equipment is in an inactive state.

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

The embodiment of the application provides a solution: the second access network equipment 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 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-temporal mobile subscriber identity, S-TMSI).

In a seventh aspect, an embodiment of the present application provides a method for updating private network subscription information, 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 signed cell indicated by private network signed information. And the first access network equipment sends a second paging message, wherein 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 is identified as 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 the updated private network subscription information of 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 RRC connection; the access network equipment determines that the access network equipment does not belong to a signed cell indicated by private network signed information; the access network equipment recovers or reestablishes RRC connection with the terminal equipment; the access network equipment sends private network subscription information to the terminal equipment.

In the embodiment of the application, a solution is introduced for the situation 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: and the base station ignores the new private network subscription information, and enables the UE to complete RRC recovery and complete the update of the new private network subscription information.

In a ninth aspect, the present application provides a private network subscription information updating apparatus, which may be a core network device, or a chip or chip set in the core network device. The apparatus may include a processing unit and a transceiver unit. When the apparatus is a core network device, the processing unit may be a processor, and the transceiving 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 an instruction, and the processing unit executes the instruction stored in the storage unit, so that the core network device executes the corresponding function in the first aspect or the fifth aspect. When the apparatus is a chip or a chip set in a core network device or a chip set in a network device, the processing unit may be a processor, and the transceiving 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 a storage unit (e.g., a read-only memory, a random access memory, etc.) outside the chip or the chipset in the communication device, so as to enable the core network device to perform 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, which may be an access network device, or a chip or chip set in the access network device. The apparatus may include a processing unit and a transceiver unit. When the apparatus is an access network device, the processing unit may be a processor, and the transceiving 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 to cause the access network device to perform 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 chip set in an access network device, the processing unit may be a processor, and the transceiving unit may be an input/output interface, a pin, a circuit, or the like; the processing unit executes instructions stored in the storage unit, so as to cause the access network device to perform corresponding functions in the second aspect, the third aspect, the fourth aspect, the sixth aspect, the seventh aspect, or the eighth aspect, where the storage unit may be a storage unit (e.g., a register, a cache, or the like) in the chip or the chipset, or may be a storage unit (e.g., a read-only memory, a random access memory, or the like) in the communication device, which is located outside the chip or the chipset.

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

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

In a thirteenth aspect, the present application further provides a communication system, where the system includes the core network device in any embodiment of the first aspect, and the first access network device in any embodiment of the second aspect.

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

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

In a sixteenth aspect, the present application further provides a communication system, where the system includes the second access network device in any embodiment of the sixth aspect, and the first access network device in any embodiment of the seventh aspect.

In a seventeenth aspect, the present application further provides a communication system including the access network device in any of the above-mentioned embodiments of the eighth aspect.

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

In a nineteenth aspect, the present application further provides a computer-readable storage medium having stored therein 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 aspect described above.

In a twentieth aspect, the present application further 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.

In a twenty-first aspect, the present application further 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 aspect described above.

Drawings

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

fig. 2 is a schematic architecture 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 schematic flowchart 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 update flow provided in an embodiment of the present application;

fig. 8 is a schematic diagram of a private network subscription information update flow provided in an embodiment of the present application;

fig. 9 is a schematic diagram of a private network subscription information update flow provided in an embodiment of the present application;

fig. 10 is a schematic diagram of a private network subscription information update flow provided in an embodiment of the present application;

fig. 11 is a schematic diagram of a private network subscription information update flow provided in an embodiment of the present application;

fig. 12 is a schematic diagram of a private network subscription information update flow provided in an embodiment of the present application;

fig. 13 is a schematic diagram of a private network subscription information update flow provided in an embodiment of the present application;

fig. 14 is a schematic diagram of a private network subscription information updating apparatus 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 understanding of embodiments of the present application, terms related to embodiments of the present application are described below:

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 (PLMNs), are networks established and operated by governments or operators approved by them for the purpose of providing land mobile communications services to the public. The network is typically interconnected with a Public Switched Telephone Network (PSTN) to form a regional or national scale communications network.

Different PLMN networks may be distinguished by different PLMN Identities (IDs). The PLMN identity is composed of a Mobile Country Code (MCC) and a mobile network number (MNC). The MCC uniquely indicates the country of the mobile subscriber, for example, the MCC of china is 460. The MNC uniquely represents the network in the country, for example, the MNC of china mobile is 00 and the MNC of china unicom is 01.

2. Private network

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

(1) Non-independent private network

Network resources used by a non-independent private network (NSA-NPN, or a public network integrated non-public network, PNI-NPN) are part of a public network. It can also be said that dependent (return on) public networks are dependent on dependent private networks, also known as Closed Access Groups (CAG). The identification of the non-independent private network comprises two parts, namely a PLMN ID and a CAG ID, wherein the PLMN ID of the non-independent private network is consistent with the public network depended on. For a plurality of non-independent private networks depending on the same public network, the CAG ID of each non-independent private network is unique, that is, for a plurality of non-independent private networks depending on the same public network, the plurality of non-independent private networks 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 non-independent private network #2 may be expressed as: PLMN #1CAG # 2.

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

According to current communication protocols, since the CAG network uses public network resources, the terminal device can switch and cell reselect between the CAG network and the public network. The switching means that the terminal device in a connection state is disconnected from the current serving cell and connected with the target cell under the control of the base station. The cell reselection refers to a cell residence process in which, after the terminal device in an idle state/deactivated state resides in one cell, the terminal device may need to be changed to another cell residence with a higher priority or better signal along with the movement of the terminal device.

(2) Independent private network

A stand-alone non-public 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 divided into two parts, PLMN ID and NID respectively. For independent private networks that rely on public networks, their PLMN IDs are consistent with those of the dependent public networks, and for independent private networks that do not rely on public networks (which may be enterprise-deployed, for example), their PLMN IDs are MCCs of 999. For a plurality of independent private networks depending on the same public network, the NID of each dependent private network is unique, that is, for a plurality of independent private networks depending on the same public network, the independent private networks can be distinguished only by the NID.

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

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

the identity of the independent private network #3 may be expressed as: PLMN #3(MCC 999) NID # 1.

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

Note that 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 that is deployed by an enterprise or the like without the assistance of 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 dependent private network and other independent private networks, that is, the terminal device in a connected state cannot be switched from the independent private network cell to the public network cell, the dependent private network cell and other independent private network cells, and vice versa; the idle/deactivated terminal device cannot reselect from an independent private network cell to a public network cell and vice versa. It will 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 dependent private network, and other independent private networks.

3. RRC state of terminal device

In NR, the RRC state of the UE includes a CONNECTED state (RRC _ CONNECTED), a deactivated state or a third state (RRC _ INACTIVE), and an IDLE state (RRC _ IDLE), where when the UE is in the RRC _ CONNECTED state, the UE establishes a link with the base station and the core network, and when data arrives at the network, the data may be directly transmitted to the UE; when the UE is in the RRC _ INACTIVE state, it indicates that the UE has previously established a link with the base station and the core network, but the link from the UE to the base station is released, and although the link is released, the base station stores the context of the UE, and when there is data to be transmitted, the base station can recover the link in time; when the UE is in the RRC _ IDLE state, there is no link between the UE and the base station and the network, and when there is data to be transmitted, a link from the UE to the base station and the core network needs to be established. The three states transition as shown in fig. 1.

4. Subscription information

The subscription information refers to user admission information which the terminal equipment subscribes to an operator or other companies building the network. If the terminal equipment signs a contract, the corresponding network can be accessed according to the network identification in the signing information, and the network resource is used. The subscription information is stored in the core network side and the terminal device side, and if the subscription information changes, the core network initiates a UE configuration update procedure (UE configuration update) to notify the terminal device side.

It should be noted that as technology develops, the terminology of the embodiments of the present application may vary, but all are within the scope of the present application.

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

The architecture of the communication system may include a network open function network element, a policy control function network element, a data management network element, an application function network element, a core network access and mobility management function network element, a session management function network element, a terminal device, an access network device, a user plane function network element, and a data network. Fig. 2 shows a possible example of the architecture of the communication system, which specifically includes: a network open function (NEF) network element, a Policy Control Function (PCF) network element, a data management (UDM) network element, AN Application Function (AF) network element, AN AMF network element, a Session Management Function (SMF) network element, a UE, AN Access Network (AN) device, a User Plane Function (UPF) network element, and a data network (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 only an example, and the embodiment of the present application is not particularly limited thereto. 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 as an example herein, and are not intended to limit the network elements included in the communication system architecture 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, a vehicle-mounted device, and the like having a wireless connection function. Currently, the terminal device may be: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm top computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving (self-driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in city (smart city), a wireless terminal in smart home (smart home), and the like. The terminal device shown in fig. 2 is shown as a UE, which is only an example and is not limited to the terminal device.

The radio access network may be AN Access Network (AN) shown in fig. 2, and provides a radio access service 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 (RAN) node (or device). Currently, some examples of access network devices are: a gbb, a Transmission Reception Point (TRP), an evolved Node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved Node B, or home Node B, HNB), a Base Band Unit (BBU), or a wireless fidelity (Wifi) Access Point (AP), etc.

For example, 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 (CU) and a Distributed Unit (DU). Wherein a radio access network device may contain one CU and at least one DU, as shown in fig. 3. A CU is connected to at least one DU and may be used to manage or control the at least one DU. The structure can separate the protocol layer of the wireless access network device in the communication system, wherein part of the protocol layer function is realized in the CU, and the rest or all of the protocol layer function is realized in the DU, and the CU controls the DU in a centralized way. Taking radio access network equipment as an example of a gNB, a protocol layer of the gNB includes a Radio Resource Control (RRC) layer, a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a media access control sublayer (MAC) layer, and a physical layer. For example, the CU may be configured to implement the functions of the RRC layer, the SDAP layer, and the PDCP layer, and the DU may be configured to implement the functions of the RLC layer, the MAC layer, and the physical layer. The embodiment of the present application does not specifically limit the protocol stacks included in the CU and the DU. The CU and the DU may be connected using an F1 interface, the CU and other radio access network devices using an Xn interface, and the CU and the 5G Core network (5G Core, 5GC) using an NG interface, as shown in fig. 4.

For example, a CU in the embodiment of the present application may be further divided into a control plane (CU-CP) network element and at least one user plane (CU-user plane, CU-UP) network element. Wherein, the CU-CP can be used for control plane management, and the CU-UP can be used for user plane data transmission. The interface between the CU-CP and the CU-UP can be the E1 port. The interface between the CU-CP and the DU may be F1-C for transport of control plane signaling. The interface between CU-UP and DU may be F1-U 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 gbb as an example, the structure of the gbb 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 (IMS) network, a local area network (i.e., a local network, such as a Mobile Edge Computing (MEC) network), and so on. The data network comprises an application server, and the application server provides service for the terminal equipment by carrying out 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 each network element in the core network:

the core network access and mobility management function network element may be configured to manage access control and mobility of the terminal device, and in practical applications, the core network access and mobility management function network element includes a mobility management function in a Mobility Management Entity (MME) in a network frame in Long Term Evolution (LTE), and is added with an access management function, and may be specifically responsible for registration, mobility management, a tracking area update procedure, reachability detection, selection of a session management function network element, mobility state transition management, and the like of the terminal device. For example, in 5G, the core network access and mobility management function network element may be an AMF (access and mobility management function) network element, for example, as shown in fig. 2, and in future communication, for example, in 6G, the core network access and mobility management function network element may still be an AMF network element or have another name, which is not limited in this application. When the core network access and mobility management function network element is an AMF network element, the AMF may provide a Namf service.

The session management functional network element may be configured to be responsible for session management (including establishment, modification, and release of a session) of the terminal device, selection and reselection of a user plane functional network element, Internet Protocol (IP) address allocation, quality of service (QoS) control, and the like of the terminal device. For example, in 5G, the session management function network element may be an SMF (session management function) network element, for example, as shown in fig. 2, in future communication, for example, in 6G, the session management function network element may still be an SMF network element, or may have another name, which is not limited in this application. When the session management function network element is an SMF network element, the SMF may provide an Nsmf service.

The policy control function network element can be used for taking charge of policy control decision, providing functions of service data flow and application detection, gating, QoS (quality of service) and flow-based charging control and the like. For example, in 5G, the policy control function network element may be a PCF (policy control function) network element, for example, as shown in fig. 2, and in future communication, for example, in 6G, the policy control function network element may still be a PCF network element, or have another name, which is not limited in this application. When the policy control function network element is a PCF network element, the PCF network element may provide an Npcf service.

The application function network element mainly functions to interact with a 3rd generation partnership project (3 GPP) core network to provide services, so as to affect 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 communication, for example, in 6G, the application function network element may still be an AF network element, or have another name, which is not limited in this application. When the application function network element is an AF network element, the AF network element may provide a Naf service.

The data management network element may be configured to manage subscription data of the terminal device, registration information related to the terminal device, and the like. For example, in 5G, the data management network element may be a unified data management network element (UDM), for example, as shown in fig. 2, and in future communication, for example, in 6G, the data management network element may still be a UDM network element or have another name, which is not limited in this application. When the data management network element is a UDM network element, the UDM network element may provide a numm service.

The network open function network element may be configured to enable the 3GPP to securely provide network service capabilities to AFs (e.g., Service Capability Servers (SCS), Application Servers (AS), etc.) of third parties. For example, in 5G, the network element may be an NEF, for example, as shown in fig. 2, and in future communication, for example, in 6G, the network element may still be an NEF network element, or have another name, which is not limited in this application. When the network open function network element is a NEF, the NEF may provide an Nnef service to other network function network elements.

The above network elements in the core network may also be referred to as functional entities, and may be network elements implemented on dedicated hardware, or may be software instances running on dedicated hardware, or may be 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 include only the network elements shown in the figure, and may also include other devices not shown in the figure, which are not specifically listed here.

It should be noted that the embodiment of the present application does not limit the distribution form of each network element in the core network, and the distribution form shown in fig. 2 is only an example, and the present application is not limited.

For convenience of description, in the following description, the network element shown in fig. 2 is taken as an example, and the XX network element is directly abbreviated as XX, for example, the AMF network element is abbreviated as AMF. It should be understood that the names of all network elements in the present application are only used as examples, and may also be referred to as other names in future communications, or network elements referred to in the present application may also be replaced by other entities or devices with the same function in future communications, and the present application does not limit the present application. The unified description is made here, and the description is not repeated.

The communication system shown in fig. 2 is not intended to limit the communication system to which the embodiments of the present invention can be applied. 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 the subscription information in the protocol is:

the terminal device may pre-configure or reconfigure the following CAG information, which belongs to a part of the mobility restriction:

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

Only the CAG indication is allowed to be accessed, which with this indication means that the terminal device cannot access the public network.

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

For terminal equipment in Inactive state, as a possible implementation manner, when triggering a configuration update process, the AMF sends a DOWNLINK non-access stratum (NAS) TRANSPORT (DOWNLINK NAS TRANSPORT) to a source base station, where the DOWNLINK NAS TRANSPORT carries a NAS-Protocol Data Unit (PDU) and a Mobility Restriction List (Mobility Restriction List), where the NAS-PDU is sent to the terminal equipment by the AMF, and the base station receives the NAS-PDU and transparently transmits the NAS-PDU to the terminal equipment. And the Mobility retrieval List is sent to the base station by the AMF, and both the NAS-PDU and the Mobility retrieval List carry updated private network subscription information. The source base station is the last serving base station before the terminal equipment enters the inactive state from the connected state. The source base station sends paging messages to base stations in the RNA of the terminal equipment, the base stations are transmitted to all UE connected with the source base station, the UE monitoring the paging messages can check whether the base stations contain the I-RNTI of the source base station, and if yes, an RRC recovery request is sent to the base station to which the current serving cell belongs. If the base station to which the current serving cell belongs is the source base station, the terminal device may receive the 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 the updated private network subscription information at the target base station. The target base station may obtain the 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 this embodiment of the present application.

Taking the example that the target base station acquires the updated private network subscription information of the UE from the core network equipment AMF, for the terminal equipment in INACTIVE, if the source base station receives the DOWNLINK NAS TRANSPORT sent by the AMF, the source base station initiates paging of the corresponding INACTIVE UE. If the target base station that the INACTIVE UE initiates access is not the source base station (i.e., the last serving gbb, the base station that disconnected the air interface and entered the INACTIVE), 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 the DOWNLINK NAS TRANSPORT containing the updated private network subscription information to the target base station after the target base station completes path switching (path switch), and the target base station forwards the NAS-PDU to the UE.

For the 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, the AMF updates the subscription information in the terminal device, and there is no good solution at present.

Based on this, the application provides a private network subscription information updating method and device, which are used for perfecting the private network subscription information updating process of the terminal device in the INACTIVE state. The method and the device are based on the same inventive concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

In the present invention, the plurality of the embodiments means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Also, it should be understood that the terms first, second, etc. used in the description of the embodiments of the present application are used for distinguishing between the descriptions and not for indicating or implying any relative importance or order.

The following describes embodiments of the present application in detail with reference to specific scenarios.

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

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 recovers 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, the first access network device sends the private network information 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 between the first access network device and the terminal device. Accordingly, the core network device may receive the private network information sent by the first access network device.

The core network device may determine, based on the private network information, an identification of at least one private network supported by the first access network device.

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

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

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 designation, and may be named as others in future communication development, and the private network in the embodiment of the present application may be understood as the private network in the embodiment of the present application as long as the function of the private network in the embodiment of the present application can be implemented.

The public network may also be referred to as a public land mobile network, and may also be referred to as a PLMN. It should be understood that "public network" is only an exemplary designation, and may be named as others in future communication development, and the public network in the embodiment of the present application may be understood as the public network in the embodiment of the present application as long as the function of the public network in the embodiment of the present application can be realized.

If the private network is a dependent private network, the identifier of the private network may include two parts, which are a PLMN ID and a CAG ID, respectively, where the PLMN ID is consistent with the dependent public network ID. For multiple non-independent private networks that depend on the same public network, the CAG ID of each non-independent private network is unique. For example, the identity of the dependent private network #1 may be expressed as: PLMN #1CAG # 1; the identity of the non-independent private network #2 may be expressed as: PLMN #1CAG # 2. Wherein the dependent private network #1 and the dependent private network #2 are both private networks established in dependence on the public network identified by the PLMN # 1.

If the private network is an independent private network, the identifier of the private network may include two parts, i.e., PLMN ID and NID, respectively, for example, the identifier of the private network may be PLMN # 1. For independent private networks that rely on public networks, the PLMN ID is consistent with the public network relied upon, and for independent private networks that do not rely on public networks (which may be deployed by the enterprise itself, for example), the MCC of the PLMN ID is a fixed value, such as 999. For example, the identity of the independent private network #1 may be expressed as: PLMN #1NID # 1; the identity of the independent private network #2 may be expressed as: PLMN #1NID # 2; the identity of the independent private network #3 may be expressed as: PLMN #3(MCC 999) NID # 1. Wherein the independent private network #1 and the independent private network #2 are both private networks established in dependence on a public network identified by PLMN # 1.

In an exemplary illustration, the first access network device may be an access network device accessed when the terminal device resumes RRC connection from INACTIVE state.

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

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

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

In the embodiment of the application, a solution is provided for the situation that the source cell and/or the target cell is not in the private network subscription information when the INACTIVE state UE updates the private network subscription information, so that the updating process of the private network subscription information of the terminal device in the INACTIVE state can be completed.

In a 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 passes.

For example, it is assumed that the private network subscription information includes PLMN #1CAG #1, PLMN #1CAG #2, and PLMN #2CAG #2, the private network information sent by the first access network device includes PLMN #1CAG #1, PLMN #1CAG #3, and PLMN #1CAG #4, and PLMN #1CAG #1 in the private network information is included in the private network subscription information of the terminal device, and therefore, it can be determined that the 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.

For example, it is assumed that the private network subscription information includes PLMN #1CAG #1, PLMN #1CAG #2, and PLMN #2CAG #2, the private network information sent by the first access network device includes PLMN #1CAG #5, PLMN #1CAG #3, and PLMN #1CAG #4, and none of 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, and therefore it may be determined that the authentication does not pass.

Further, if the verification is passed, the core network device may send the private network subscription information of the terminal device to the first access network device. It is to be understood 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 fails, 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 further 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, and for example, the reason for releasing the terminal device may be related to private network subscription information.

Or, the first indication information is used for indicating that the reason of the path switching failure is related to the 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 path switching failure are related to the private network subscription information.

In one possible embodiment, the first indication information may include, but is not limited to, at least one of: an invalid private network identity; an unsupported private network identifier; not within the private network subscription range; unreasonable private network access.

In another possible implementation, if the verification fails, 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 a 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, to the first access network device, an NAS-PDU carrying private network subscription information, and the first access network device passes through to the terminal device. By the mode, the terminal equipment can update the 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 a NAS-PDU in the release message, where the NAS-PDU carries the private network subscription information, so that the first access network device may pass the NAS-PDU through to the terminal device when receiving the release message.

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

After the core network device triggers the private network subscription information updating process, second indication information from the second access network device may be received, where the second indication information is used to indicate that the core network device sends 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 indicate that the second access network device of the core network device cannot send the latest private network subscription information to the terminal device.

In another possible implementation, the terminal device may trigger the RRC connection restoration procedure before the core network device receives the path switching request from the first access network device. For example, the terminal device sends an RRC recovery 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 accessed by the terminal device before entering the INACTIVE state (hereinafter referred to as a source cell for convenience of description) is the same cell as a cell accessed by the terminal device when the terminal device resumes the RRC connection from the INACTIVE state (hereinafter referred to as a target cell for convenience of description).

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 following describes a private network subscription information updating process in detail with reference to a specific scenario. For convenience of description, the core network device is an AMF, the private network is a CAG, and the public network is a PLMN.

Scene one: the UE1 accesses a first cell of a source base station before entering an INACTIVE state, and the UE1 accesses a second cell of a target base station when resuming an 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 updating process 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 by the UE 1. For example, the indicated subscription cell may not be identical for the UE1 after the update of the private network subscription information as compared to the private network subscription information before the update.

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

In one implementation, the AMF may send a download NAS TRANSPORT to the source base station, where the download NAS TRANSPORT may carry the private network subscription information of the UE 1.

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

The second indication information is used to indicate that the UE1 is in 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 the path switching request of the target base station, or the second indication information is used to indicate 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. The paging may be used to inform the UE1 to resume the RRC connection. S704 is performed.

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

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

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

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

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

And the RRC recovery request can be used for requesting the UE to recover the RRC connection in the target cell under the target base station.

S706, the target base station sends a CONTEXT restore REQUEST (RETRIEVE UE CONTEXT REQUEST) to the source base station. S707 is executed.

The resume context request may be for the target base station to request the source base station to send a context for the UE1 for the target base station to resume the RRC connection with the UE 1.

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

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

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

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

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

S709, the UE1 sends an RRC recovery COMPLETE message (RRC RESUME COMPLETE) to the target base station. 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 the UE 1. Assume that the public network identity is PLMN 1.

In addition, if the target network is a private network, the RRC 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 that the target network depends on.

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

It can be understood that, in the embodiment of the present application, the target network is a private network, and therefore, the RRC recovery 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 a PLMN supported by the second cell selected by the terminal device. For example, if the terminal device accesses through the PLMN1 of the second cell, the ID of the at least one CAG may be understood as the ID of the CAG depending on PLMN1 or the ID of the CAG under PLMN 1. Where PLMN1 is the public network on which the target network selected by UE1 depends. S711 is performed.

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

For example, the 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 of the PLMN1 in all the CAGs supported by the second cell to the AMF.

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

For an example, assume that the target base station supports a private network with: 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 by the target base station to the AMF may include PLMN #1CAG # 1; PLMN #1CAG # 2; PLMN #1CAG # 3.

In another embodiment, the RRC recovery complete message may carry the private network information, 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 a data sink of an interface and/or data channel between the AMF and the target base station to the target base station. It is understood that when the core network sends data to the UE1, the data may be sent to the target base station first, and the data is 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 is passed, go to step S712; if the verification fails, go to step S716.

And if at least one CAG ID in the private network information belongs to the private network subscription information of the UE1, the authentication is passed.

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

S712, the AMF sends a path switch acknowledgement (path switch acknowledgement) to the target base station. S713 is performed.

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

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

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

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

In one implementation, the AMF may send a download NAS TRANSPORT to the target base station, where the download NAS TRANSPORT may carry the private network subscription information of the UE 1.

S715, the target base station sends the 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 through the DOWNLINK NAS TRANSPORT sent by the AMF to the UE 1.

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

A release message may be used to instruct the target base station to release the RRC connection with the UE 1.

Further, the target base station may send the release message to the 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, depending on the type of release message.

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

The first indication information may include, but is not limited to, at least one of: an invalid private network identity; an unsupported private network identifier; not within the private network subscription range; unreasonable private network access.

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

In another possible implementation, the AMF may also carry the private network subscription information of the UE1 in the release message, for example, may carry a NAS-PDU carrying the private network subscription information of the UE1 in the release message. The target base station sends the private network subscription information of the UE1 to the UE1, and the specific process may refer to step S715, and repeated details are not described again.

Scene two: the UE1 accesses the first cell of the source base station before entering the INACTIVE state, and the UE1 accesses the second cell of the source base station when the RRC connection is restored from the INACTIVE state, that is, the source base station and the target base station are the same base station.

The private network subscription information updating process of the scene two is similar to the private network subscription information updating process of the scene one, 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 process of the scene one, and repeated parts are not repeated.

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

Scene three: the UE1 accesses the first cell of the source base station before entering the INACTIVE state, and the UE1 accesses the first cell of the source base station when resuming the RRC connection from the INACTIVE state, that is, the source cell and the target cell are the same cell.

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

In another implementation manner, for scenario three, the private network subscription information updating method provided in the embodiment of the present application may not be used.

In one possible implementation manner, in the scenarios one to three, the private network subscription information updating process may be triggered by the AMF, that is, the foregoing steps S0701 to S708 may be performed before step S709, as shown in fig. 7.

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

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

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

The first access network device is an access network device where a target cell is located, the second access network device is an access network device where a source cell is located, the source cell is a first cell accessed before the terminal device enters an INACTIVE state, and the target cell is a cell accessed when the terminal device recovers RRC connection from the INACTIVE state.

The first access network device, the second access network device, and the core network device may specifically refer to the description of the first access network device, the second access network device, and the core network device in the first embodiment, which is not described herein again.

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

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

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

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

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

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

S904, after the UE residing in the target cell hears the paging message, the UE sends an RRC recovery request message in the target cell.

S905, the target cell sends a request message for acquiring the UE context 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 the private network subscription information sent by the AMF. If the verification fails, S907 is executed.

If the verification is passed, the source cell may send the context of the UE 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 sends UE context recovery failure 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 obtaining the UE context is related to private network subscription information. The first indication information may specifically refer to the related description of the first indication information in the first embodiment, and is not described herein again.

S908, RRC establishment is performed 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 at 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 setup 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 sends downlink information forwarding to the UE, wherein the downlink information forwarding information carries private network subscription information of the UE.

S914, the UE sends uplink information forwarding to the target cell, where the downlink information forwarding message may be used to indicate that the private network subscription information update is completed.

S915, the target cell sends an uplink NAS transmission to the AMF, where the uplink NAS transmission message may be used to indicate that updating of the private network subscription information is completed.

It can be understood that the action of the source cell may be performed by an access network device in which the source cell is located, that is, the second access network device, and the action of the target cell may be performed by an access network device in which the target cell is located, that is, the first access network device.

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

In order to better understand the method provided by the third embodiment, the following description takes core network equipment as AMF as an example, and the private network subscription information updating process may be as follows:

the steps a1 to a5 may specifically refer to S901 to S905, which are not described herein again.

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

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

A8, the UE sends RRC resume complete message to the target cell.

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

A10, the UE sends a configuration completion message to the target cell, the configuration completion message is used for indicating that the update of the private network subscription information is completed.

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

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

Example three: the application provides another private network subscription information updating method. Taking the core network device as the AMF, as shown in fig. 10, the private network subscription information updating process may be:

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

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

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

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

S1002 to S1005 refer to S902 to S905, which are not described herein again.

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

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

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

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

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

S1010, the UE sends uplink information forwarding to the target cell, where the downlink information forwarding message may be used to indicate that updating of the private network subscription information is completed.

S1011, the target cell sends an uplink NAS transmission to the AMF, where the uplink NAS transmission message may be used to indicate that updating of the private network subscription information is completed.

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

It can be understood that the action of the source cell may be performed by an access network device in which the source cell is located, that is, the second access network device, and the action of the target cell may be performed by an access network device in which the target cell is located, that is, the first access network device. The first access network device, the second access network device, and the core network device may specifically refer to the description of the first access network device, the second access network device, and the core network device in the first embodiment, which is not described herein again.

The third embodiment of the present application introduces a solution: and the AMF sends new subscription information twice and respectively informs the UE and the base station, thereby avoiding the further judgment of the source base station. Therefore, the behavior of the base station side is basically the same as that of the existing flow, and the change of the protocol is small.

Example four: the application provides another private network subscription information updating method. Taking the core network device as the AMF, as shown in fig. 11, the private network subscription information updating process 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 specifically refer to the related description of the first indication information in the first embodiment, and is not described herein again.

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

By performing step S1103, the AMF does not need to be within the TAI list but only needs to be within the RNA range when initiating paging, and in general, the RNA is smaller than the TAI list. For example, TAI list is all cells under BS 1-BS 10, and the UE's RNA may be all cells under BS 1-BS 5. So if the source base station gives an RNA range to the AMF, the AMF can page only in the RNA range, thereby saving much signaling and resources.

Step S1103 is optional and may or may not be executed.

S1104, the AMF initiates CN paging.

If step S1103 is executed, the AMF may initiate CN paging in the RNA range.

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

Illustratively, the Paging initiated by the core network device (e.g., AMF) may be referred to as CN Paging. CN paging can be initiated by AMF of a 5G core network, a paging message base station is sent, the base station is transmitted to all UE connected with a relevant cell of the base station, the UE monitoring the paging message can check whether the UE contains an ID of the UE, if so, an RRC establishment request can be initiated to connect with a network; if not, the paging request may be ignored.

S1105, the target cell sends CN paging.

S1106, after receiving the CN page, the UE in INACTIVE state performs RRC establishment with the target cell.

S1107 to S1112 can refer to S910 to S915, which are not described herein again.

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

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

when the source cell receives new private network subscription information sent by the AMF, the cells in the RNA are treated differently:

and sending the RAN paging to the cell still in the new private network subscription information, and carrying out the RAN paging in the cell by the cell still in the new private network subscription information. The UE initiates RRC recovery if it receives a paging message in a cell that is still within the new private network subscription information. Optionally, the RAN paging may carry the I-RNTI.

And for the cell which is not in the range of the new private network subscription information, sending the Paging carrying the indication information, wherein the indication information is used for indicating that the cell does not belong to the subscription cell indicated by the private network subscription information. And the cell which is not in the range of the new private network subscription information carries out CN paging in the cell. And if the UE receives CN paging in a cell which is not in the range of the new private network subscription information, initiating an RRC establishment request in the cell. Optionally, the indication information may be S-TMSI. In addition, the Paging may also carry I-RNTI.

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

s1201, refer to S901, which is not described herein 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 I-RNTI or the S-TMSI may be indicated by per cell, so that the target base station may determine the UE identity 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 indicate that the target base station sends a paging message containing an I-RNTI or an S-TMSI in a corresponding cell, or the indication information is used to indicate whether a 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.

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

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

S1205 to S1210 refer to S910 to S915, which are not described herein again.

It can be understood that the action of the source cell may be performed by an access network device in which the source cell is located, that is, a second access network device, and the action of the target base station and/or the target cell may be performed by an access network device in which the target cell is located, that is, a first access network device. The first access network device, the second access network device, and the core network device may specifically refer to the description of the first access network device, the second access network device, and the core network device in the first embodiment, which is not described herein again.

The fifth embodiment of the present 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 an RRC establishment process, and the INACTIVE UE can complete private network subscription information updating.

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

after receiving the new private network subscription information sent by the AMF, the source cell finds that the target cell is not in the new private network subscription information, does not release the UE, but 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 the new private network subscription information, the UE may be triggered to perform RRC recovery, and update of the private network subscription information is completed.

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

s1301 to S1304 may refer to S901 to S904, which are not described herein again.

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

S1306 to S1313, refer to S908 to S915, which are not described herein.

It is to be understood that the actions of the source cell and the target cell may be performed by the same access network device, i.e., the access network device in which the source cell and the target cell are located.

In the fifth embodiment of the present application, a solution is introduced for a situation that a source cell and a target cell are the same base station and the target cell is not in new private network subscription information: and the base station ignores the new private network subscription information, and enables the UE to complete RRC recovery and complete 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 structure of the apparatus may be as shown in fig. 14, and includes a communication unit 1401 and a processing unit 402.

In a specific implementation manner, the apparatus may be specifically used to implement the method executed by the core network device in the embodiments described in fig. 6 to fig. 7, and the apparatus may be the core network device itself, or may also be a chip or a chip set in the core network device, or a part of the chip or the chip used for executing the function of the related method. The communication unit 1401 is configured to receive 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 the radio resource control RRC connection. The processing unit 1402 is configured to perform verification based on the private network information and the private network subscription information of the terminal device, where the private network subscription information is stored in the core network device.

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

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

Illustratively, the release message carries first indication information, where the first indication information is used to indicate that the reason for the path switch failure is related to the private network subscription information.

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

In a specific implementation manner, the apparatus may be specifically used to implement the method executed by the core network device in the embodiments described in fig. 6 to fig. 7, and the apparatus may be the core network device itself, or may also be a chip or a chip set in the core network device, or a part of the chip or the chip used for executing the function of the related method. The processing unit 1402 is configured to recover a radio resource control, RRC, connection with the terminal device; a communication unit 1401, 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 radio resource control RRC connection.

The communication unit 1401 may be further configured to receive the private network subscription information of the terminal device after transmitting the private network information to the core network device.

The communication unit 1401 may further be 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.

Illustratively, 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 switching failure.

Illustratively, the first indication information includes at least one of: an invalid private network identity; an unsupported private network identifier; not within the private network subscription range; unreasonable private network access.

In a specific implementation manner, the apparatus may be specifically configured to implement the method performed by the second access network device in the embodiment described in fig. 8, and the apparatus may be the second access network device itself, or may be a chip or a chip set in the second access network device, or a part of a chip or a chip in the chip for performing a function of the related method. Wherein, the communication unit 1401, is used for receiving and transmitting the signal; a processing unit 1402 for executing, by the communication unit 1401: receiving a third message from the first access network device, wherein the third message is used for requesting the context information of the terminal device from the second access network device; and if at least one of the second access network equipment and the first access network equipment does not belong to the signed cell indicated by the private network signing information, sending a fourth message to the first access network equipment, wherein the fourth message is used for indicating that the first access network equipment fails to acquire the context information, and the fourth message carries indication information which is used for indicating that the reason for acquiring the context information failure is related to the private network signing information.

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

In a specific implementation manner, the apparatus may be specifically used to implement the method executed by the core network device in the embodiment illustrated in fig. 11, and the apparatus may be the core network device itself, or may also be a chip or a chip set in the core network device, or a part of the chip or the chip used for executing a function of the 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 finally provides a service for the terminal device before the terminal device enters an inactive state; a communication unit 1401, 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 further be configured to: after sending the first message to the second access network device, receiving second information from the second access network device, the second information being used for indicating the terminal device based on the notification region RNA information of 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, the paging message is transmitted within the RNA range indicated by the second information.

The division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation, and in addition, each functional unit in each embodiment of the present application may be integrated in one processor, may also exist alone physically, or may also be integrated in one unit by two or more units. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It is understood that the functions or implementations of the respective units in the embodiments of the present application may further refer to the related description of the method embodiments.

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

The processor 1501 may be a Central Processing Unit (CPU), a digital processing unit, or the like. The communication interface 1502 may be a transceiver, an interface circuit such as a transceiver circuit, or the like, a transceiver chip, or the like. The communication device further includes: a memory 1503 for storing programs executed by the processor 1502. The memory 1503 may be a nonvolatile memory such as a Hard Disk Drive (HDD) or a solid-state drive (SSD), and may also be a volatile memory (RAM), such as a random-access memory (RAM). The 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 thereto.

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

The embodiment of the present application does not limit the specific connection medium among the communication interface 1501, the processor 1502, and the memory 1503. In the embodiment of the present application, the memory 1503, the processor 1502, and the communication interface 1501 are connected by the bus 15014 in fig. 15, the bus is indicated by a thick line in fig. 15, and the connection manner between other components is merely illustrative and not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 15, but this is not intended to represent only one bus or type of bus.

The embodiment of the present invention further provides a computer-readable storage medium, which is used for storing computer software instructions required to be executed for executing the processor, and which contains a program required to be executed for executing the processor.

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

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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

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

the method comprises the steps that core network equipment receives private network information from first access network equipment, wherein the private network information comprises an identifier of at least one private network supported by a cell which is used for recovering Radio Resource Control (RRC) connection between the first access network equipment and terminal equipment;

and the core network equipment carries out verification based on the private network information and the private network subscription information of the terminal equipment.

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

if at least one private network identifier in the private network information belongs to the private network signing information, the authentication is passed;

or if the private network identifier 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, wherein after the core network device receives the private network information from the first access network device, further comprising:

and if the private network identifier in the private network information does not belong to the private network subscription information, the core network device sends a release message to the first access network device, wherein the release message is used for indicating the first access network device to release the RRC connection with the terminal device.

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

5. The method of claim 3, wherein the first indication information comprises at least one of: an invalid private network identity; an unsupported private network identifier; not within the private network subscription range; unreasonable private network access.

6. A private network subscription information updating method is characterized by comprising the following steps:

the first access network equipment recovers the Radio Resource Control (RRC) connection with the terminal equipment;

the first access network equipment sends private network information to core network equipment, wherein the private network information comprises an identifier of at least one private network supported by a cell in which the first access network equipment and terminal equipment recover Radio Resource Control (RRC) connection.

7. The method of claim 6, wherein after the first access network device sends private network information to a core network device, the method further comprises:

and the first access network equipment receives the private network subscription information of the terminal equipment.

8. The method of claim 6, wherein after the first access network device sends private network information to a core network device, the method further comprises:

and the first access network equipment receives a release message from the core network equipment, wherein the release message is used for indicating the first access network equipment to release the RRC connection with the terminal equipment.

9. The method of claim 8, wherein the release message carries indication information, and the indication information is used for indicating that a reason for releasing the terminal device and/or a reason for a path switching failure are related to private network subscription information.

10. A private network subscription information updating method is characterized by comprising the following steps:

the second access network equipment receives a third message from the first access network equipment, wherein the third message is used for requesting the context information of the terminal equipment from the second access network equipment;

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, and the fourth message carries indication information which is used for indicating that the reason for acquiring the context information fails is related to the private network subscription information.

11. A private network subscription information updating method is characterized by comprising the following steps:

the first access network equipment sends a third message to second access network equipment, wherein the third message is used for requesting the context information of the terminal equipment from the second access network equipment;

the first access network device receives a fourth message from the second 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 acquiring the context information failure is related to private network subscription information;

the first access network equipment acquires the updated private network subscription information of the terminal equipment from core network equipment;

and the first access network equipment sends the private network subscription information to the terminal equipment.

12. The method of claim 11, wherein the first indication information comprises at least one of: an invalid private network identity; an unsupported private network identifier; not within the private network subscription range; unreasonable private network access.

13. A private network subscription information updating method is characterized by comprising the following steps:

the core network equipment determines that second access network equipment does not belong to a signed 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;

and the core network equipment sends a first message to the second access network equipment, wherein the first message is used for indicating the second access network equipment to release the context information of the terminal equipment.

14. The method of claim 13, wherein the first message carries first indication information indicating that a reason for releasing the context information is related to private network subscription information.

15. The method of claim 13 or 14, wherein after the core network device sends the first message to the second access network device, the method further comprises:

and the core network equipment receives second information from the second access network equipment, wherein the second information is used for indicating the terminal equipment to notify the area RNA information based on the access network.

16. The method of claim 15, wherein after the core network device receives the second information from the second access network device, the method further comprises:

and the core network equipment sends a paging message in the range of the RNA indicated by the second information.

17. A private network subscription information updating apparatus, wherein the apparatus is configured to perform the method of any of claims 1 to 5, and/or any of claims 13 to 16.

18. A private network subscription information updating apparatus, wherein the apparatus is configured to perform the method of any of claims 6 to 9, and/or, claim 10, and/or, claim 11 to 12.

19. A private network subscription information updating apparatus, comprising a processor and a communication interface, wherein the communication interface is configured to receive a computer program code or instruction and transmit the computer program code or instruction to the processor; the processor executes the computer program code or instructions to cause the apparatus to implement the method of any of claims 1-5 and/or the method of any of claims 13 to 16.

20. A private network subscription information updating apparatus, comprising a processor and a communication interface, wherein the communication interface is configured to receive a computer program code or instruction and transmit the computer program code or instruction to the processor; the processor executes the computer program code or instructions to cause the apparatus to implement the method of any of claims 6 to 9, and/or, claim 10, and/or, claims 11 to 12.

21. A computer-readable storage medium, in which a program is stored, which program, when read and executed by one or more processors, may implement the method of any one of claims 1-5, and/or the method of any one of claims 13-16.

22. A computer-readable storage medium, in which a program is stored, which program, when read and executed by one or more processors, may implement the method of any one of claims 6 to 9, and/or, claim 10, and/or, claim 11 to 12.

23. A communication system, comprising: the apparatus as claimed in claim 17, and/or the apparatus as claimed in claim 18.

24. A communication system, comprising: the apparatus as claimed in claim 19, and/or the apparatus as claimed in claim 20.