A non-public network subscription information updating method and device

Abstract

This application discloses a method and apparatus for updating subscription information on a non-public network. The method includes: after receiving an RRC recovery request message from a terminal device, the access network device can send an RRC rejection message or an RRC release message to the terminal device, wherein the RRC rejection message or RRC release message includes new subscription information; or, the access network device can send an RRC recovery message to the terminal device, carrying indication information restricting the terminal device from transmitting non-access stratum (NAS) signaling and / or service data. This method allows the terminal device to update its subscription information promptly even when it fails the access network device's verification.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular to a method and apparatus for updating subscription information on a non-public network. Background Technology

[0002] Public network integrated non-public network (PNI-NPN) is a non-public network (NPN) that relies on the public land mobile network (PLMN). A non-public network is a network open to specific users, providing NPN services only within specific areas (such as industrial parks or schools) via NPN cells. Users can access NPN cells through terminal devices that support NPN services (e.g., NPN terminal devices). Typically, these terminal devices are configured with subscription information, i.e., user access agreements signed between the terminal device and the operator or other company building the non-public network. After signing the subscription, the terminal device can access the corresponding network and use its resources based on the network identifiers allowed in the subscription information. For example, for terminal devices supporting PNI-NPN services, the subscription information includes a list of allowed closed access groups (CAGs) and instructions indicating that access is only permitted via CAGs.

[0003] When the subscription information of a terminal device (e.g., the CAG list of allowed access mentioned above) changes (or is updated), the access and mobility management function (AMF) initiates a user equipment (UE) configuration update (UCU) procedure to notify the terminal device of the updated subscription information. For terminal devices in an inactive state, when the AMF triggers the UCU, it sends a downlink non-access stratum transmission message to the source base station of the terminal device. This downlink non-access stratum transmission message carries a non-access stratum-packet data unit (NAS-PDU) and a mobility restriction list (MRL). The NAS-PDU is sent by the AMF to the terminal device and is transparently transmitted to the terminal device by the source base station after receiving it. The MRL is sent by the AMF to the source base station. Both the NAS-PDU and the MRL carry the updated subscription information of the terminal device. The source base station is the last serving base station before the terminal device enters the inactive state from the connected state. For an inactive NPN terminal device, it needs to re-access the NPN cell to receive updated subscription information; that is, the terminal device must perform a radio resource control (RRC) recovery process. During this RRC recovery process, if the NPN terminal device accesses the source base station, the source base station may have already updated the corresponding terminal device's subscription information according to the MRL. There might be a mismatch between the updated subscription information and the NPN information supported by the source base station. Therefore, the source base station will refuse the terminal device's access. Consequently, the terminal device cannot receive updated subscription information by accessing the source base station's cell, resulting in its subscription information not being updated in a timely manner. Summary of the Invention

[0004] This application provides a method and apparatus for updating subscription information on a non-public network to solve the problem that terminal devices cannot update subscription information in a timely manner because they cannot pass the verification of access network devices.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] A first aspect of this application provides a method for updating subscription information on a non-public network. The method may include: a first access network device receiving an RRC recovery request message sent by a terminal device; the first access network device sending a first message to the terminal device, the first message including a first CAG information list, wherein the first CAG information list is the updated CAG information list of the terminal device, and the first message is an RRC rejection message or an RRC release message.

[0007] Based on the method in the first aspect, after the first access network device receives the RRC recovery request message sent by the terminal device, the first access network device can send a first message to the terminal device to refuse or release the terminal device's access to the first access network device, and carry the updated CAG information list of the terminal device in the first message, so that the terminal device can update the CAG information list according to the first message. This allows terminal devices that cannot be verified by the first access network device to update their CAG information list in a timely manner without entering the connected state.

[0008] In one possible design, the first message also includes a first cause value, which is used to instruct the terminal device to update the CAG information list.

[0009] Based on this possible design, the terminal device can easily update the CAG information list according to the determination of the received first cause value, thereby simplifying the system design.

[0010] In one possible design, the method further includes: a first access network device sending a second message to a terminal device, the second message instructing the terminal device to send an RRC recovery request message to the first access network device, the second message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list; the RRC recovery request message including the second cause value.

[0011] Based on this possible design, the first access network device can determine, according to the indication of the second cause value included in the received RRC recovery request message, that the purpose of the terminal device sending the RRC recovery request message is to update the CAG information list, and then send a first message to the terminal device so that the terminal device can update the CAG information list in a timely manner.

[0012] In one possible design, the method further includes: a first access network device receiving a third message sent by a core network device, the third message including a first CAG information list; the first access network device setting a first identifier, the first identifier being used to indicate that the CAG information list of the terminal device has not been updated.

[0013] Based on this possible design, the first access network device, upon receiving an RRC recovery request message, can determine, according to a set first identifier, that the terminal device's CAG information list has not been updated, and thus send a first message to the terminal device to ensure that the terminal device updates its CAG information list in a timely manner.

[0014] In one possible design, the method further includes: after the first access network device sends a first message to the terminal device, the first access network device deletes the first identifier.

[0015] Based on this possible design, deleting the first identifier after sending the first message can prevent the first access network device from resending the first message to the terminal device when the terminal device subsequently sends an RRC recovery request, thus avoiding repeated updates of the CAG information list by the terminal device. Specifically, the first access network device can delete the first identifier after confirming that the terminal device has received the first message.

[0016] In one possible design, the method further includes: a first access network device sending a fourth message to a second access network device, the fourth message being used to request the context of a terminal device; the first access network device receiving a fifth message sent by the second access network device, the fifth message including a first CAG information list and a first indication, the first indication being used to instruct the terminal device to update its CAG information list.

[0017] Based on this possible design, when the first access network device receiving the RRC recovery request message does not have the context of the terminal device (e.g., the updated CAG information of the terminal device) (for example, the first access network device could be another access network device near the terminal device's last serving access network device), the first access network device can request the context from the second access network device. After receiving the fourth message requesting the context, the second access network device can send the updated CAG information list of the terminal device (or the first CAG information list) to the first access network device via a fifth message. This facilitates the first access network device obtaining the updated CAG information list of the terminal device and sending it to the terminal device via a first message to update the terminal device's CAG information list.

[0018] In one possible design, the method further includes: a first access network device receiving a sixth message sent by a second access network device, the sixth message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list; the first access network device sending a second message to the terminal device, the second message being used to instruct the terminal device to send an RRC recovery request message to the first access network device, the second message including a second cause value; the RRC recovery request message including the second cause value.

[0019] In this way, the first access network device can determine that the terminal device has not updated the CAG information list based on the second cause value in the received RRC recovery request message, and then send a first message to the terminal device so that the terminal device can update the CAG information list.

[0020] In one possible design, the method further includes: the first access network device configuring at least one of preamble resources, time domain resources, and frequency domain resources dedicated to updating the CAG information list of the terminal device in a system message.

[0021] In this way, terminal devices can receive configured resources dedicated to updating their CAG information list via system messages, simplifying system design.

[0022] Secondly, a communication device is provided, which can be a first access network device or a chip or system-on-a-chip within the first access network device. This communication device can realize the functions performed by the first access network device in the first aspect or its possible designs. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include a receiving unit, a processing unit, and a transmitting unit.

[0023] The receiving unit can be used to receive RRC recovery request messages sent by the terminal device;

[0024] The sending unit can be used to send a first message to the terminal device. The first message includes a first CAG information list, wherein the first CAG information list is the updated CAG information list of the terminal device, and the first message is an RRC rejection message or an RRC release message.

[0025] In one possible design, the first message also includes a first cause value, which is used to instruct the terminal device to update the CAG information list.

[0026] In one possible design, the sending unit is further configured to send a second message to the terminal device, the second message instructing the terminal device to send an RRC recovery request message to the first access network device, the second message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list; the RRC recovery request message includes the second cause value.

[0027] In one possible design, the receiving unit is further configured to receive a third message sent by the core network device, the third message including a first CAG information list; the processing unit is configured to set a first identifier, the first identifier being used to indicate that the CAG information list of the terminal device has not been updated.

[0028] In one possible design, after sending the first message to the terminal device, the processing unit is also used to delete the first identifier.

[0029] In one possible design, the sending unit is further configured to send a fourth message to the second access network device, the fourth message being used to request the context of the terminal device; the receiving unit is further configured to receive a fifth message sent by the second access network device, the fifth message including a first CAG information list and a first indication, the first indication being used to instruct the terminal device to update the CAG information list.

[0030] In one possible design, the receiving unit is further configured to receive a sixth message sent by the second access network device, the sixth message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list; the sending unit is further configured to send a second message to the terminal device, the second message being used to instruct the terminal device to send an RRC recovery request message to the first access network device, the second message including a second cause value; the RRC recovery request message including the second cause value.

[0031] In one possible design, the processing unit is also configured in a system message to configure at least one of the preamble resources, time-domain resources, and frequency-domain resources of the terminal device specifically for updating the CAG information list.

[0032] Thirdly, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer execution instructions, and when the communication device is in operation, the processor executes the computer execution instructions stored in the memory to cause the communication device to perform the non-public network subscription information update method as described in the first aspect or any possible design of the first aspect.

[0033] Fourthly, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, enable the computer to perform the non-public network subscription information update method described in the first aspect or any possible design of the above aspects.

[0034] Fifthly, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to execute the non-public network subscription information update method described in the first aspect or any possible design of the first aspect.

[0035] Sixthly, a communication device is provided. This communication device can be a system-on-a-chip (SoC), which may include a processor and a transceiver, for supporting the communication device in implementing the functions involved in the first aspect or any possible design of the first aspect. In one possible design, the SoC further includes a memory for storing necessary program instructions and data for the communication device. The SoC may be composed of chips or may include chips and other discrete devices.

[0036] The technical effects of any of the design methods in aspects two through six can be found in the first aspect or any possible design of the first aspect, and will not be repeated here.

[0037] In a seventh aspect, another method for updating subscription information on a non-public network is provided. This method may include: a second access network device receiving a fourth message sent by a first access network device, the fourth message being used to request the context of a terminal device; the second access network device sending a fifth message to the first access network device, the fifth message including a first CAG information list and a first indication, the first CAG information list being the updated CAG information list of the terminal device, and the first indication being used to indicate that the CAG information list of the terminal device is updated.

[0038] Based on the method of the seventh aspect, when the first access network device that receives the RRC recovery request message does not have the context of the terminal device (e.g., the updated CAG information of the terminal device) (e.g., the first access network device could be another access network device near the terminal device's last serving access network device), the first access network device can request the context from the second access network device. After receiving the fourth message requesting the context, the second access network device can send the updated CAG information list of the terminal device (or the first CAG information list) to the first access network device via a fifth message. This facilitates the first access network device in obtaining the updated CAG information list of the terminal device and determining, according to the first instruction, that the terminal device needs to update its CAG information list. Then, by sending the first message, the second access network device sends the updated CAG information list of the terminal device to the terminal device to enable the terminal device to update its CAG information list.

[0039] In one possible design, the method further includes: the second access network device sending a sixth message to the first access network device, the sixth message being used to instruct the first access network device to send a second message, the sixth message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list.

[0040] Based on this possible design, the first access network device can determine whether the terminal device needs to update the CAG information according to the second cause value, thus simplifying the system design.

[0041] Eighthly, a communication device is provided, which can be a second access network device or a chip or system-on-a-chip within the second access network device. This communication device can implement the functions performed by the second access network device in the seventh aspect or possible designs of the seventh aspect. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include a receiving unit and a transmitting unit, etc.

[0042] The receiving unit can be used to receive a fourth message sent by the first access network device, the fourth message being used to request the context of the terminal device;

[0043] The sending unit can be used to send a fifth message to the first access network device. The fifth message includes a first CAG information list and a first indication. The first indication is used to instruct the terminal device to update the CAG information list.

[0044] In one possible design, the sending unit is further configured to send a sixth message to the first access network device, the sixth message being used to instruct the first access network device to send a second message, the sixth message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list.

[0045] A ninth aspect provides a communication device, comprising: a processor and a memory; the memory being used to store computer-executable instructions, wherein when the communication device is in operation, the processor executes the computer-executable instructions stored in the memory to cause the communication device to perform the non-public network subscription information update method as described in the seventh aspect or any possible design of the seventh aspect.

[0046] In a tenth aspect, a computer-readable storage medium is provided, which stores instructions that, when executed on a computer, enable the computer to perform the non-public network subscription information update method described in the seventh aspect or any possible design of the seventh aspect.

[0047] In the eleventh aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to execute the non-public network subscription information update method described in the seventh aspect or any possible design of the seventh aspect.

[0048] In a twelfth aspect, a communication device is provided. This communication device can be a system-on-a-chip (SoC), which may include a processor and a transceiver for supporting the communication device in implementing the functions involved in the seventh aspect or any possible design of the seventh aspect. In one possible design, the SoC further includes a memory for storing necessary program instructions and data for the communication device. The SoC may be composed of chips or may include chips and other discrete devices.

[0049] The technical effects of any of the design methods in aspects eight through twelfth are similar to those in aspect seven or any possible design in aspect seven, and will not be repeated here.

[0050] In a thirteenth aspect, a method for updating subscription information on a non-public network is also provided. The method may include: a terminal device sending an RRC recovery request message to a first access network device; the terminal device receiving a first message from the first access network device, the first message being an RRC rejection message or an RRC release message; the first message including a first CAG information list, wherein the first CAG information list is the updated CAG information list of the terminal device.

[0051] Based on the method in aspect thirteen, when the terminal device sends an RRC recovery request message to the first access network device, the first access network device can reject or release the terminal device's access through a first message, and carry the updated CAG information list of the terminal device in the first message. Upon receiving the first message, the terminal device can update its CAG information list. This allows the terminal device to update its CAG information without entering the connected state, and enables timely updates of its CAG information even when the terminal device fails to pass the authentication of the first access network device.

[0052] In one possible design, the first message also includes a first cause value, which is used to instruct the terminal device to update the CAG information list.

[0053] Based on this possible design, the terminal device can determine the need to update the CAG information list according to the first cause value, and then update the CAG information list, simplifying the system design.

[0054] In one possible design, the method further includes: the terminal device receiving a second message sent by the first access network device, the second message being used to instruct the terminal device to send an RRC recovery request message to the first access network device, the second message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list; the RRC recovery request message including the second cause value.

[0055] Based on this possible design, the first access network device can determine, according to the indication of the second cause value included in the received RRC recovery request message, that the purpose of the terminal device sending the RRC recovery request message is to update the CAG information list, and then send a first message to the terminal device so that the terminal device can update the CAG information list in a timely manner.

[0056] In a fourteenth aspect, a communication device is provided, which can be a terminal device or a chip or system-on-a-chip within a terminal device. This communication device can implement the functions performed by the terminal device in the thirteenth aspect or possible designs of the thirteenth aspect, wherein the functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include a receiving unit and a transmitting unit, etc.

[0057] The sending unit is used to send an RRC recovery request message to the first access network device;

[0058] The receiving unit is configured to receive a first message from the first access network device, wherein the first message is an RRC rejection message or an RRC release message; the first message includes a first CAG information list, wherein the first CAG information list is the updated CAG information list of the terminal device.

[0059] In one possible design, the first message also includes a first cause value, which is used to instruct the terminal device to update the CAG information list.

[0060] In one possible design, the receiving unit is further configured to receive a second message sent by the first access network device. The second message is used to instruct the terminal device to send an RRC recovery request message to the first access network device. The second message includes a second cause value, which is used to instruct the terminal device to update its CAG information list. The RRC recovery request message includes the second cause value.

[0061] In a fifteenth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer-executable instructions, wherein when the communication device is in operation, the processor executes the computer-executable instructions stored in the memory to cause the communication device to perform a non-public network subscription information update method as described in the thirteenth aspect or any possible design of the thirteenth aspect.

[0062] In a sixteenth aspect, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, enable the computer to perform the non-public network subscription information update method described in the thirteenth aspect or any possible design of the thirteenth aspect.

[0063] In a seventeenth aspect, a computer program product containing instructions is provided that, when run on a computer, enables the computer to execute the non-public network subscription information update method described in the thirteenth aspect or any possible design of the thirteenth aspect.

[0064] In an eighteenth aspect, a communication device is provided. This communication device can be a system-on-a-chip (SoC), which may include a processor and a transceiver for supporting the communication device in implementing the functions involved in the thirteenth aspect or any possible design of the thirteenth aspect. In one possible design, the SoC further includes a memory for storing necessary program instructions and data for the communication device. The SoC may be composed of chips or may include chips and other discrete devices.

[0065] The technical effects of any of the design methods in aspects fourteen through eighteen can be found in aspect thirteen or any possible design in aspect thirteen, and will not be repeated here.

[0066] In a nineteenth aspect, a method for updating subscription information on a non-public network is also provided. The method may include: a first access network device receiving a Radio Resource Control (RRC) recovery request message sent by a terminal device; the first access network device sending an RRC recovery message to the terminal device, the RRC recovery message including a second indication, the second indication being used to restrict the terminal device from transmitting NAS signaling and / or service data.

[0067] Based on the method of the nineteenth aspect, after the first access network device receives the RRC recovery request message, it can instruct the terminal device to connect to the first access network device under restricted transmission of NAS signaling and / or service data via a second instruction. This enables the terminal device to obtain a NAS-PDU message containing an updated CAG information list sent by the core network device from the first access network device, thereby updating the CAG information list. In this way, even if the terminal device fails to pass the authentication of the first access network device, it can still establish a temporary connection with the first access network device with restricted transmission to receive NAS-PDUs and update the CAG information list.

[0068] In one possible design, the method further includes, after receiving the RRC recovery completion message from the terminal device, the first access network device sends a NAS-PDU to the terminal device, the NAS-PDU being used by the terminal device to update the terminal device's CAG information list.

[0069] In one possible design, the method further includes: the first access network device sending an RRC release message to the terminal device.

[0070] In a twentieth aspect, a communication device is provided, which can be a first access network device or a chip or system-on-a-chip within the first access network device. This communication device can implement the functions performed by the first access network device in the nineteenth aspect or possible designs of the nineteenth aspect. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include a receiving unit and a transmitting unit, etc.

[0071] The receiving unit can be used to receive RRC recovery request messages sent by the terminal device;

[0072] The sending unit can be used to send an RRC recovery message to the terminal device. The RRC recovery message includes a second indication, which is used to restrict the terminal device from transmitting NAS signaling and / or service data.

[0073] The specific implementation of the communication device can refer to the behavior function of the first access network device in the non-public network subscription information update method provided by the nineteenth aspect or any possible design of the nineteenth aspect. The nineteenth aspect or any possible design method of the nineteenth aspect can be implemented by the receiving unit and the sending unit included in the communication device, which will not be elaborated here.

[0074] In a twenty-first aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer execution instructions, wherein when the communication device is in operation, the processor executes the computer execution instructions stored in the memory to cause the communication device to perform the non-public network subscription information update method as described in the nineteenth aspect or any possible design of the nineteenth aspect.

[0075] In a twenty-second aspect, a computer-readable storage medium is provided, which stores instructions that, when executed on a computer, enable the computer to perform the non-public network subscription information update method described in the nineteenth aspect or any possible design of the nineteenth aspect.

[0076] In a twentieth aspect, a computer program product containing instructions is provided that, when run on a computer, enables the computer to execute the non-public network subscription information update method described in the nineteenth aspect or any possible design of the nineteenth aspect.

[0077] In a twenty-fourth aspect, a communication device is provided. This communication device can be a system-on-a-chip (SoC), which may include a processor and a transceiver for supporting the communication device in implementing the functions involved in the nineteenth aspect or any possible design of the nineteenth aspect. In one possible design, the SoC further includes a memory for storing necessary program instructions and data for the communication device. The SoC may be composed of chips or may include chips and other discrete devices.

[0078] The technical effects of any of the design methods in aspects 20 to 24 can be found in aspect 19 or any possible design in aspect 19, and will not be repeated here.

[0079] In a twentieth aspect, a method for updating subscription information on a non-public network is also provided. The method may include: a terminal device sending an RRC recovery request message to a first access network device; the terminal device receiving an RRC recovery message sent by the first access network device, wherein the RRC recovery message includes a second indication, the second indication being used to restrict the terminal device from transmitting NAS signaling and / or service data.

[0080] Based on the method of aspect twenty-five, after receiving the RRC recovery request message, the first access network device can, through a second instruction, instruct the terminal device to connect to the first access network device under restricted transmission of NAS signaling and / or service data. This enables the terminal device to obtain a NAS-PDU message containing an updated CAG information list sent by the core network device from the first access network device, thereby updating the CAG information list. In this way, even if the terminal device fails to pass the authentication of the first access network device, it can still establish a temporary connection with the first access network device with restricted transmission to receive NAS-PDUs and update the CAG information list.

[0081] In one possible design, the method further includes: the terminal device sending an RRC recovery completion message to the first access network device; the terminal device receiving a NAS-PDU from the first access network device, the NAS-PDU being used by the terminal device to update the terminal device's CAG information list.

[0082] In one possible design, the method further includes: the terminal device receiving an RRC release message sent by the first access network device.

[0083] In a twenty-sixth aspect, a communication device is provided, which can be a first access network device or a chip or system-on-a-chip within the first access network device. This communication device can implement the functions performed by the first access network device in the twenty-fifth aspect or possible designs of the twenty-fifth aspect. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include a receiving unit and a transmitting unit, etc.

[0084] The sending unit can be used to send an RRC recovery request message to the first access network device;

[0085] The receiving unit can be used to receive an RRC recovery message sent by the first access network device. The RRC recovery message includes a second indication, which is used to restrict the terminal device from transmitting NAS signaling and / or service data.

[0086] The specific implementation of the communication device can refer to the behavior function of the first access network device in the non-public network subscription information update method provided by aspect 25 or any possible design of aspect 25. aspect 25 or any possible design method of aspect 25 can be implemented by the receiving unit and the sending unit included in the communication device, which will not be elaborated here.

[0087] A twenty-seventh aspect provides a communication device, comprising: a processor and a memory; the memory being used to store computer execution instructions, wherein when the communication device is in operation, the processor executes the computer execution instructions stored in the memory to cause the communication device to perform the non-public network subscription information update method as described in the twenty-fifth aspect or any possible design of the twenty-fifth aspect.

[0088] In a twentieth aspect, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, enable the computer to perform the non-public network subscription information update method described in the twentieth aspect or any possible design of the twentieth aspect.

[0089] In a twentieth aspect, a computer program product containing instructions is provided that, when run on a computer, enables the computer to execute the non-public network subscription information update method described in the twentieth aspect or any possible design of the twentieth aspect.

[0090] In a thirtieth aspect, a communication device is provided. This communication device can be a system-on-a-chip (SoC), which may include a processor and a transceiver for supporting the communication device in implementing the functions involved in the twenty-fifth aspect or any possible design of the twenty-fifth aspect. In one possible design, the SoC further includes a memory for storing necessary program instructions and data for the communication device. The SoC may be composed of chips or may include chips and other discrete devices.

[0091] The technical effects of any of the design methods in aspects 26 to 30 can be found in aspect 25 or any possible design in aspect 25, and will not be repeated here.

[0092] In a thirty-first aspect, a communication system is provided, which may include a communication device or chip system as described in any one of the second to sixth aspects, a communication device or chip system as described in any one of the eighth to twelfth aspects, and a communication device or chip system as described in any one of the fourteenth to eighteenth aspects; or,

[0093] The communication system may include the communication device or chip system described in any one of the 20th to 24th aspects, and the communication device or chip system described in any one of the 26th to 30th aspects. Attached Figure Description

[0094] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0095] Figure 2 A flowchart illustrating a method for updating non-public network contract information provided in this application embodiment;

[0096] Figure 3 A flowchart illustrating another method for updating non-public network contract information provided in this application embodiment;

[0097] Figure 4 A flowchart illustrating another method for updating non-public network contract information provided in this application embodiment;

[0098] Figure 5 A flowchart illustrating another method for updating non-public network contract information provided in this application embodiment;

[0099] Figure 6 A flowchart illustrating another method for updating non-public network contract information provided in this application embodiment;

[0100] Figure 7A flowchart illustrating another method for updating non-public network contract information provided in this application embodiment;

[0101] Figure 8 A flowchart illustrating another method for updating non-public network contract information provided in this application embodiment;

[0102] Figure 9 This is a schematic diagram of the composition of a communication device provided in an embodiment of this application;

[0103] Figure 10 A schematic diagram illustrating the composition of another communication device provided in an embodiment of this application;

[0104] Figure 11 A schematic diagram illustrating the composition of another communication device provided in an embodiment of this application;

[0105] Figure 12 This is a schematic diagram illustrating the composition of another communication device provided in an embodiment of this application. Detailed Implementation

[0106] In a non-public network integrated with a public network, users can access the non-public network cell through terminal devices that support non-public network services. These terminal devices typically have subscription information configured. This subscription information may be user access information signed between the terminal device and an operator or other company building the non-public network. For example, the subscription information may include an allowed closed access group list (Allowed CAG list) and an indication that the terminal device is only allowed to access through a closed access group (CAG-only indication). After the terminal device subscribes, it can access the corresponding network based on the network identifiers allowed in the configured subscription information. Taking a subscription information including an allowed closed access group list as an example, the terminal device can access the access network device that supports the closed access group corresponding to that closed access group identifier based on the closed access group identifier in the allowed closed access group list. The access network device may be configured with its supported closed access group list, or it may obtain the allowed closed access group list from the core network device or the terminal device. When a terminal device needs to access an access network device, it can send an access request. Upon receiving the request, the access network device verifies the terminal device based on its supported closed access group list and the list of allowed closed access groups. For example, if the supported and allowed closed access group lists contain the same closed access group identifier (e.g., the first closed access group identifier), the access network device verifies the terminal device. The terminal device can then connect to the access network device through the first closed access group corresponding to the first closed access group identifier. Similarly, if the supported and allowed closed access group lists do not contain the same closed access group identifier, the access network device fails to verify the terminal device and may refuse access.

[0107] When the subscription information of a terminal device, such as the list of closed access groups allowed for the terminal device's access in the subscription information, changes, the access management function network element will initiate a configuration update for the user equipment to notify the terminal device of the updated subscription information. For example, the access management function network element sends a downlink non-access stratum transmission message to the access network device, carrying a NAS-PDU containing the updated list of closed access groups allowed for the terminal device's access. The access network device then transparently transmits the NAS-PDU to the terminal device via downlink information transfer (DL Information Transfer). For terminal devices in a non-connected state (e.g., inactive state), in order to send the NAS-PDU to the terminal device, the access network device will send a paging message to the terminal device within the access network's notification area. When the terminal device hears the paging message, it checks whether the paging message contains its own identifier. If it does, the terminal device can send an RRC recovery request message to the access network device to restore the connected state. After the terminal device restores the connected state, the access network device can send the NAS-PDU to the terminal device to allow the terminal device to update its subscription information. In addition, the access management function network element will also send a mobility restriction list to the access network equipment. This mobility restriction list contains the updated list of closed access groups that the terminal equipment is allowed to access, so as to update the subscription information of the corresponding terminal equipment stored in the access network equipment (e.g., the list of closed access groups that the terminal equipment is allowed to access).

[0108] As can be seen, if the updated list of closed access groups allowed for terminal device access by the terminal device does not have the same closed access group identifier as the list of closed access groups supported by the access network device, the terminal device will be unable to restore the connected state because it cannot pass the verification of the access network device. This causes the terminal device to be unable to receive NAS-PDU from the access network device, thus preventing the terminal device from updating the list of closed access groups allowed for terminal device access (or subscription information) in a timely manner.

[0109] To address the aforementioned issues, this application provides a method for updating subscription information in a non-public network. This method may include: after an access network device (e.g., a first access network device) receives an RRC recovery request message from a terminal device, and the access network device determines that the terminal device has not yet updated its subscription information (e.g., a list of closed access groups allowed for the terminal device's access), and the access verification of the terminal device fails based on the updated subscription information (or new subscription information), the access network device may send an RRC rejection message or an RRC release message to the terminal device. The RRC rejection message or RRC release message includes the new subscription information, allowing the terminal device to update its subscription information by receiving the RRC rejection message or RRC release message. Alternatively, the access network device may send an RRC recovery message to the terminal device, carrying indication information restricting the terminal device's transmission of non-access stratum (NAS) signaling and / or service data. This allows the terminal device to restore its connection state while restricting the transmission of NAS signaling and / or service data, enabling the terminal device to receive a NAS-PDU containing the new subscription information from the access network device, thus allowing the terminal device to update its subscription information.

[0110] This method updates the subscription information of terminal devices, enabling them to update their subscription information promptly even when they fail to pass the verification process of the access network devices.

[0111] The following description, in conjunction with the accompanying drawings, provides an exemplary illustration of the method for updating non-public network contract information provided in this application.

[0112] It should be noted that in the description of this application, the words "first" and "second" are merely for distinguishing descriptions and are not used to specifically limit any feature. In the description of the embodiments of this application, "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the related objects before and after it are in an "or" relationship. In this application, "at least one" refers to one or more; "multiple" refers to two or more.

[0113] The non-public network subscription information update method provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, Wireless Fidelity (WiFi) systems, future communication systems, or systems integrating multiple communication systems, etc., and this application does not limit the application. 5G can also be referred to as New Radio (NR).

[0114] The non-public network subscription information update method provided in this application embodiment can be applied to various communication scenarios, such as one or more of the following communication scenarios: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), machine type communication (MTC), massive machine type communications (mMTC), device to device (D2D), vehicle to everything (V2X), vehicle to vehicle (V2V), and Internet of Things (IoT).

[0115] Figure 1 A schematic diagram of a communication system provided in an embodiment of this application is shown. Figure 1 As shown, the communication system may include: access network equipment 110 and core network equipment 120.

[0116] The access network device 110 can also be referred to as a next-generation access network device. Terminal devices can communicate with core network device 120 through the access network device 110. The access network device 110 can provide terminal devices with functions and services such as radio resource management, quality of service management, data encryption and compression.

[0117] Access network device 110 and core network device 120 can communicate through the next generation (NG) interface, and different access network devices 110 can communicate with each other through the Xn interface.

[0118] Optionally, the terminal equipment can be user equipment (UE), mobile station (MS), or mobile terminal (MT), etc. Specifically, terminal device 110 can be a mobile phone ("cellular"), cell phone, computer, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), laptop computer, handheld communication device, handheld computing device, satellite wireless device, wireless modem card, set-top box (STB), customer premises equipment (CPE), wearable device (e.g., smartwatch, smart bracelet, pedometer, etc.), vehicle-mounted equipment (e.g., car, bicycle, electric vehicle, airplane, ship, train, high-speed rail, etc.), virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, smart home device (e.g., refrigerator, television, air conditioner, electricity meter, etc.), intelligent robot, workshop equipment, wireless terminal in self-driving, remote medical... Wireless terminals in various fields, including those for surgery, smart grids, transportation safety, smart cities, or smart homes, as well as flying devices (e.g., intelligent robots, hot air balloons, drones, airplanes) and other devices used for communication over wireless systems, are not limited to any specific form of terminal equipment in this application.

[0119] In some embodiments, the access network device 110 may be a next-generation node B (gNB), a next-generation evolved node B (ng-eNB), a central unit (CU), a distributed unit (DU), a central unit-control plane (CU-CP), a central unit-user plane (CU-UP), etc.

[0120] The gNB provides terminal devices with control plane and / or user plane protocols and functions for new radio (NR) and accesses the 5G core network (5GC). The ng-eNB provides terminal devices with control plane and / or user plane protocols and functions for evolved universal terrestrial radio access (E-UTRA) and accesses the 5GC. The CU mainly includes the gNB's RRC layer, service data adaptation protocol (SDAP) layer, and packet data convergence protocol (PDCP) layer, or the ng-eNB's RRC layer and PDCP layer. The DU mainly includes the gNB or ng-eNB's radio link control (RLC) layer, medium access control (MAC) layer, and physical layer. The CU-CP mainly includes the RRC layer in the gNB-CU or ng-eNB-CU, and the control plane in the PDCP layer. CU-UP mainly includes the SDAP layer in gNB-CU or ng-eNB-CU, and the user plane in the PDCP layer.

[0121] In some embodiments, the core network device 120 may include a session management function (SMF), an AMF, a network data analytics function (NWDAF), a user plane function (UPF), etc.

[0122] The SMF (Service Message Function) is primarily responsible for session management (e.g., session establishment, modification, and release), UE IP address allocation and management, user plane function selection and control, and terminating the session management portion of NAS messages. The AMF (Access Message Function) is primarily responsible for access control, mobility management, attach and detach, and gateway selection. The NWDAF (Network Window Message Function) is primarily responsible for data collection and analysis. The UPF (User Message Provider Function) is primarily responsible for packet routing and forwarding.

[0123] It should be noted that the aforementioned SMF, AMF, NWDAF, UPF, etc. are merely illustrative examples of the core network equipment 120, and this application does not impose any limitations on them.

[0124] Understandably, the aforementioned Figure 1 The communication system shown is merely for illustrating the technical solutions of the embodiments of this application more clearly and does not constitute a limitation on the technical solutions provided in the embodiments of this application. For example, the communication system may also include other devices, such as network control devices. The network control device may be an operation administration and maintenance (OAM) system, also known as a network management system. The network control device can manage the aforementioned access network device 110 and core network device 120.

[0125] Furthermore, as those skilled in the art will recognize, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0126] Taking the update of the list of closed access groups (or CAG information list of terminal devices) that are allowed to be accessed by terminal devices in the contract information as an example. The CAG information list of terminal devices can include the identifiers of the closed access groups that are allowed to be accessed by the terminal devices. Figure 2 This illustration shows a flowchart of a method for updating non-public network subscription information according to an embodiment of this application. Figure 2 As shown, the non-public network contract information update method may include the following S201-S204.

[0127] S201. The access network device (such as the first access network device) sends a second message to the terminal device, instructing the terminal device to send an RRC recovery request message to the access network device. That is, the second message is used to page the terminal device.

[0128] For example, the second message may be a paging message sent by the access network device to the terminal device to page the terminal device, so that the terminal device, upon receiving the paging message, sends an RRC recovery request message to the access network device.

[0129] In this context, the access network device can be the last serving access network device (or last serving base station) for the terminal device when it transitions from a connected state to an inactive state. The terminal device can transition from a connected state to an inactive state through an RRC release process. The last serving access network device retains the terminal device's transmission parameters, allowing the terminal device to perform uplink and / or downlink transmissions with it based on these parameters. The access network device can also be other access network devices located near the last serving access network device, such as other access network devices within its notification area.

[0130] When the access network device is the last serving access network device, it can determine that the terminal device needs to update its CAG information list based on a message (such as the third message) received from the core network device (e.g., an AMF element) containing the updated CAG information list of the terminal device, and thus send the aforementioned second message to the terminal device. The message containing the updated CAG information list of the terminal device sent by the core network device can be a mobility restriction list (MRL) used by the core network device to update the subscription information of the access network device.

[0131] When an access network device is another access network device near the last serving access network device, the access network device can send the aforementioned second message to the terminal device based on a message (such as the sixth message) sent by the last serving access network device instructing it to send a second message to the terminal device. For example, the sixth message can be a radio access network (RAN) paging message. The last serving access network device can, after receiving a message from a core network device (such as the aforementioned third message), send an RAN paging message to instruct access network devices near the last serving access network device to send the aforementioned second message to the terminal device.

[0132] S202. The terminal device sends an RRC recovery request message to the access network device.

[0133] Upon receiving the second message from the access network device, the terminal device can send an RRC recovery request message to the access network device to request a connection. For example, if the second message is a paging message, the access network device sends a paging message within its range. If a terminal device that detects the paging message determines that the paging message contains its own identifier, it will send an RRC recovery request message to the access network device.

[0134] S203. When the terminal device needs to update the CAG information list, the access network device sends the first message to the terminal device.

[0135] The first message may include the updated CAG information list of the terminal device (or the first CAG information list). The first message may be an RRC rejection message or an RRC release message sent by the access network device to the terminal device.

[0136] In some possible implementations, the first message may also include a cause value (such as a first cause value), which can be used to instruct the terminal device to update the CAG information list. For example, the first cause value could be "UEsubscription update". This allows the terminal device to update the CAG information list according to the instruction of the first cause value after receiving the first message.

[0137] When an access network device receives an RRC recovery request message from a terminal device, the access network device can authenticate the terminal device. For example, the access network device authenticates the terminal device based on the terminal device's CAG information list and a list of CAG information supported by the access network device (e.g., a list of identifiers for CAGs supported by the access network device). Since the access network device has updated its configured subscription information based on the MRL sent by the core network device, the aforementioned CAG information list of the terminal device can be the updated CAG information list of the terminal device (i.e., the first CAG information list). If the terminal device's CAG information list and the list of CAG information supported by the core network device do not contain the same CAG identifier, the access network device fails to authenticate the terminal device. If the terminal device's CAG information list and the list of CAG information supported by the core network device contain the same CAG identifier, the access network device successfully authenticates the terminal device.

[0138] In some possible implementations, if the access network device fails to authenticate the terminal device, it can reject or release the terminal device's access by sending a first message. The first message carries an updated CAG information list for the terminal device, allowing the terminal device to update its CAG information list based on the first message.

[0139] In other possible implementations, even if the access network device allows the terminal device to access the network after successful authentication, it may still reject or release the terminal device's access by sending a first message. This first message carries the updated CAG information list of the terminal device, allowing the terminal device to update its CAG information list based on the first message. This allows the terminal device to update its CAG information list directly without entering a connected state, improving the efficiency of CAG information list updates.

[0140] In this embodiment of the application, before sending the first message, the access network device may first determine whether the terminal device needs to update the CAG information list. For example, the access network device may determine whether the terminal device needs to update the CAG information list in the following possible ways.

[0141] In one possible approach, the access network device is the last-serving access network device, which can receive messages (such as a third message) from core network devices (such as AMF network elements). These messages contain an updated CAG information list for the terminal devices. The access network device can update its own stored subscription information for the terminal devices based on this third message (e.g., storing the updated CAG information list for the terminal devices). The access network device can also store the subscription information for the terminal devices before the update (e.g., storing the CAG information list for the terminal devices before the update), meaning the access network device stores two sets of subscription information for the terminal devices. If the access network device can successfully verify the terminal device using the CAG information list before the update, but fails to verify it using the updated CAG information list, the access network device can determine that the terminal device needs to update its CAG information list.

[0142] In another possible approach, the access network device is the last-serving access network device, which can receive messages (such as a third message) from core network devices (such as AMF network elements) containing an updated CAG information list of terminal devices. The access network device can update its own stored subscription information for terminal devices based on this third message; that is, the access network device only stores the latest subscription information for terminal devices. The access network device can also configure an identifier (such as a first identifier) ​​to indicate that the CAG information list of terminal devices has not been updated based on the received third message. Upon receiving an RRC recovery request message from a terminal device, the access network device can determine that the terminal device needs to update its CAG information list based on this first identifier.

[0143] In another possible approach, the access network device is the last-serving access network device, which can receive messages (such as a third message) from core network devices (such as AMF network elements) containing the updated CAG information list of the terminal devices. The access network device can update its stored subscription information for the terminal devices based on this third message. Subsequently, the access network device can send a second message (such as a paging message) to the terminal devices, instructing them to send an RRC recovery request message. This second message carries a cause value (such as a second cause value), which can be used to instruct the terminal devices to update their CAG information list. Because the second message carries the second cause value, subsequent RRC recovery request messages sent by the terminal devices based on the second message can also carry this second cause value. Therefore, when the access network device receives an RRC recovery request message, it can determine that the terminal devices need to update their CAG information list based on the indication of the second cause value.

[0144] In another possible approach, the access network device is another access network device near the last serving access network device, which can receive messages (e.g., a fifth message) from the last serving access network device. This fifth message can be a terminal device context request response message or a terminal device context request failure message, etc. The fifth message may include an updated CAG information list for the terminal device, and a first indication that can be used to instruct the terminal device to update its CAG information list. Upon receiving the fifth message, the access network device can determine that the terminal device needs to update its CAG information list based on the first indication therein. Optionally, before receiving the fifth message, the access network device may also send a message (e.g., a fourth message) to the last serving access network device to request the terminal device's context, without limitation.

[0145] S204. The terminal device updates its CAG information list based on the first message received.

[0146] In some possible implementations, after updating the CAG information list, the terminal device can enter an idle state to select a suitable cell for access based on the updated CAG information list of the terminal device.

[0147] In some possible implementations, the access network device (such as the first access network device) may also configure at least one of the preamble resources, time domain resources and frequency domain resources of the terminal device in the system message for updating the CAG information list. This is not limited in the embodiments of this application.

[0148] based on Figure 2The method described allows the access network device to update its CAG information list even when it is inactive and cannot connect to the access network device due to failure to pass authentication. This is achieved by sending an updated CAG information list to the terminal device along with an RRC rejection message or RRC release message.

[0149] The following will combine Figure 3 Taking the terminal device as the UE, the access network device as the last serving base station, the core network device as the AMF network element, and the terminal device in an inactive state, where the updated UE's CAG information list (or the first CAG information list) and the access network device's supported CAG information list (or the second CAG information list) do not have the same CAG identifier as an example, the following is an example: Figure 2 The method shown will be explained in detail.

[0150] Figure 3 This is a flowchart illustrating another method for updating non-public network subscription information provided in an embodiment of this application. Figure 3 As shown, the non-public network contract information update method may include the following S301-S307.

[0151] S301, the AMF network element sends an MRL to the last serving base station, which includes the updated CAG information list of the UE.

[0152] The MRL sent by the AMF network element to the last serving base station can be used by the last serving base station to update the subscription information of terminal devices it stores, such as updating the CAG information list of terminal devices (e.g., UEs) stored in the last serving base station. Therefore, the MRL includes the updated CAG information list of the UE. When the last serving base station receives the MRL, it can save the updated CAG information of the UE so that the last serving base station can subsequently determine whether the UE needs to update its CAG information list based on the saved CAG information and the CAG information before the update.

[0153] S302. After receiving the MRL, the last serving base station saves the updated list of UE CAG information in the MRL, as well as the list of UE CAG information before the update.

[0154] S303, The last serving base station sends a paging message to the UE.

[0155] This S303 can be referenced. Figure 2 The explanation of S201 in the method shown will not be repeated here.

[0156] S304. After receiving the paging message, the UE sends an RRC recovery request message to the last serving base station.

[0157] When the UE detects a paging message, it can check if there is a corresponding identifier in the paging message. If there is, the UE can send an RRC recovery request message to the last serving base station to request a connection with the last serving base station.

[0158] S305. The last serving base station verifies the UE.

[0159] When the last serving base station receives the RRC recovery request message, it can verify the UE to determine whether to allow the UE to access the network and whether the UE needs to update its CAG information list. If the updated UE's CAG information list does not have the same CAG identifier as the CAG information list supported by the last serving base station (i.e., the last serving base station and the updated UE's CAG information list are incompatible, or the UE verification fails), then the last serving base station will not allow the UE to access the network. If, at this time, the CAG information list before the update has the same CAG identifier as the CAG information list supported by the last serving base station (i.e., the last serving base station and the CAG information list before the update are compatible), then the last serving base station can determine that the UE needs to update its CAG information list.

[0160] S306. After the UE verification fails, the last serving base station sends an RRC rejection message or an RRC release message to the UE.

[0161] If the last serving base station determines that the UE needs to update its CAG information list, the updated UE's CAG information list can be carried in the RRC rejection message or RRC release message.

[0162] Optionally, the RRC rejection message or RRC release message may also carry the cause value "UE subscription information update" to instruct the UE to update the CAG information list so that the UE can subsequently update the CAG information list according to the cause value.

[0163] S307. The UE updates the CAG information list based on the received RRC rejection message or RRC release message.

[0164] The S307 can be referenced. Figure 2 The explanation of S204 in the method shown will not be repeated here.

[0165] based on Figure 3The method described above allows the UE to update its CAG information list when it is inactive and fails verification by the last serving base station. The last serving base station can determine this by comparing the updated and unupdated CAG information lists of the UE. Therefore, when access is denied, the updated CAG information list is included in the RRC rejection or RRC release message sent to the UE, enabling the UE to update its CAG information list. This ensures that inactive UEs can update their CAG information lists promptly.

[0166] The following will combine Figure 4 Continuing with the example of the terminal device as the UE, the access network device as the last serving base station, the core network device as the AMF network element, the terminal device being inactive, and the updated UE's CAG information list (or first CAG information list) and the access network device's supported CAG information list (or second CAG information list) not having the same CAG identifier, the following steps are taken: Figure 2 The method shown will be explained in detail.

[0167] Figure 4 This is a flowchart illustrating another method for updating non-public network subscription information provided in an embodiment of this application. Figure 4 As shown, the non-public network contract information update method may include the following S401-S408.

[0168] S401 and AMF network elements send an MRL to the last serving base station, which includes an updated list of CAG information for the UE.

[0169] The MRL sent by the AMF network element to the last serving base station can be used by the last serving base station to update the subscription information of the terminal devices it stores, such as updating the CAG information list of terminal devices (e.g., UEs) stored in the last serving base station. Therefore, the MRL includes the updated CAG information list of the UEs.

[0170] S402. After receiving the MRL, the last serving base station updates its stored list of UE's CAG information to the updated list of UE's CAG information and configures an identifier to indicate the update of the UE's CAG information list.

[0171] For example, the identifier used to indicate that the UE's CAG information list has been updated could be the identifier "No subscription information updated for UE".

[0172] By configuring an identifier to indicate that the UE's CAG information list needs to be updated, the last serving base station can easily determine whether the UE needs to update its CAG information list based on this identifier.

[0173] S403, The last serving base station sends a paging message to the UE.

[0174] The S403 can be referenced. Figure 2 The explanation of S201 in the method shown will not be repeated here.

[0175] S404. After receiving the paging message, the UE sends an RRC recovery request message to the last serving base station.

[0176] Among them, S404 can be referenced. Figure 3 The explanation of S304 in the method shown will not be repeated here.

[0177] S405. The last serving base station verifies the UE.

[0178] When the last serving base station receives the RRC recovery request message, it can verify the UE to determine whether to allow the UE to access the network and whether the UE needs to update its CAG information list. If the updated UE's CAG information list does not have the same CAG identifier as the CAG information list supported by the last serving base station (i.e., the last serving base station and the updated UE's CAG information list are incompatible, or the UE verification fails), then the last serving base station will not allow the UE to access the network. If the last serving base station is also configured with the identifier mentioned above to indicate that the UE's CAG information list needs to be updated, then the last serving base station can determine that the UE needs to update its CAG information list.

[0179] S406. After the UE verification fails, the last serving base station sends an RRC rejection message or an RRC release message to the UE.

[0180] Among them, S406 can be referenced. Figure 3 The explanation of S306 in the method shown will not be repeated here.

[0181] S407. After sending an RRC rejection message or an RRC release message, the last serving base station deletes the identifier configured to indicate an update to the UE's CAG information list.

[0182] In some possible implementations, the last serving base station may delete the aforementioned identifier after receiving the L2ACK from the UE for the RRC rejection message or the RRC release message, that is, the last serving base station deletes the aforementioned identifier after confirming that the UE has successfully received the updated CAG information list.

[0183] The last serving base station deleting the above identifier can prevent the last serving base station from performing S406 again when the UE sends an RRC recovery request to the last serving base station, causing the UE to repeatedly update the CAG information list.

[0184] S408. The UE updates the CAG information list based on the received RRC rejection message or RRC release message.

[0185] The S408 can be referenced. Figure 2 The explanation of S204 in the method shown will not be repeated here.

[0186] based on Figure 4 The method described above allows the UE to update its CAG information list when it is inactive and fails verification by the last serving base station. The last serving base station can determine this by using a configured identifier to indicate the need for CAG information list updates. Therefore, when UE access is not permitted, the updated CAG information list is included in the RRC rejection or RRC release message sent to the UE, enabling the UE to update its CAG information list. This ensures that inactive UEs can update their CAG information list promptly.

[0187] The following will combine Figure 5 Continuing with the example of the terminal device as the UE, the access network device as the last serving base station, the core network device as the AMF network element, the terminal device being inactive, and the updated UE's CAG information list (or first CAG information list) and the access network device's supported CAG information list (or second CAG information list) not having the same CAG identifier, the following steps are taken: Figure 2 The method shown will be explained in detail.

[0188] Figure 5 This is a flowchart illustrating another method for updating non-public network subscription information provided in an embodiment of this application. Figure 5 As shown, the non-public network contract information update method may include the following S501-S507.

[0189] The S501 and AMF network elements send an MRL to the last serving base station. The MRL includes the updated CAG information list of the UE.

[0190] The MRL sent by the AMF network element to the last serving base station can be used by the last serving base station to update the subscription information of the terminal devices it stores, such as updating the CAG information list of terminal devices (e.g., UEs) stored in the last serving base station. Therefore, the MRL includes the updated CAG information list of the UEs.

[0191] S502. The last serving base station updates its stored list of UE's CAG information to the updated list of UE's CAG information based on the received MRL.

[0192] S503. The last serving base station sends a paging message to the UE, which may carry a reason value to indicate the UE's CAG information list update.

[0193] For example, the reason value could be "UE subscription information update".

[0194] In addition, the S503 can also be referenced Figure 2 The explanation of S201 in the method shown will not be repeated here.

[0195] S504. After receiving the paging message, the UE sends an RRC recovery request message to the last serving base station, which carries the aforementioned cause value.

[0196] When a UE detects a paging message, it can check if the message contains its corresponding identifier. If so, the UE can send an RRC recovery request message to the last serving base station to request a connection with it. If the detected paging message contains a cause value, the UE can also include that cause value in its sent RRC recovery request message.

[0197] S505, the last serving base station verifies the UE.

[0198] When the last serving base station receives the RRC recovery request message, it can verify the UE to determine whether to allow the UE to access the network and whether the UE needs to update its CAG information list. If the updated UE's CAG information list does not have the same CAG identifier as the CAG information list supported by the last serving base station (i.e., the last serving base station and the updated UE's CAG information list are incompatible, or the UE verification fails), then the last serving base station will not allow the UE to access the network. If the RRC recovery request received by the last serving base station carries the aforementioned reason value used to indicate that the UE's CAG information list needs to be updated, then the last serving base station can determine that the UE needs to update its CAG information list.

[0199] S506. After the UE verification fails, the last serving base station sends an RRC rejection message or an RRC release message to the UE.

[0200] Among them, S506 can be referenced. Figure 3 The explanation of S306 in the method shown will not be repeated here.

[0201] S507. The UE updates the CAG information list based on the received RRC rejection message or RRC release message.

[0202] The S507 can be referenced. Figure 2 The explanation of S204 in the method shown will not be repeated here.

[0203] based on Figure 5The method described above allows the UE to update its CAG information list when it is in an inactive state and fails verification by the last serving base station. The last serving base station can determine the need for the UE to update its CAG information list based on the cause value carried in the received RRC recovery request message. Therefore, when access is not permitted, the updated CAG information list is included in the RRC rejection message or RRC release message sent to the UE, enabling the UE to update its CAG information list. This ensures that the inactive UE can update its CAG information list promptly.

[0204] The following will combine Figure 6 Taking a terminal device as a UE, a communication system with two access network devices (e.g., a first access network device and a second access network device), where the first access network device is another base station near the last serving base station (or the target base station, i.e., the base station receiving the RRC recovery request message sent by the UE), the second access network device is the last serving base station, the core network device is an AMF network element, the terminal device is inactive, and the updated UE's CAG information list (or the first CAG information list) and the CAG information list supported by the access network device (or the second CAG information list) do not have the same CAG identifier as an example, for... Figure 2 The method shown will be explained in detail.

[0205] Figure 6 This is a flowchart illustrating another method for updating non-public network subscription information provided in an embodiment of this application. Figure 6 As shown, the non-public network contract information update method may include the following S601-S6010.

[0206] S601 and AMF network elements send an MRL to the last serving base station, which includes the updated CAG information list of the UE.

[0207] The MRL sent by the AMF network element to the last serving base station can be used by the last serving base station to update the subscription information of terminal devices, such as updating the CAG information list of terminal devices (e.g., UEs) configured in the last serving base station. Therefore, the MRL includes the updated CAG information list of the UE.

[0208] S602. The last serving base station updates its stored list of UE's CAG information to the updated list of UE's CAG information based on the received MRL.

[0209] S603. The last serving base station sends a RAN paging message to the target base station.

[0210] Among them, S603 can be referenced. Figure 2 The description of other access network devices near the last serving access network device in S201 of the method shown will not be repeated here.

[0211] S604. After receiving the RAN paging message, the target base station sends a paging message to the UE.

[0212] The S604 can be referenced. Figure 2 The description of S201 in the method shown regarding other access network devices near the last serving access network device is not repeated here.

[0213] S605: After receiving the paging message, the UE sends an RRC recovery request message to the target base station.

[0214] When the UE detects a paging message, it can check if there is a corresponding identifier in the paging message. If so, the UE can send an RRC recovery request message to the target base station to request a connection with the target base station.

[0215] S606. After receiving the RRC recovery request message, the target base station sends a context request message to the last serving base station to request the UE's context from the last serving base station.

[0216] S607. After receiving the context request message, the last serving base station sends a context request response message or a context request failure message to the target base station.

[0217] The context request response message or context request failure message may carry the updated CAG information list of the UE. It may also carry indication information to indicate that the UE's CAG information list has been updated. For example, this indication information could be "instruct UE to update subscription information".

[0218] S608. After receiving a context request response message or a context request failure message, the target base station verifies the UE.

[0219] The target base station can verify the UE to determine whether to allow the UE to access the network and whether the UE needs to update its CAG information list. If the updated UE's CAG information list does not have the same CAG identifier as the CAG information list supported by the target base station (i.e., the target base station's CAG information list is incompatible with the updated UE's CAG information list, or the UE verification fails), then the target base station will not allow the UE to access the network. If the context request response message or context request failure message received by the target base station carries indication information for updating the UE's CAG information list, then the target base station can determine that the UE needs to update its CAG information list.

[0220] S609. After the UE verification fails, the target base station sends an RRC rejection message or an RRC release message to the UE.

[0221] If the target base station determines that the UE needs to update its CAG information list, the updated UE CAG information list can be carried in the RRC rejection message or RRC release message. This updated UE CAG information list can be the one carried in the context request response message or context request failure message received by the target base station.

[0222] Optionally, the RRC rejection message or RRC release message may also carry the cause value "UE subscription information update" to instruct the UE to update the CAG information list so that the UE can subsequently update the CAG information list according to the cause value.

[0223] S6010, the UE updates the CAG information list based on the received RRC rejection message or RRC release message.

[0224] The S6010 can be used as a reference. Figure 2 The explanation of S204 in the method shown will not be repeated here.

[0225] In this embodiment of the application, optionally, Figure 7 This is a flowchart illustrating another method for updating non-public network subscription information provided in an embodiment of this application. Figure 7 As shown, the non-public network contract information update method includes S701-S7010, which is similar to... Figure 6 The methods shown are basically the same, with S701-S7010 corresponding to S601-S6010 respectively. The difference lies in that the RAN paging message in S703 can also carry a reason value to indicate the UE's CAG information list update, such as the reason value "UE subscription information update". In this case, the paging message in S704 and the RRC recovery request message in S705 can also carry the above reason value. Thus, when the target base station receives the RRC recovery request message, it can determine from the indication of the reason value that the purpose of the UE sending the RRC recovery request is to update the CAG information list.

[0226] based on Figure 6 The method shown and Figure 7The method described above allows the target base station to determine that the UE needs to update its CAG information list when the UE is in an inactive state and fails to authenticate when sending an RRC recovery request message to another base station near the last serving base station. This can be done based on the indication information carried in the received context request response message / context request failure message, and / or the reason value carried in the RRC recovery request message. Therefore, when UE access is not permitted, the target base station enables the UE to update its CAG information list by including the updated UE's CAG information list in the RRC rejection message or RRC release message sent to the UE. This ensures that the inactive UE can update its CAG information list in a timely manner.

[0227] In this embodiment, another method for updating non-public network subscription information is also provided. This method may include: upon receiving an RRC recovery request message, the access network device may further send an RRC recovery message to the terminal device, carrying in the RRC recovery message an indication, such as a second indication, for restricting the terminal device from transmitting non-access stratum (NAS) signaling and / or service data. This enables the terminal device to establish a restricted temporary connection with the access network device, thereby receiving a NAS-PDU containing new subscription information from the core network device (such as an AMF network element) sent by the access network device.

[0228] The following will combine Figure 8 Taking the terminal device as UE, the access network device as the last serving base station, the core network device as the AMF network element, the terminal device in an inactive state, and the updated UE's CAG information list (or the first CAG information list) and the access network device's supported CAG information list (or the second CAG information list) as an example, the non-public network subscription information update method provided in this application embodiment will be described in detail.

[0229] Figure 8 This is a flowchart illustrating another method for updating non-public network subscription information provided in an embodiment of this application. Figure 8 As shown, the non-public network contract information update method may include the following steps S801-S8011.

[0230] S801 and AMF network elements send NAS-PDU and MRL to the last serving base station. Both NAS-PDU and MRL include the updated CAG information list of the UE.

[0231] The NAS-PDU sent by the AMF network element to the last serving base station is used by the last serving base station to transparently transmit to the UE to update the UE's CAG information list. Therefore, the NAS-PDU includes the updated CAG information list of the UE. The last serving base station can also save the updated CAG information of the UE when it receives the MRL, so that the last serving base station can determine whether the UE needs to update its CAG information list based on the saved CAG information and the CAG information before the update.

[0232] S802. After receiving the MRL, the last serving base station saves the updated list of UE CAG information in the MRL, as well as the list of UE CAG information before the update.

[0233] S803, the last serving base station sends a paging message to the UE.

[0234] The S803 can be referenced. Figure 2 The explanation of S201 in the method shown will not be repeated here.

[0235] S804. After receiving the paging message, the UE sends an RRC recovery request message to the last serving base station.

[0236] When the UE detects a paging message, it can check if there is a corresponding identifier in the paging message. If there is, the UE can send an RRC recovery request message to the last serving base station to request a connection with the last serving base station.

[0237] S805, the last serving base station verifies the UE.

[0238] When the last serving base station receives the RRC recovery request message, it can verify the UE to determine whether to allow the UE to access the network and whether the UE needs to update its CAG information list. If the updated UE's CAG information list does not have the same CAG identifier as the CAG information list supported by the last serving base station (i.e., the last serving base station and the updated UE's CAG information list are incompatible, or the UE verification fails), then the last serving base station will not allow the UE to access the network. If, at this time, the CAG information list before the update has the same CAG identifier as the CAG information list supported by the last serving base station (i.e., the last serving base station and the CAG information list before the update are compatible), then the last serving base station can determine that the UE needs to update its CAG information list.

[0239] S806. If the last serving base station determines that the UE needs to update its CAG information list, and after the UE authentication fails, the last serving base station sends an RRC recovery message to the UE. This RRC recovery message carries an indication to restrict the UE from transmitting NAS signaling (such as service requests, PDU session control establishment requests, etc.) and / or service data. This indication prevents the UE from sending data to core network equipment through the last serving base station after establishing a temporary connection with it.

[0240] This RRC recovery message enables the UE to establish a temporary connection with the last serving base station under restricted transmission conditions, so that the last serving base station can transparently transmit the NAS-PDU containing the updated CAG information list of the UE sent by the core network equipment to the UE.

[0241] S807. After receiving the RRC recovery message, the UE sends an RRC recovery completion message to the last serving base station.

[0242] S808, UE enters connected state and establishes a connection with the last serving base station.

[0243] S809, the last serving base station sends a NAS-PDU to the UE.

[0244] S8010, the UE updates the CAG information list based on the received NAS-PDU.

[0245] In some possible implementations, after updating the CAG information list, the terminal device can enter an idle state to select a suitable cell for access based on the updated CAG information list of the terminal device.

[0246] Optionally, after S8010, this embodiment may further include S8011, where the last serving base station sends an RRC release message to the UE.

[0247] The RRC release message is used to put the UE into an idle state after the UE receives the NAS-PDU, thus avoiding a long-term connection between the UE and the last serving base station.

[0248] based on Figure 8 The method shown allows the UE to update its CAG information list when the terminal device is inactive and cannot pass the verification of the last serving base station. The last serving base station can determine that the UE needs to update its CAG information list based on the saved updated UE CAG information list and the CAG information list before the update. Thus, while restricting the information transmitted by the UE, a temporary connection is established with the UE so that the UE can receive the NAS-PDU containing the updated UE CAG information list sent by the core network device from the last serving base station. This facilitates the timely update of the CAG information list for the inactive UE.

[0249] The above primarily describes the solution provided by the embodiments of this application from the perspective of interaction between various nodes. It is understood that each node, such as a terminal device, a first access network device, and a second access network device, includes corresponding hardware structures and / or software modules to perform the aforementioned functions. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, the methods of the embodiments of this application can be implemented in hardware, software, or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0250] This application embodiment can divide the terminal device, the first access network device, and the second access network device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0251] In practical implementation, the network elements shown in this application, such as terminal equipment, first access network equipment, and second access network equipment, can be adopted as follows: Figure 9 The shown composition or includes Figure 9 The components shown. Figure 9 This is a schematic diagram of a communication device provided in an embodiment of this application. When the communication device has the functions of the terminal device described in the embodiment of this application, the communication device can be a terminal device or a chip or system-on-a-chip in the terminal device. When the communication device has the functions of the access network device described in the embodiment of this application, the communication device can be an access network device or a chip or system-on-a-chip in the access network device.

[0252] like Figure 9 As shown, the communication device may include a processor 901, a communication line 902, and a transceiver 903. The processor 901, memory 904, and transceiver 903 can be connected via the communication line 902. In one example, the processor 901 may include one or more CPUs, for example... Figure 9 CPU0 and CPU1 in the CPU.

[0253] As an optional implementation, the communication device includes multiple processors, for example, besides Figure 9 In addition to processor 901, it may also include processor 907.

[0254] The processor 901 can be a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 901 can also be other devices with processing capabilities, such as circuits, devices, or software modules.

[0255] Communication line 902 is used to transmit information between the components included in the communication device.

[0256] Transceiver 903 is used to communicate with other devices or other communication networks. These other communication networks can be Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. Transceiver 903 can be an interface circuit, pins, RF module, transceiver, or any device capable of enabling communication.

[0257] Furthermore, the communication device may also include a memory 904. The memory 904 is used to store instructions. These instructions may be computer programs.

[0258] The memory 904 can be a read-only memory (ROM) or other type of static storage device that can store static information and / or instructions; it can also be a random access memory (RAM) or other type of dynamic storage device that can store information and / or instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage, magnetic disk storage media or other magnetic storage devices. Optical disc storage includes compressed optical discs, laser discs, optical discs, digital universal optical discs, or Blu-ray discs, etc.

[0259] It should be noted that the memory 904 can exist independently of the processor 901 or be integrated with the processor 901. The memory 904 can be used to store instructions, program code, or some data, etc. The memory 904 can be located inside or outside the communication device, without limitation. When the processor 901 executes the instructions stored in the memory 904, it can implement the non-public network subscription information update method provided in the above embodiments of this application.

[0260] As an optional implementation, the communication device also includes an output device 905 and an input device 906. For example, the input device 906 is a device such as a keyboard, mouse, microphone, or joystick, and the output device 905 is a device such as a display screen or speaker.

[0261] It should be noted that the communication device can be a desktop computer, laptop computer, network server, mobile phone, tablet computer, wireless terminal, embedded device, chip system, or something else. Figure 9 Equipment with a similar structure. Furthermore... Figure 9 The structural composition shown does not constitute a limitation on the communication device, except... Figure 9 In addition to the components shown, the communication device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0262] In this embodiment of the application, the chip system may be composed of chips or may include chips and other discrete devices.

[0263] Figure 10 A structural diagram of a communication device 1000 is shown. This communication device 1000 can be a first access network device, a chip within the first access network device, a system-on-a-chip, or other devices capable of implementing the functions of the first access network device in the above-described method. This communication device 1000 can be used to execute the functions of the first access network device involved in the above-described method embodiments. As one possible implementation, Figure 10 The communication device 1000 shown includes: a receiving unit 1001, a processing unit 1002, and a transmitting unit 1003.

[0264] The receiving unit 1001 can be used to receive an RRC recovery request message sent by the terminal device;

[0265] The sending unit 1003 can be used to send a first message to the terminal device. The first message includes a first CAG information list, wherein the first CAG information list is the updated CAG information list of the terminal device, and the first message is an RRC rejection message or an RRC release message.

[0266] In one possible design, the first message also includes a first cause value, which is used to instruct the terminal device to update the CAG information list.

[0267] In one possible design, the sending unit 1003 is further configured to send a second message to the terminal device, the second message being used to instruct the terminal device to send an RRC recovery request message to the first access network device, the second message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list; the RRC recovery request message including the second cause value.

[0268] In one possible design, the receiving unit 1001 is further configured to receive a third message sent by the core network device, the third message including a first CAG information list; the processing unit 1002 is configured to set a first identifier, the first identifier being used to indicate that the CAG information list of the terminal device has not been updated.

[0269] In one possible design, after sending the first message to the terminal device, the processing unit 1002 is also used to delete the first identifier.

[0270] In one possible design, the sending unit 1003 is further configured to send a fourth message to the second access network device, the fourth message being used to request the context of the terminal device; the receiving unit 1001 is further configured to receive a fifth message sent by the second access network device, the fifth message including a first CAG information list and a first indication, the first indication being used to instruct the terminal device to update the CAG information list.

[0271] In one possible design, the receiving unit 1001 is further configured to receive a sixth message sent by the second access network device, the sixth message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list; the sending unit 1003 is further configured to send a second message to the terminal device, the second message being used to instruct the terminal device to send an RRC recovery request message to the first access network device, the second message including a second cause value; the RRC recovery request message including a second cause value.

[0272] In one possible design, the processing unit 1002 is also configured in a system message to configure at least one of the preamble resources, time domain resources, and frequency domain resources of the terminal device specifically for updating the CAG information list.

[0273] Specifically, the aforementioned Figures 2 to 7 Each step involved in the first access network device in the method embodiment shown can be referenced from the corresponding functional unit or module of the device. The communication device can be used to perform the function of the first access network device in the aforementioned non-public network subscription information update method, so it can achieve the same effect as the aforementioned non-public network subscription information update method, which will not be elaborated here.

[0274] As another feasible approach Figure 10 The communication device 1000 shown can also be used to perform, for example Figure 8 The method embodiment shown relates to the function of the first access network device.

[0275] For example, receiving unit 1001 can be used to receive an RRC recovery request message sent by a terminal device; sending unit 1003 can be used to send an RRC recovery message to the terminal device. The RRC recovery message includes a second indication, which is used to restrict the terminal device from transmitting non-access stratum (NAS) signaling and / or service data.

[0276] Specifically, the aforementioned Figure 8 Each step involved in the first access network device in the method embodiment shown can be referenced from the corresponding functional unit or module of the device. The communication device can be used to perform the function of the first access network device in the aforementioned non-public network subscription information update method, so it can achieve the same effect as the aforementioned non-public network subscription information update method, which will not be elaborated here.

[0277] Figure 11 A structural diagram of a communication device 1100 is shown. This communication device 1100 can be a second access network device, a chip within the second access network device, a system-on-a-chip, or other devices capable of implementing the functions of the second access network device in the above-described method. The communication device 1100 can be used to execute the functions of the second access network device involved in the above-described method embodiments. As one possible implementation, Figure 11 The communication device 1100 shown includes: a receiving unit 1101 and a transmitting unit 1102.

[0278] The receiving unit 1101 can be used to receive a fourth message sent by the first access network device, the fourth message being used to request the context of the terminal device;

[0279] The sending unit 1102 can be used to send a fifth message to the first access network device. The fifth message includes a first CAG information list and a first indication. The first indication is used to instruct the terminal device to update the CAG information list.

[0280] In one possible design, the sending unit 1102 is further configured to send a sixth message to the first access network device, the sixth message being used to instruct the first access network device to send a second message, the sixth message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list.

[0281] Specifically, the aforementioned Figure 6 , Figure 7Each step involved in the second access network device in the method embodiment shown can be referenced from the corresponding functional unit or module of the device. The communication device can be used to perform the function of the second access network device in the aforementioned non-public network subscription information update method, so it can achieve the same effect as the aforementioned non-public network subscription information update method, which will not be elaborated here.

[0282] Figure 12 A structural diagram of a communication device 1200 is shown. This communication device 1200 can be a terminal device, a chip within the terminal device, a system-on-a-chip, or other devices capable of implementing the functions of the terminal device in the above-described method. The communication device 1200 can be used to execute the functions of the terminal device involved in the above-described method embodiments. As one possible implementation, Figure 12 The communication device 1200 shown includes: a receiving unit 1201 and a transmitting unit 1202.

[0283] The sending unit 1202 is used to send an RRC recovery request message to the first access network device;

[0284] The receiving unit 1201 is used to receive a first message from the first access network device. The first message is an RRC rejection message or an RRC release message. The first message includes a first CAG information list, wherein the first CAG information list is the updated CAG information list of the terminal device.

[0285] In one possible design, the first message also includes a first cause value, which is used to instruct the terminal device to update the CAG information list.

[0286] In one possible design, the receiving unit 1201 is further configured to receive a second message sent by the first access network device. The second message is used to instruct the terminal device to send an RRC recovery request message to the first access network device. The second message includes a second cause value, which is used to instruct the terminal device to update its CAG information list. The RRC recovery request message includes the second cause value.

[0287] Specifically, the aforementioned Figures 2 to 7 Each step involved in the terminal device in the method embodiment shown can be referenced from the corresponding functional unit or module of the device. The communication device can be used to perform the functions of the terminal device in the aforementioned non-public network subscription information update method, and thus can achieve the same effect as the aforementioned non-public network subscription information update method, which will not be elaborated here.

[0288] As another feasible approach Figure 12 The communication device 1200 shown can also be used to perform, for example Figure 8 The method embodiments shown involve the functions of the terminal device.

[0289] For example, the sending unit 1202 can be used to send an RRC recovery request message to the first access network device;

[0290] The receiving unit 1201 can be used to receive an RRC recovery message sent by the first access network device. The RRC recovery message includes a second indication, which is used to restrict the terminal device from transmitting NAS signaling and / or service data.

[0291] Specifically, the aforementioned Figure 8 Each step involved in the terminal device in the method embodiment shown can be referenced from the corresponding functional unit or module of the device. The communication device can be used to perform the functions of the terminal device in the aforementioned non-public network subscription information update method, and thus can achieve the same effect as the aforementioned non-public network subscription information update method, which will not be elaborated here.

[0292] This application also provides a communication system, which may include: a terminal device, a first access network device, and a second access network device. The first access network device may have the functions of the aforementioned communication device 1000, the second access network device may have the functions of the aforementioned communication device 1100, and the terminal device may have the functions of the aforementioned communication device 1200.

[0293] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be a terminal device of any of the foregoing embodiments, such as an internal storage unit including a data sending end and / or a data receiving end, such as a hard disk or memory of the terminal device. The computer-readable storage medium can also be an external storage device of the terminal device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device. Further, the computer-readable storage medium can include both the internal storage unit and the external storage device of the terminal device. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0294] This application also provides computer instructions. All or part of the processes in the above method embodiments can be executed by computer instructions to instruct related hardware (such as computers, processors, network devices, and terminals). The program can be stored in the aforementioned computer-readable storage medium.

[0295] This application also provides a chip system. The chip system may be composed of chips or may include chips and other discrete devices, without limitation. The chip system includes a processor and a transceiver. All or part of the processes in the above method embodiments can be completed by this chip system. For example, the chip system can be used to implement the functions performed by the terminal device in the above method embodiments, or to implement the functions performed by the first access network device or the second access network device in the above method embodiments.

[0296] In one possible design, the chip system further includes a memory for storing program instructions and / or data. When the chip system is running, the processor executes the program instructions stored in the memory to cause the chip system to perform the functions performed by the terminal device in the above method embodiments, or the functions performed by the first access network device in the above method embodiments, or the functions performed by the terminal device in the above method embodiments.

[0297] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0298] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store instructions and / or data.

[0299] It should be noted that the terms "comprising" and "having," and any variations thereof, in the specification, claims, and drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0300] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0301] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0302] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0303] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device, such as a microcontroller, chip, or processor, to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0304] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for updating contracted information on a non-public network, characterized in that, The method includes: The first access network device receives a Radio Resource Control (RRC) recovery request message sent by the terminal device; The first access network device sends a first message to the terminal device. The first message includes a first closed access group (CAG) information list, wherein the first CAG information list is the updated CAG information list of the terminal device, and the first message is an RRC rejection message or an RRC release message.

2. The method according to claim 1, characterized in that, The first message also includes a first reason value, which is used to instruct the terminal device to update the CAG information list.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The first access network device sends a second message to the terminal device. The second message is used to instruct the terminal device to send the RRC recovery request message to the first access network device. The second message includes a second cause value, which is used to instruct the terminal device to update its CAG information list. The RRC recovery request message includes the second cause value.

4. The method according to claim 1 or 2, characterized in that, The method further includes: The first access network device receives a third message sent by the core network device, the third message including the first CAG information list; The first access network device sets a first identifier, which is used to indicate that the CAG information list of the terminal device has not been updated.

5. The method according to claim 4, characterized in that, The method further includes: After the first access network device sends the first message to the terminal device, the first access network device deletes the first identifier.

6. The method according to claim 1 or 2, characterized in that, The method further includes: The first access network device sends a fourth message to the second access network device, the fourth message being used to request the context of the terminal device; The first access network device receives a fifth message sent by the second access network device. The fifth message includes the first CAG information list and a first indication, wherein the first indication is used to instruct the terminal device to update the CAG information list.

7. The method according to claim 6, characterized in that, The method further includes: The first access network device receives a sixth message sent by the second access network device. The sixth message includes a second reason value, which is used to instruct the terminal device to update its CAG information list. The first access network device sends a second message to the terminal device, the second message being used to instruct the terminal device to send the RRC recovery request message to the first access network device, the second message including the second cause value; The RRC recovery request message includes the second cause value.

8. The method according to claim 1, characterized in that, The method further includes: The first access network device configures the terminal device in the system message to use at least one of the preamble resources, time domain resources, and frequency domain resources specifically for updating the CAG information list.

9. A method for updating contracted information on a non-public network, characterized in that, The method includes: The terminal device sends a Radio Resource Control (RRC) Recovery Request message to the first access network device; The terminal device receives a first message from the first access network device, the first message being an RRC rejection message or an RRC release message; the first message includes a first closed access group (CAG) information list, wherein the first CAG information list is the updated CAG information list of the terminal device.

10. The method according to claim 9, characterized in that, The first message also includes a first reason value, which is used to instruct the terminal device to update the CAG information list.

11. The method according to claim 9 or 10, characterized in that, The method further includes: The terminal device receives a second message sent by the first access network device. The second message is used to instruct the terminal device to send the RRC recovery request message to the first access network device. The second message includes a second cause value, which is used to instruct the terminal device to update its CAG information list. The RRC recovery request message includes the second cause value.

12. A communication device, characterized in that, The communication device includes: The receiving unit is used to receive Radio Resource Control (RRC) recovery request messages sent by the terminal device; The sending unit is configured to send a first message to the terminal device, the first message including a first Closed Access Group (CAG) information list, wherein the first CAG information list is the updated CAG information list of the terminal device, and the first message is an RRC rejection message or an RRC release message.

13. The communication device according to claim 12, characterized in that, The first message also includes a first reason value, which is used to instruct the terminal device to update the CAG information list.

14. The communication device according to claim 12 or 13, characterized in that, The sending unit is further configured to send a second message to the terminal device, the second message being configured to instruct the terminal device to send the RRC recovery request message to the communication device, the second message including a second cause value, the second cause value being configured to instruct the terminal device to update its CAG information list; the RRC recovery request message including the second cause value.

15. The communication device according to claim 12 or 13, characterized in that, The receiving unit is further configured to receive a third message sent by the core network device, the third message including the first CAG information list; The communication device further includes a processing unit for setting a first identifier, which indicates that the CAG information list of the terminal device has not been updated.

16. The communication device according to claim 15, characterized in that, After sending the first message to the terminal device, the processing unit is further configured to delete the first identifier.

17. The communication device according to claim 12 or 13, characterized in that, The sending unit is further configured to send a fourth message to the second access network device, the fourth message being used to request the context of the terminal device; The receiving unit is further configured to receive a fifth message sent by the second access network device, the fifth message including the first CAG information list and a first indication, the first indication being used to instruct the terminal device to update the CAG information list.

18. The communication device according to claim 17, characterized in that, The receiving unit is further configured to receive a sixth message sent by the second access network device, the sixth message including a second cause value, the second cause value being used to instruct the terminal device to update its CAG information list; The sending unit is further configured to send a second message to the terminal device, the second message being configured to instruct the terminal device to send the RRC recovery request message to the communication device, the second message including the second cause value; The RRC recovery request message includes the second cause value.

19. The communication device according to claim 12, characterized in that, The communication device further includes a processing unit for configuring at least one of the preamble resources, time domain resources, and frequency domain resources of the terminal device specifically for updating the CAG information list in system messages.

20. A communication device, characterized in that, The communication device includes: The transmitting unit is used to send a Radio Resource Control (RRC) recovery request message to the first access network device; The receiving unit is configured to receive a first message from the first access network device, wherein the first message is an RRC rejection message or an RRC release message; the first message includes a first closed access group (CAG) information list, wherein the first CAG information list is the updated CAG information list of the communication device.

21. The communication device according to claim 20, characterized in that, The receiving unit is further configured to receive a second message sent by the first access network device, the second message being configured to instruct the communication device to send the RRC recovery request message to the first access network device, the second message including a second cause value, the second cause value being configured to instruct the communication device to update its CAG information list; the RRC recovery request message including the second cause value.

22. A communication device, characterized in that, The communication device includes a processor and a transceiver, the processor and the transceiver being configured to support the communication device in performing the non-public network subscription information update method as described in any one of claims 1-11.

Images