WO2021160096A1

WO2021160096A1 - Private network subscription information update method and apparatus

Info

Publication number: WO2021160096A1
Application number: PCT/CN2021/076048
Authority: WO
Inventors: 吴烨丹; 耿婷婷
Original assignee: 华为技术有限公司
Priority date: 2020-02-13
Filing date: 2021-02-08
Publication date: 2021-08-19
Also published as: CN113259924A

Abstract

The present application provides a private network subscription information update method and apparatus, for improving a private network subscription information update process of a terminal device. The method comprises: a core network device receives private network information from a first access network device, the private network information comprising the identifier of at least one private network supported by a cell used by the first access network device and a terminal device for recovering a radio resource control connection; the core network device performs verification on the basis of the private network information and private network subscription information of the terminal device. In the embodiments of the present application, when an inactive terminal device encounters a case that a source cell and/or a target cell does not exist in private network subscription information when updating the private network subscription information, a solution is provided, so that an update process for the private network subscription information of the inactive terminal device can be improved.

Description

Method and device for updating private network contract information

Cross-references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on February 13, 2020, the application number is 202010091446.5, and the application name is "a method and device for updating private network contract information", the entire content of which is incorporated by reference In this application.

Technical field

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

Background technique

In daily life, it is generally the public network that provides network services for terminal devices. The public network, that is, the public land mobile network (PLMN), is a network established and operated by the government or an operator approved by it to provide the public with land mobile communication services. In addition to public networks, operators or private individuals will also build some private networks (non-public networks, NPN) to meet the needs of users. A private network can also be called a non-public network, which refers to a network open to specific users, such as an internal network built by a company, school, or factory. Terminal devices that have not signed a contract with 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 contract information of the terminal device. The contract information refers to the user access information signed by the terminal device with the operator or other company that builds the private network. If the terminal device signs a contract, it can access the corresponding network according to the network identification in the contract information and use the network resource. If the subscription information changes, the core network will initiate a user equipment (UE) configuration update process (UE configuration update) to notify the terminal equipment side of the updated subscription information.

For inactive terminal devices, for the updated subscription information, the source cell and/or target cell may be in the new contract cell list, or may not be in the new contract cell list, and if the source cell and / Or the target cell is not in the new contracted cell list, how to update the contract information in the terminal device, there is currently no good solution. Especially when the target cell is not in the new contracted cell list, the behavior of the target base station and the AMF is not involved in the current communication protocol, and this is a relatively common problem in private network communication.

Summary of the invention

This application provides a method and device for updating private network subscription information, which are used to improve the private network subscription information update process of terminal equipment.

In the first aspect, an embodiment of the present application provides a method for updating private network subscription information, including: a core network device receives private network information from a first access network device, and the private network information includes the first access network device and the terminal device It is used to restore the identity of at least one private network supported by a cell connected to a radio resource control (Radio Resource Control, RRC). The core network equipment is verified 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 this application, a solution is provided for the situation that the source cell and/or target cell are not in the private network subscription information when the INACTIVE state UE updates the private network subscription information, so that the terminal equipment in the INACTIVE state can be improved. The update process of the private network contract information.

In a possible design, at least one private network depends on the first public network, the first public network is the public network on which the target network selected by the terminal device depends, and the network identification of the first public network is the PLMN ID. In the above design, the first access network device reports the first public network identifier and at least one private network identifier that relies on the first public network, so that the core network device can verify the first access based on the first public network identifier and the private network identifier. Network access equipment.

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

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

In a possible design, the core network device performs verification based on the private network information and the private network subscription information of the terminal device, including: if at least one private network identifier in the private network information belongs to the private network subscription information, the verification is passed; or, If the private network identifier in the private network information does not belong to the private network contract information, the verification fails. 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 can determine that the first access network device does not have the access conditions of the contracted cell of the terminal device, so that it can determine that the first access network The device verification failed.

In a possible design, after the core network device receives the private network information from the first access network device, it further includes: the private network identifier in the private network information does not belong to the private network subscription information, then the core network device sends the private network information to the first access network device. The access network device sends a release message, where the release message is used to instruct the first access network device to release the RRC connection with the terminal device. With the above design, when the first access network device fails the verification, resources can be released in time through the release message, thereby improving resource utilization.

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

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

In the second aspect, an embodiment of the present application provides a method for updating private network subscription information, including: a first access network device restores an RRC connection with a terminal device; and the first access network device sends a message to the core network device Private network information. The private network information includes an identifier of at least one private network supported by the cell where the RRC connection between the first access network device and the terminal device is restored. In the embodiment of this application, a solution is provided for the situation that the source cell and/or target cell are not in the private network subscription information when the INACTIVE state UE updates the private network subscription information, so that the terminal equipment in the INACTIVE state can be improved. The update process of the private network contract information.

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

In a possible design, the identity of the private network includes PLMN ID and NID.

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

In a possible design, after the first access network device sends the private network information to the core network device, the method further includes: the first access network device receives a release message from the core network device, where the release message is used to indicate the second An access network device releases the RRC connection with the terminal device. With the above design, when the first access network device fails the verification, resources can be released in time through the release message, thereby improving resource utilization.

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

The embodiment of the present application introduces a solution. When the first access network device fails to acquire the context from the second access network device, the first access network device triggers the RRC establishment process. Or the first access network device successfully acquires the context and triggers the RRC recovery process. The integrity of the communication protocol has been supplemented, which can solve the problem that the update of the private network contract information cannot be completed.

In a fourth aspect, an embodiment of the present application provides a method for updating private network subscription information, including: a first access network device sends a third message to a second access network device, and the third message is used to send a third message to the second access network device. The device requests the context information of the terminal device; the first access network device receives a fourth message from the second access network device, the fourth message is used to indicate that the first access network device fails to obtain the context information, and the fourth message carries indication information , The indication information is used to indicate that the reason for the failure to obtain the context information is related to the private network subscription information. The embodiment of the present application introduces a solution. When the first access network device fails to acquire the context from the second access network device, the first access network device triggers the RRC establishment process. Or the first access network device successfully acquires the context and triggers the RRC recovery process. The integrity of the communication protocol has been supplemented, which can solve the problem that the update of the private network contract information cannot be completed.

In a fifth aspect, the embodiments of the present application provide a method for updating private network subscription information, including: the core network device determines that the second access network device does not belong to the contracted cell of the terminal device, and the second access network device is the terminal device entering The access network device that lastly provided service for the terminal device before the inactive state; the core network device sends a first message to the second access network device, and the first message is used to instruct the second access network device to release the context information of the terminal device.

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

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

In a possible design, after the core network device sends the first message to the second access network device, the method further includes: the core network device receives second information from the second access network device, where the second information is used for Instruct the terminal equipment to be based on the RAN-Based notification area (RNA) information of the access network. In the above design, the second access network device uses the UE's RNA to facilitate the AMF to initiate CN paging in the RNA, which saves a lot of savings compared to paging in the tracking area identity (TAI) list (TAI) Overhead.

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

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

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

The embodiment of the application provides a solution: the second access network device differentiates between the cells that are still in the new private network subscription information and the cells that are not in the new private network subscription information, so that they are not in the new private network. The cell in the subscription information can trigger the UE to initiate the RRC establishment process, so that the INACTIVE UE can complete the private network subscription information update.

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

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

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

In one possible design, the non-access layer user identification is S-TMSI.

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

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

In a ninth aspect, this application provides a device for updating private network subscription information. The device may be a core network device, or a chip or chipset in the core network device. The device may include a processing unit and a transceiving unit. When the device is a core network device, the processing unit may be a processor, and the transceiving unit may be a transceiver; the device may also include a storage unit, and the storage unit may be a memory; the storage unit is used to store instructions, and the processing The unit executes the instructions 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 device is a chip or chipset in a core network device, or a chip or chipset in a network device, the processing unit may be a processor, and the transceiver unit may be an input/output interface, a pin or a circuit, etc.; The processing unit executes the instructions stored in the storage unit to enable the core network device to perform the corresponding functions in the first aspect or the fifth aspect. The storage unit may be a storage unit (for example, a register, a cache, etc.) in the chip or a chipset. ), it may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip or chipset in the communication device.

In a tenth aspect, this application provides a device for updating private network subscription information. The device may be an access network device, or a chip or chipset in the access network device. The device may include a processing unit and a transceiving unit. When the device is an access network device, the processing unit may be a processor, and the transceiving unit may be a transceiver; the device may also include a storage unit, and the storage unit may be a memory; the storage unit is used to store instructions, the The processing unit executes the instructions stored in the storage unit, so that the access network device executes 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 device is a chip or chipset in an access network device, the processing unit can be a processor, and the transceiver unit can be an input/output interface, a pin or a circuit, etc.; the processing unit executes instructions stored in the storage unit , So that the access network device can perform the corresponding functions in the second aspect, third aspect, fourth aspect, sixth aspect, seventh aspect, or eighth aspect, and the storage unit may be a storage in the chip or chipset. The unit (for example, register, cache, etc.) may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip or chipset in the communication device.

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

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

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

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

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

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

In a seventeenth aspect, this application also provides a communication system, which includes the access network device in any one of the embodiments of the eighth aspect.

In an eighteenth aspect, this application also provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when run on a computer, cause the computer to execute the above-mentioned first or fifth aspect Methods.

In a nineteenth aspect, this application also provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when run on a computer, cause the computer to execute the second or third aspect or the first aspect described above. The method according to the fourth aspect or the sixth aspect or the seventh aspect or the eighth aspect.

In a twentieth aspect, this application also provides a computer program product including instructions, which when run on a computer, cause the computer to execute the method described in the first or fifth aspect.

In the twenty-first aspect, this application also provides a computer program product that includes instructions, which when run on a computer, causes the computer to execute the above-mentioned second aspect, third aspect, fourth aspect, sixth aspect, or seventh aspect. Or the method described in the eighth aspect.

Description of the drawings

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

2 is a schematic diagram of the architecture of a communication system provided by an embodiment of this application;

FIG. 3 is a schematic structural diagram of an access network device provided by an embodiment of this application;

FIG. 4 is a schematic structural diagram of an access network device provided by an embodiment of this application;

FIG. 5 is a schematic structural diagram of an access network device provided by an embodiment of this application;

FIG. 6 is a schematic flowchart of a method for updating private network subscription information provided by an embodiment of the application;

FIG. 7 is a schematic diagram of a private network subscription information update process provided by an embodiment of the application;

FIG. 8 is a schematic diagram of a private network subscription information update process provided by an embodiment of the application;

FIG. 9 is a schematic diagram of a private network subscription information update process provided by an embodiment of the application;

FIG. 10 is a schematic diagram of a private network subscription information update process provided by an embodiment of the application;

FIG. 11 is a schematic diagram of a private network subscription information update process provided by an embodiment of the application;

FIG. 12 is a schematic diagram of a private network subscription information update process provided by an embodiment of the application;

FIG. 13 is a schematic diagram of a private network subscription information update process provided by an embodiment of the application;

FIG. 14 is a schematic diagram of a private network subscription information update device provided by an embodiment of the application;

Fig. 15 is a schematic diagram of an apparatus for updating private network subscription information provided by an embodiment of the application.

Detailed ways

In order to facilitate the understanding of the embodiments of the present application, the following introduces terms related to the embodiments of the present application:

1. Public network

In daily life, it is generally the public network that provides network services for terminal devices. The public network, that is, the public land mobile network (PLMN), is a network established and operated by the government or an operator approved by it to provide the public with land mobile communication services. This network is usually interconnected with the public switched telephone network (PSTN) to form an entire region or country-scale communication network.

Different PLMN identification (ID) can be used to distinguish different PLMN networks. The PLMN identity is composed of a mobile country code (mobile contrast code, MCC) and a mobile network number (mobile net code, MNC). Among them, MCC uniquely indicates the country where the mobile user belongs. For example, China's MCC is 460. MNC only indicates the network in the country. For example, China Mobile’s MNC is 00 and China Unicom’s MNC is 01.

2. Private network

In addition to the public network, for certain purposes, operators or private individuals will also build some private networks (non-public networks, NPN) to meet the needs of users. A private network can also be called a non-public network, which refers to a network open to specific users, such as an internal network built by a company, school, or factory. Terminal devices that have not signed a contract with the private network are not allowed to access the private network. Private networks are divided into non-independent private networks and independent private networks.

(1) Non-independent private network

The network resources used by the non-stand-alone non-public network (NSA-NPN, or public network integrated non-public network, PNI-NPN) are part of the public network. It can also be said that the non-independent private network depends on the public network, and the non-independent private network is also called a closed access group (CAG). The identification of the non-independent private network includes two parts, namely the PLMN ID and the CAG ID. Among them, the PLMN ID of the non-independent private network is consistent with the public network on which it depends. For multiple dependent private networks that depend on the same public network, the CAG ID of each dependent private network is unique. That is to say, for multiple dependent private networks that depend on the same public network, you can It is distinguished only by CAG ID.

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

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

That is to say, both the non-independent private network #1 and the non-independent private network #2 are private networks that rely on the public network identified as PLMN#1. In some situations, the above two private networks can be distinguished only by CAG#1 and CAG#2.

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

(2) Independent private network

Stand-alone non-public Network (SNPN) refers to a private network that does not rely on the network functions of the public network. Similarly, the identity of an independent private network is also divided into two parts, namely PLMN ID and NID. For an independent private network that depends on the public network, its PLMN ID is the same as the dependent public network. For an independent private network that does not rely on the public network (for example, it can be deployed by an enterprise), the MCC of its PLMN ID is 999. For multiple independent private networks that depend on the same public network, the NID of each non-independent private network is unique, that is to say, for multiple independent private networks that depend on the same public network, you can only pass the NID Make a distinction.

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

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

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

In other words, the independent private network #1 and the independent private network #2 are both private networks that rely on the public network identified as PLMN#1. In some cases, the above two private networks can be distinguished only by NID#1 and NID#2.

In addition, the MCC of the PLMN ID of the independent private network #3 is 999, indicating that the independent private network #3 is an independent private network deployed by enterprises and others without the help of operators.

As a possible way, the independent private network does not support the handover and cell reselection of terminal equipment between independent private networks and public networks, non-independent private networks, and other independent private networks. The private network cell is switched to the public network cell, the non-independent private network cell and other independent private network cells, and vice versa; the terminal equipment in the idle state/deactivated state cannot be reselected from the independent private network cell to the public network cell, and vice versa . It is understandable that, as another possible implementation manner, the independent private network can support the handover and cell reselection of the terminal device between the independent private network and the public network, the non-independent private network, and other independent private networks.

3. RRC status of terminal equipment

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

4. Signing information

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

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

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

The architecture of a possible communication system to which the method for updating private network subscription information provided by the embodiments of the present application is applicable may include network opening function network elements, policy control function network elements, data management network elements, and applications Function network element, core network access and mobility management function network element, session management function network element, terminal equipment, access network equipment, user plane function network element and data network. Wherein, FIG. 2 shows a possible example of the architecture of the communication system, which specifically includes: network exposure function (NEF) network element, policy control function (PCF) network element , Data management network element (UDM) network element, application function network element (AF) network element, AMF network element, session management function network element (session management function, SMF) network element, UE, interface Access network (AN) equipment, user plane function (UPF) network elements, and data network (DN). Among them, the AMF network element and the terminal device can be connected through the N1 interface, the AMF and the AN device can be connected through the N2 interface, the AN device and the UPF can be connected through the N3 interface, and the SMF and UPF can be connected through the N4 interface. , UPF and DN can be connected through the N6 interface. The interface name is only an example, and the embodiment of the present application does not specifically limit this. It should be understood that the embodiment of the present application is not limited to the communication system shown in FIG. 2. The name of the network element shown in FIG. 2 is only used as an example for illustration, and is not included in the communication system architecture applicable to the method of the present application. The limit of the network element. The function of each network element or device in the communication system is described in detail below:

The terminal equipment, which may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a way to provide users with voice and/or data connectivity Sexual equipment. For example, the terminal device may include a handheld device with a wireless connection function, a vehicle-mounted device, and the like. At present, the terminal device may be: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palmtop computer, a mobile Internet device (MID), a wearable device, a virtual reality (VR) device, an augmented Augmented reality (AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, and smart grid (smart grid) Wireless terminals in ), wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, etc. Wherein, the terminal device described in FIG. 2 is shown as a UE, which is only used as an example and does not limit the terminal device.

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

Exemplarily, 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) . Among them, one radio access network device may include one CU and at least one DU, as shown in FIG. 3. The CU is connected to at least one DU and can be used to manage or control the at least one DU. This structure can disassemble the protocol layer of the wireless access network equipment in the communication system, in which part of the protocol layer functions are implemented in the CU, and the remaining part or all of the protocol layer functions are distributed in the DU, and the CU centrally controls the DU. Taking the gNB as an example of the radio access network device, the protocol layer of gNB includes the radio resource control (radio resource control, RRC) layer, the service data adaptation protocol (SDAP) layer, and the packet data aggregation protocol (packet data). The convergence protocol (PDCP) layer, the radio link control (RLC) layer, the media access control sublayer (media access control, MAC) layer, and the physical layer. Among them, exemplarily, the CU may be used to implement the functions of the RRC layer, the SDAP layer, and the PDCP layer, and the DU may be used to implement the functions of the RLC layer, the MAC layer, and the physical layer. The embodiment of this application does not specifically limit the protocol stack included in the CU and DU. CU and DU can be connected by F1 interface, CU and other wireless access network equipment can be connected by Xn interface, CU and 5G core network (5G Core, 5GC) can be connected by NG interface, as shown in Figure 4.

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

The data network, such as the data network (DN) shown in FIG. 2, may be the Internet, IP Multi-media Service (IMS) network, local network (ie, local network, such as mobile Edge computing (mobile edge computing, MEC) network) and so on. The data network includes an application server, and the application server provides business services for the terminal device by performing data transmission with the terminal device.

The core network is used to connect the terminal device to a DN that can implement the service of the terminal device. The following describes the functions of each network element in the core network:

The core network access and mobility management function network element can be used to manage the access control and mobility of the terminal device. In practical applications, it includes the long term evolution (LTE) network The mobility management function in the mobility management entity (MME) in the framework, and the access management function is added, which can be specifically responsible for the registration of the terminal equipment, mobility management, tracking area update process, reachability detection, Session management function network element selection, mobile state transition management, etc. 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 Figure 2, in future communications, such as 6G, the core network The access and mobility management function network element can still be an AMF network element or have other names, 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 Namf service.

The session management function network element can be used to be responsible for the session management of the terminal device (including the establishment, modification and release of the session), the selection and reselection of the user plane function network element, and the internet protocol of the terminal device. , IP) address allocation, quality of service (quality of service, QoS) control, etc. 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 communications, such as 6G, the session management function network element may still be an SMF network element. Yuan, or other names, this application is not limited. When the session management function network element is an SMF network element, the SMF can provide the Nsmf service.

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

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

The data management network element may be used 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 (unified data management, UDM). For example, as shown in FIG. 2, in future communications, such as 6G, the data management network element may still be UDM network elements, or other names, are not limited in this application. When the data management network element is a UDM network element, the UDM network element may provide Nudm services.

The network open function network element can be used to enable 3GPP to safely provide network service capabilities to third-party AF (for example, Service Capability Server (SCS), Application Server (AS), etc.). For example, in 5G, the network opening function network element may be NEF. For example, as shown in Figure 2, in future communications, such as 6G, the network opening function network element may still be a NEF network element, or have other names. , This application is not limited. When the network opening function network element is NEF, the NEF may provide Nnef services to other network function network elements.

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

It should be noted that the architecture of the communication system shown in FIG. 2 is not limited to only including the network elements shown in the figure, and may also include other devices not shown in the figure. The specifics of this application will not be 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. The distribution form shown in FIG. 2 is only exemplary, and this application does not limit it.

For the convenience of description, the following description of this application takes the network element shown in FIG. 2 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 this application are merely examples, and may also be referred to as other names in future communications, or the network elements involved in this application may also be used by other entities or devices with the same function in future communications. Instead, this application does not limit this. Here is a unified explanation, and I won’t repeat it in the follow-up.

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

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

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

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

-Only allow access to the CAG indication, if this indication is carried, it means that the terminal device cannot access the public network.

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

For inactive terminal devices, as a possible implementation, when AMF triggers the configuration update process, it will send a downlink non-access stratum (NAS) transmission (DOWNLINK NAS TRANSPORT) to the source base station. The transmission carries the NAS-protocol data unit (protocol data unit, PDU) and the mobility restriction list (Mobility Restriction List). Among them, the NAS-PDU is sent to the terminal device by the AMF, and the base station transparently transmits the NAS-PDU to the terminal device after receiving the NAS-PDU . The Mobility Restriction List is sent by the AMF to the base station, and both the NAS-PDU and the Mobility Restriction List carry updated private network subscription information. The source base station is the last serving base station before the terminal device enters the inactive state from the connected state. The source base station sends a paging message to the base station in the RNA of the terminal device, and these base stations transparently transmit to all UEs connected to it. The UE that listens to the paging message will check whether it contains its own I-RNTI. Initiate an RRC recovery request 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 can 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 can receive 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 the embodiment of the present application.

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

Regarding the updated subscription information, the source base station and target base station may be in the new contract cell list or not in the new contract cell list. If the source base station and target base station are not in the new contract cell list, how does AMF update terminal equipment? There is currently no good solution for the contract information in China.

Based on this, this application provides a method and device for updating private network subscription information to improve the private network subscription information update process of terminal equipment in the INACTIVE state. Among them, the method and the device are based on the same inventive concept. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.

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

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

It is understandable that in the embodiments of the present application, the terminal device and/or the network device can perform some or all of the steps in the embodiments of the present application. These steps or operations are only examples, and the embodiments of the present application may also perform other operations or various operations. Deformation of the operation. In addition, each step may be executed in a different order presented in the embodiments of the present application, and it may not be necessary to perform all the operations in the embodiments of the present application.

Refer to Figure 6, which is a flowchart of the method for updating private network subscription information provided by this application. The method includes:

S601: The first access network device resumes the RRC connection with the terminal device.

The terminal device may be an inactive UE, and the first access network device is the access network device that initiated the recovery request by the terminal device.

S602: Private network information sent by the first access network device to the core network device.

Wherein, the private network information includes the identification of at least one private network supported by the cell used by the first access network device and the terminal device to restore the RRC connection. Correspondingly, the core network device can receive the private network information sent by the first access network device.

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

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

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

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

The public network can also be called a public land mobile network, or PLMN. It should be understood that "public network" is only an exemplary naming, and other names may be used in future communication development. As long as the functions of the public network in the embodiments of the present application can be realized, it can be understood as the public network in the embodiments of the present application.

If the private network is a non-independent private network, the identification of the private network can include two parts, namely the PLMN ID and the CAG ID, 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 non-independent private network #1 can be expressed as: PLMN#1 CAG#1; the identity of the non-independent private network #2 can be expressed as: PLMN#1 CAG#2. Among them, the non-independent private network #1 and the non-independent private network #2 are both private networks that rely on the public network identified as PLMN#1.

If the private network is an independent private network, the identification of the private network may include two parts, namely PLMN ID and NID. For example, the identification of the private network may be PLMN #1. For an independent private network that depends on the public network, its PLMN ID is the same as the dependent public network. For an independent private network that does not rely on the public network (for example, it can be deployed by the enterprise), the MCC of its PLMN ID is a fixed value. Such as 999. For example, the identity of independent private network #1 can be expressed as: PLMN#1 NID#1; the identity of independent private network #2 can be expressed as: PLMN#1 NID#2; the identity of independent private network #3 can be expressed as: PLMN #3(MCC=999)NID#1. Among them, the independent private network #1 and the independent private network #2 are both private networks that rely on the public network identified as PLMN#1.

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

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

S603: The core network device performs verification based on the private network information and the private network subscription information of the terminal device.

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

In the embodiment of this application, a solution is provided for the situation that the source cell and/or target cell are not in the private network subscription information when the INACTIVE state UE updates the private network subscription information, so that the terminal equipment in the INACTIVE state can be improved. The update process of the private network contract information.

In a possible implementation, 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 pass the verification.

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

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

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

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. Understandably, the private network subscription information may be the latest private network subscription information. Or, the private network contract information may be updated private network contract information.

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

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

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

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

In another possible implementation manner, if the verification fails, the core network device may send first notification information to the first access network device, and the first notification information is used to notify the first access network device that the terminal device passes through the public network. Make access.

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

In other embodiments, the core network device may also carry a NAS-PDU in the release message, and the NAS-PDU carries private network subscription information, so that the first access network device may use the NAS-PDU when receiving the release message. Transparently transmitted to terminal equipment.

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

After the core network device triggers the private network subscription information update process, it can receive second indication information from the second access network device. The second indication information is used to indicate that the core network device is receiving the private network information of the first access network device. Then, the private network subscription information is sent to the first access network device, or the second indication information is used to indicate that the core network device, the second access network device, cannot send the latest private network subscription information to the terminal device.

In another possible implementation manner, before the core network device receives the path switching request from the first access network device, the terminal device may trigger the process of restoring the RRC connection. 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 the cell that the terminal device accesses before entering the INACTIVE state (for ease of description, the following This is referred to as the source cell), and it is the same cell as the cell accessed when the terminal device resumes the RRC connection from the INACTIVE state (for the convenience of description, it is referred to as the target cell below).

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

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

In order to better understand the methods provided in the embodiments of the present application, the following describes the private network subscription information update process in detail in conjunction with specific scenarios. For the convenience of description, the following description takes the core network device as AMF, the private network as CAG, and the public network as PLMN as an example.

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

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

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

In an exemplary illustration, the private network subscription information may be UE1's updated private network subscription information. For example, compared with the private network subscription information before the update, the updated private network subscription information of the UE1 may not have exactly the same sign-up cell.

As an example, assume that the private network subscription information before the update includes PLMN#1 CAG#1, PLMN#1CAG#2 and PLMN#2CAG#2, and the updated private network subscription information includes PLMN#1CAG#1 PLMN#1CAG#3 and PLMN#2CAG#2.

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

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

The second indication information is used to indicate that the UE1 is in the 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 It can also instruct the AMF to send the private network subscription information to the target base station after receiving the path switch request from the target base station, or the second indication information is used to instruct the core network device that the second access network device cannot send the latest private network to the terminal device. Network contract information.

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

S703: The source base station sends a paging message (paging) to the target base station. The paging can be used to notify UE1 to resume the RRC connection. Go to S704.

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

S704: The target base station sends paging to UE1. The paging can be used to notify UE1 to resume the RRC connection. Go to S705.

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

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

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

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

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

The recovery context request may be used by the target base station to request the source base station to send the context of UE1, and the context is used for the target base station and UE1 to resume the RRC connection.

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

S707: The source base station sends a recovery context response (RETRIEVE UE CONTEXT RESPONSE) to the target base station. Go to S708.

The recovery context response may carry the context of UE1.

S708: Perform RRC recovery (RRC RESUME) between the target base station and UE1. Go to S709.

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

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

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

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

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

It is understandable that, in this 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, where the private network information includes the ID of at least one CAG supported by the second cell. Further, the private network information includes the ID of at least one CAG under the PLMN supported by the second cell selected by the terminal device. For example, if the terminal device accesses through the PLMN1 of the second cell, the ID of the at least one CAG can be understood as the ID of the CAG dependent on the PLMN 1, or the ID of the CAG under PLMN1. Among them, PLMN 1 is the public network on which the target network selected by UE1 depends. Perform S711.

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

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

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

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

In another implementation manner, 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 an implementation manner, the target base station may send a path switch request (PATH SWITCH REQUEST) to the AMF, and the PATH SWITCH REQUEST may carry private network information. The path switch request can be used to request the AMF to transfer the interface between the AMF and the target base station and/or the data receiving point of the data channel to the target base station. It can be understood that when the core network sends data to UE1, it may first be sent to the target base station, and the target base station will forward it to UE1.

S711, the AMF performs verification based on the private network information and UE1's private network subscription information. If the verification passes, step S712 is executed; if the verification fails, step S716 is executed.

Among them, if at least one CAG ID in the private network information belongs to UE1's private network subscription information, the verification is passed.

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

S712. The AMF sends a path switch acknowledgement (path switch acknowledge) to the target base station. Perform S713.

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

S713: The target base station sends a UE context release message (UE CONTEXT RELEASE) to the source base station. Go to S714.

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

S714: The AMF sends the private network subscription information of UE1 to the target base station. Perform S715.

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

S715: The target base station sends private network subscription information to UE1.

In an implementation manner, the target base station may send a downlink information forwarding message to UE1, and the downlink information forwarding message may carry UE1's private network subscription information.

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

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

The release message can be used to instruct the target base station to release the RRC connection with UE1.

Further, the target base station may send the release message to UE1. The UE1 can switch from the RRC CONNECTED state to the RRC IDLE state or the RRC INATIVE state, or from the RRC INATIVE state to the RRC IDLE state according to the type of the release message.

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

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

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

In another possible implementation manner, the AMF may also carry UE1's private network subscription information in the release message. For example, the release message may carry NAS-PDU, which carries UE1's private network subscription information. Then, the target base station sends UE1's private network subscription information to UE1. For the specific process, please refer to step S715, and the repetition will not be repeated.

Scenario 2: UE1 accesses the first cell of the source base station before entering the INACTIVE state, and accesses the second cell of the source base station when UE1 resumes the RRC connection 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 update process of Scenario 2 is similar to the private network subscription information update process of Scenario 1. The difference is that the same base station performs the private network subscription information update process of Scenario 1 in the private network subscription information update process of Scenario 2. The actions of the source base station and the target base station are not repeated here.

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

Scenario 3: UE1 accesses the first cell of the source base station before entering the INACTIVE state, and accesses the first cell of the source base station when UE1 resumes 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 in Scenario 3 is similar to the private network subscription information update process in Scenario 2. The difference is that in the private network subscription information update process in Scenario 2, the information of the second cell is replaced with the first The information of the cell will not be repeated here. Optionally, in scenario 3, the information exchange between the source base station and the target base station may not be performed. The information exchange between the source cell and the target cell may not be performed.

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

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

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

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

Solution 1: The method includes: when the first access network device obtains the context of the UE from the second access network device, the second access network device can contact the first access network device based on the private network subscription information sent by the core network device. authenticating. If the verification fails, the second access network device sends a failure to restore the UE context to the first access network device, and the first access network device triggers the RRC establishment process with the UE. If the verification is successful, the second access network device sends the UE context to the first access network device, and the first access network device triggers the RRC recovery process with the UE.

Among them, the first access network device is the access network device where the target cell is located, the second access network device is the access network device where the source cell is located, and the source cell is the first cell that the terminal device accesses before entering the INACTIVE state. The target cell is the cell that the terminal device accesses when the RRC connection is restored from the INACTIVE state.

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

In order to better understand the method provided by solution 1, the following takes the core network device as an AMF as an example, combined with a possible scenario to illustrate solution one. As shown in Figure 9, the private network subscription information update process can be:

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

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

In an implementation manner, the paging message may be sent to all base stations in the RNA of the UE.

S903: The target cell initiates a RAN paging to the UE.

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

S904: The UE sends an RRC recovery request message to the target cell. Among them, the UE camps on the target cell.

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

Optionally, the target cell can obtain 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, go to S907.

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

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

S907: The source cell sends the UE context recovery failure to the target cell.

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

S908: Perform RRC establishment between the target cell and the UE.

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

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

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

S911: The AMF sends an initial context establishment request to the target cell. Among them, the initial context establishment request message may carry the UE's private network subscription information.

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

S913: The target cell sends a downlink information forwarding to the UE, where the downlink information forwarding message 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 update of the private network subscription information 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 the update of the private network subscription information is completed.

It should be noted that steps S901 to S903 and S908 to S915 are optional steps, and may or may not be executed in specific implementations.

It is understandable that the actions of the source cell may be performed by the access network device where the source cell is located, that is, the second access network device, and the actions of the target cell may be performed by the access network device where the target cell is located, that is, the first access network device. implement.

Solution 2: The method includes: when the first access network device obtains the UE context 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 device triggers the RRC recovery process with the UE, and sends private network subscription information to the UE after the RRC connection between the first access network device and the UE is restored.

In order to better understand the method provided in the third embodiment, the following takes the core network device as an AMF as an example for description. The private network subscription information update process can be:

Steps A1 to A5, please refer to S901 to S905 for details, which will not be repeated here.

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

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

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

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

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

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

The second embodiment of the present application introduces a solution. When the target cell fails to obtain the context from the source cell, the target cell triggers the RRC establishment process. Or the target cell succeeds in acquiring the context and triggers the RRC recovery process. The integrity of the communication protocol has been supplemented, which can solve the problem that the update of the private network contract information cannot be completed.

Embodiment 3: This application provides another method for updating private network subscription information. Taking the core network equipment as AMF as an example, as shown in Figure 10, the private network subscription information update process can be as follows:

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

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

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

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

For S1002～S1005, please refer to S902～S905, which will not be repeated here.

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

S1007: The target cell and the UE perform RRC recovery.

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

Exemplarily, the message may mark 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 message carries 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 the update 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 the update of the private network subscription information is completed.

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

It is understandable that the actions of the source cell may be performed by the access network device where the source cell is located, that is, the second access network device, and the actions of the target cell may be performed by the access network device where the target cell is located, that is, the first access network device. implement. For the first access network device, the second access network device, and the core network device, please refer to the related descriptions of the first access network device, the second access network device, and the core network device in Embodiment 1, which will not be repeated here.

The third embodiment of the present application introduces a solution: the AMF sends the new subscription information twice, and notifies the UE and the base station respectively, so as to avoid the source base station from making further judgments. In this way, the behavior of the base station side is basically the same as the existing process, and the protocol changes are relatively small.

Embodiment 4: This application provides another method for updating private network subscription information. Taking the core network equipment as AMF as an example, as shown in Figure 11, the private network subscription information update process can be as follows:

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

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

S1102: The AMF sends a release message to the source cell.

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

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

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

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

S1104, the AMF initiates CN paging.

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

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

Exemplarily, a paging initiated by a core network device (such as AMF) may be called CN Paging. CN paging can be initiated by the AMF of the 5G core network to send a paging message to the base station, and the base station transparently transmits it to all UEs connected to its related cell. The UE that listens to the paging message will check whether it contains its own ID. If yes, you can initiate an RRC setup request to connect to the network; if not, you can ignore this paging request.

S1105: The target cell sends a CN page.

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

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

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

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

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

The cell still in the new private network subscription information sends RAN paging, and the cell still in the new private network subscription information performs RAN paging in the cell. If the UE receives a paging message in a cell still in the new private network subscription information, it initiates RRC recovery. Optionally, RAN paging may carry I-RNTI.

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

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

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

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

The paging message may carry I-RNTI and/or S-TMSI. Optionally, the aforementioned I-RNTI or S-TMSI may be indicated by per cell, so that the target base station can determine the UE identity that needs to be carried in the paging message sent by the corresponding cell. Alternatively, the paging message may also carry indication information, which is used to instruct the target base station to send a paging message containing I-RNTI or S-TMSI in the corresponding cell, or the indication information is used to instruct the target base station to download Whether your cell 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 to carry the I-RNTI paging message in the cell based on the above 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 above paging message.

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

S1204: Establish an RRC connection between the UE and the target cell.

For S1205～S1210, please refer to S910～S915, which will not be repeated here.

It is understandable that the actions of the source cell may be performed by the access network device where the source cell is located, that is, the second access network device, and the actions of the target base station and/or target cell may be performed by the access network device where the target cell is located, that is, the second access network device. One access network equipment execution. For the first access network device, the second access network device, and the core network device, please refer to the related descriptions of the first access network device, the second access network device, and the core network device in Embodiment 1, which will not be repeated here.

The fifth embodiment of the present application provides a solution: the source cell differentiates between the cells that are still in the new private network subscription information and the cells that are not in the new private network subscription information, so that they are not included in the new private network subscription information. The cell can trigger the UE to initiate the RRC establishment process, so that the INACTIVE UE can complete the private network subscription information update.

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

When the source cell receives the new private network subscription information sent by the AMF, and finds that the target cell is not in the new private network subscription message, it does not release the UE, but sends the RRC establishment to the UE, so that the UE in the INACTIVE state and the IDLE state Behave the same.

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 can be triggered to perform RRC recovery and complete the update of the private network subscription information.

In order to better understand the solution provided in the sixth embodiment of this application, taking the core network device as an AMF as an example, as shown in Figure 13, the private network subscription information update process can be:

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

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

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

It is understandable that the above actions of the source cell and the target cell may be performed by the same access network device, that is, the access network device where the source cell and the target cell are located.

In the fifth embodiment of this application, for the case where 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, a solution is introduced: the base station ignores the new private network subscription information and allows the UE to complete RRC Restore, complete the update of the new private network contract information.

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

In a specific implementation manner, the device can be specifically used to implement the method executed by the core network device in the embodiments described in FIG. 6 to FIG. 7. The device may be the core network device itself or the chip in the core network device. Or a part of the chipset or chip used to perform related method functions. Wherein, the communication unit 1401 is configured to receive private network information from the first access network device, and the private network information includes at least one private network supported by the first access network device and the terminal device for restoring the radio resource control RRC connected cell The logo of the net. 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, and the private network subscription information is stored by the core network device.

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

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

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

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

In a specific implementation manner, the device can be specifically used to implement the method executed by the core network device in the embodiments described in FIG. 6 to FIG. 7. The device may be the core network device itself or the chip in the core network device. Or a part of the chipset or chip used to perform related method functions. Among them, the processing unit 1402 is used to restore the radio resource control RRC connection with the terminal device; the communication unit 1401 is used to send private network information to the core network device, and the private network information includes the recovery of the first access network device and the terminal device The identification of at least one private network supported by the cell to which the radio resource control RRC is connected.

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

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

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

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

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

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

In a specific implementation, the device may be specifically used to implement the method executed by the core network device in the embodiment described in FIG. 11. The device may be the core network device itself, or the chip or chipset in the core network device. Or a part of the chip used to perform related method functions. Wherein, the processing unit 1402 is configured to determine that the second access network device does not belong to the contracted cell of the terminal device, and the second access network device is the access network device that finally provides service for the terminal device before the terminal device enters the inactive state; The communication unit 1401 is configured to send a first message to the second access network device, where the first message is used to instruct the second access network device to release the context information of the terminal device.

The communication unit 1401 may be further configured to: after sending the first message to the second access network device, receive second information from the second access network device, where the second information is used to instruct the terminal device to notify based on the access network Area RNA information.

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

The division of units in the embodiments of this application is illustrative, and is only a logical function division. In actual implementation, there may be other division methods. In addition, the functional units in the various embodiments of this application can be integrated into one processing unit. In the device, it can also exist alone physically, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It can be understood that, for the function or implementation of each unit in the embodiment of the present application, reference may be made to the related description of the method embodiment.

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

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

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

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

The embodiment of the present invention also provides a computer-readable storage medium for storing computer software instructions required to execute the above-mentioned processor, which contains a program required to execute the above-mentioned processor.

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

This application is described with reference to flowcharts and/or block diagrams of methods, equipment (systems), and computer program products according to this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are used to generate It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, then this application is also intended to include these modifications and variations.

Claims

A method for updating private network contract information, which is characterized in that it includes:

The core network device receives private network information from the first access network device, where the private network information includes at least one private network supported by the cell used by the first access network device and the terminal device to restore the radio resource control RRC connection The logo;

The core network device performs verification based on the private network information and the private network subscription information of the terminal device.
The method according to claim 1, wherein the verification by the core network device 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 subscription 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 fails.
The method according to claim 1 or 2, wherein after the core network device receives the private network information from the first access network device, the method further comprises:

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, and the release message is used to indicate the first access The network device releases the RRC connection with the terminal device.
The method according to claim 3, wherein the release message carries first indication information, and the first indication information is used to indicate that the reason for releasing the terminal device and/or the reason for the path conversion failure is related to the private network. Contract information related.
The method of claim 3, wherein the first indication information includes at least one of the following: an invalid private network identifier; an unsupported private network identifier; not within the scope of a private network contract; an unreasonable private network Access.
A method for updating private network contract information, which is characterized in that it includes:

The first access network device resumes the radio resource control RRC connection with the terminal device;

The first access network device sends private network information to the core network device, where the private network information includes at least one private network supported by the cell where the first access network device and the terminal device resume the radio resource control RRC connection Logo.
The method according to claim 6, wherein after the first access network device sends the private network information to the core network device, the method further comprises:

The first access network device receives the private network subscription information of the terminal device.
The method according to claim 6, wherein after the first access network device sends the private network information to the core network device, the method further comprises:

The first access network device receives a release message from the core network device, where the release message is used to instruct the first access network device to release the RRC connection with the terminal device.
The method according to claim 8, wherein the release message carries indication information, and the indication information is used to indicate that the reason for releasing the terminal device and/or the reason for the path conversion failure is related to the private network subscription information.
A method for updating private network contract information, which is characterized in that it includes:

The second access network device receives a third message from the first access network device, where the third message is used to request context information of the terminal device from the second access network device;

If the first cell does not belong to the contracted cell indicated by the private network subscription information, the first cell is the cell where the terminal device performs radio resource control RRC connection recovery, and the first cell is the first access network In the cell of the device, the second access network device sends a fourth message to the first access network device, where the fourth message is used to indicate that the first access network device fails to obtain the context information, so The fourth message carries indication information, and the indication information is used to indicate that the reason for the failure to obtain the context information is related to the private network subscription information.
The method of claim 10, wherein the method further comprises:

The second access network device receives the private network subscription information sent by the core network device.
The method according to claim 10 or 11, wherein the indication information includes at least one of the following: invalid private network identifier; unsupported private network identifier; not within the scope of private network contract; unreasonable private network Access.
The method according to any one of claims 10-12, wherein before the second access network device receives the third message from the first access network device, the method further comprises:

The second access network device disconnects the RRC connection with the terminal device, and saves the context information of the terminal device.
A method for updating private network contract information, which is characterized in that it includes:

The first access network device sends a third message to the second access network device, where the third message is used to request the second access network device for context information of the terminal device;

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 obtain the context information, and the fourth The message carries indication information, and the indication information is used to indicate that the reason for the failure to obtain the context information is related to the private network subscription information;

Acquiring, by the first access network device, the updated private network subscription information of the terminal device from the core network device;

The first access network device sends the private network subscription information to the terminal device.
The method according to claim 14, wherein the first indication information includes at least one of the following: invalid private network identification; unsupported private network identification; not within the scope of private network subscription; unreasonable private network Access.
A method for updating private network contract information, which is characterized in that it includes:

The core network device determines that the first cell does not belong to the contracted cell of the terminal device, the first cell is the last cell that the terminal device provides services for the terminal device before the terminal device enters the inactive state, and the first cell is the second cell The cell of the access network equipment;

The core network device sends a first message to the second access network device, where the first message is used to instruct the second access network device to release the context information of the terminal device.
The method according to claim 16, wherein the first message carries first indication information, and the first indication information is used to indicate that the reason for releasing the context information is related to private network subscription information.
The method according to claim 16 or 17, wherein after the core network device sends the first message to the second access network device, the method further comprises:

The core network device receives second information from the second access network device, where the second information is used to indicate that the terminal device is based on the RNA information of the notification area of the access network.
The method according to claim 18, wherein after the core network device receives the second information from the second access network device, the method further comprises:

The core network device sends a paging message within the RNA range indicated by the second information.
A private network contract information update device, characterized in that the device includes:

The communication unit is configured to receive private network information from a first access network device, where the private network information includes at least one of the cells supported by the first access network device and the terminal device for restoring a radio resource control RRC connection The logo of the private network;

The processing unit is configured to perform verification based on the private network information and the private network subscription information of the terminal device.
The device according to claim 20, wherein the processing unit is specifically configured to:

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

Or, if the private network identifier in the private network information does not belong to the private network subscription information, the verification fails.
The device according to claim 20 or 21, wherein the communication unit is further configured to: after receiving the private network information from the first access network device, the private network identifier in the private network information does not belong to The private network subscription information sends a release message to the first access network device, where the release message is used to instruct the first access network device to release the RRC connection with the terminal device.
The apparatus according to claim 22, wherein the release message carries first indication information, and the first indication information is used to indicate that the reason for releasing the terminal device and/or the reason for the path conversion failure is related to the private network. Contract information related.
The device according to claim 22, wherein the first indication information includes at least one of the following: invalid private network identifier; unsupported private network identifier; not within the scope of private network contract; unreasonable private network Access.
A private network subscription information update device, applied to a first access network device, or applied to a chip in the first access network device, characterized in that the device includes:

A processing unit for restoring the radio resource control RRC connection with the terminal device;

The communication unit is configured to send private network information to a 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 resume a radio resource control RRC connection.
The device according to claim 25, wherein the communication unit is further configured to:

After sending the private network information to the core network device, the private network subscription information of the terminal device is received.
The device according to claim 25, wherein the communication unit is further configured to:

After sending the private network information to the core network device, a release message from the core network device is received, where the release message is used to instruct the first access network device to release the RRC connection with the terminal device.
The apparatus according to claim 27, wherein the release message carries indication information, and the indication information is used to indicate that the reason for releasing the terminal device and/or the reason for the path conversion failure is related to the private network subscription information.
A private network subscription information update device, applied to a second access network device, or applied to a chip in the second access network device, characterized in that the device includes:

The communication unit is used to communicate with the first access network device;

A processing unit, configured to: receive a third message from a first access network device through the communication unit, the third message being used to request context information of the terminal device from the second access network device;

If the first cell does not belong to the contracted cell indicated by the private network subscription information, the first cell is the cell where the terminal device performs radio resource control RRC connection recovery, and the first cell is the first access network The cell of the device sends a fourth message to the first access network device, where the fourth message is used to indicate that the first access network device fails to obtain the context information, and the fourth message carries indication information, The indication information is used to indicate that the reason for the failure to obtain the context information is related to the private network subscription information.
The device according to claim 29, wherein the processing unit is further configured to:

Receiving the private network subscription information sent by the core network device through the communication unit.
The device according to claim 29 or 30, wherein the indication information includes at least one of the following: an invalid private network identifier; an unsupported private network identifier; not within the scope of a private network contract; an unreasonable private network Access.
The device according to any one of claims 29-31, wherein the processing unit is further configured to: before receiving the third message from the first access network device through the communication unit, disconnect RRC connection between the terminal devices, and save the context information of the terminal device.
A private network subscription information update device, applied to a first access network device, or applied to a chip in the first access network device, characterized in that the device includes:

The communication unit is configured to send a third message to the second access network device, where the third message is used to request context information of the terminal device from the second access network device; and

Receive 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 obtain the context information, the fourth message carries indication information, and the indication information is used Indicating that the reason for the failure to obtain the context information is related to the private network subscription information;

A processing unit, configured to obtain the updated private network subscription information of the terminal device from the core network device;

The communication unit is further configured to send the private network subscription information to the terminal device.
The device according to claim 33, wherein the first indication information includes at least one of the following: invalid private network identifier; unsupported private network identifier; not within the scope of private network contract; unreasonable private network Access.
A private network contract information update device, characterized in that the device includes:

A processing unit, configured to determine that a first cell is not a subscribed cell of a terminal device, the first cell is the last cell that the terminal device provides service for the terminal device before the terminal device enters the inactive state, and the first cell is The cell of the second access network device;

The communication unit is configured to send a first message to the second access network device, where the first message is used to instruct the second access network device to release the context information of the terminal device.
The apparatus according to claim 35, wherein the first message carries first indication information, and the first indication information is used to indicate that the reason for releasing the context information is related to private network subscription information.
The device according to claim 35 or 36, wherein the communication unit is further configured to:

After sending the first message to the second access network device, receiving second information from the second access network device, where the second information is used to indicate that the terminal device is based on the notification area of the access network RNA information.
The device according to claim 37, wherein the communication unit is further configured to:

After receiving the second information from the second access network device, send a paging message within the RNA range indicated by the second information.
A private network subscription information update device, characterized in that the device includes a processor and a communication interface, the communication interface is used to receive computer program codes or instructions and transmit them to the processor; The computer program code or instructions are used to enable the device to implement the method according to any one of claims 1 to 5, and/or the method according to any one of claims 16 to 19.
A private network subscription information update device, characterized in that the device includes a processor and a communication interface, the communication interface is used to receive computer program codes or instructions and transmit them to the processor; The computer program code or instructions are used to enable the device to implement the method according to claims 6 to 9, and/or claims 10 to 13, and/or any one of claims 14 to 15.
A computer-readable storage medium, characterized in that a program is stored in the computer-readable storage medium, and when the program is read and executed by one or more processors, it can implement any one of claims 1-5 The method described, and/or, the method of any one of claims 16-19.
A computer-readable storage medium, characterized in that a program is stored in the computer-readable storage medium, and when the program is read and executed by one or more processors, it can implement claims 6 to 9, and/ Or, as claimed in claims 10 to 13, and/or as claimed in any one of claims 14 to 15.
A communication system, characterized by comprising: the device according to any one of claims 20-24, and/or the device according to any one of claims 25-28.
A communication system, characterized by comprising: the device according to any one of claims 29-32, and/or the device according to claim 33 or 34.
A communication system, characterized by comprising: the device according to any one of claims 35-38.
A communication system, characterized by comprising: the device as claimed in claim 39, and/or the device as claimed in claim 40.