WO2021062664A1 - 更新配置数据的方法、装置和系统 - Google Patents

更新配置数据的方法、装置和系统 Download PDF

Info

Publication number
WO2021062664A1
WO2021062664A1 PCT/CN2019/109528 CN2019109528W WO2021062664A1 WO 2021062664 A1 WO2021062664 A1 WO 2021062664A1 CN 2019109528 W CN2019109528 W CN 2019109528W WO 2021062664 A1 WO2021062664 A1 WO 2021062664A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration data
access
cag
terminal device
mobility management
Prior art date
Application number
PCT/CN2019/109528
Other languages
English (en)
French (fr)
Inventor
郭龙华
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2019/109528 priority Critical patent/WO2021062664A1/zh
Priority to EP20872648.9A priority patent/EP4030828A4/en
Priority to BR112022006079A priority patent/BR112022006079A2/pt
Priority to CN202080068459.9A priority patent/CN114451016B/zh
Priority to PCT/CN2020/108497 priority patent/WO2021063115A1/zh
Publication of WO2021062664A1 publication Critical patent/WO2021062664A1/zh
Priority to US17/708,841 priority patent/US20220225098A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/76—Group identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • This application relates to the field of communication technology, and more specifically, to a method, device, and system for updating configuration data.
  • the closed access group (CG) technology mainly restricts the UE's access to the cell, and only allowed users can access the core network through the CAG cell.
  • the access network device can broadcast one or more CAG IDs, and the CAG ID is the CAG cell identifier.
  • the UE is configured with a list of CAGs that are allowed to access, for example, a list of CAG IDs that the UE is allowed to access. After the UE receives the broadcast CAG ID, if it is in the list of CAG IDs allowed by itself, it tries to access the core network through the current CAG cell.
  • the UE may also be configured with a CAG Only indication, which restricts the UE to only access the network system through the CAG cell.
  • the UE When the CAG list allowed by the UE is empty and is set to CAG only, because there is no accessible CAG cell in the UE, and it is set to CAG only, the UE can no longer access the network, and the configuration update process cannot be performed. .
  • the present application provides a method and device for updating configuration data to implement the configuration update of the UE.
  • this application provides a method for updating configuration data, including:
  • the first configuration data includes a first restriction indication and an empty closed access group CAG list, and the first restriction indication is used to instruct the terminal device to pass the closed access group CAG list.
  • the access group CAG accesses the network
  • the CAG list is a set of CAG IDs that the terminal device is allowed to access
  • the access and mobility management function device configures the terminal device to not only be allowed to pass through the CAG list
  • the access and mobility management The device sends the second configuration data to the terminal device.
  • the access and mobility management function device sends first configuration data for removing the first restriction instruction to the terminal device, and the device for removing the first restriction instruction
  • the first configuration data is used to configure that the terminal device is no longer only allowed to access the network through CAG.
  • the access and mobility management function device does not send the first configuration data to the terminal device, and the empty CAG list is used to replace the non-function stored in the terminal device. Empty CAG list.
  • the first configuration data for removing the first restriction indication includes first indication information, and the first indication information is used to indicate that the terminal device is no longer only allowed to pass through CAG accesses the network.
  • the access and mobility management function device sends at least one identifier of a default CAG to the terminal device, and the default CAG is used for the terminal device to update configuration data.
  • the access and mobility management apparatus uses the NAS security context to protect the confidentiality and/or integrity of the rejection message or the configuration update message.
  • the access and mobility management apparatus activates the NAS security context before sending the second configuration data.
  • the UE can update the configuration data through the default CAG cell and the network side, or cancel the CAG only state of the UE, so that the UE can access with non-CAG cells Network to perform configuration updates.
  • the default CAG cell is not included in the CAG list, and can also be used as a default configured CAG cell as a part of the CAG list stored by the UE.
  • the present application provides a method for updating configuration data, which is characterized in that it includes:
  • the first configuration data includes a first restriction indication and an empty closed access group CAG list, and the first restriction indication is used to instruct the terminal device to pass the closed access group.
  • the CAG list is a set of CAG IDs that the terminal device is allowed to access, and the terminal device is configured not only to be allowed to access the network through the CAG in the CAG list;
  • the configuration data for the terminal device is updated to the second configuration data, wherein the CAG list in the second configuration data is not empty or does not include the first restriction indication, the terminal device receives Access and mobility management device second configuration data.
  • this application provides another method for updating configuration data, which is characterized in that it includes:
  • the first configuration data includes a first restriction indication and an empty closed access group CAG list, and the first restriction indication is used to indicate
  • the terminal device accesses the network through a closed access group CAG
  • the CAG list is a set of CAG IDs that the terminal device is allowed to access
  • the configuration data management device does not send the empty CAG identifier list to the terminal Device
  • the access and mobility management The device sends the second configuration data to the terminal device.
  • the configuration data management device is a unified data management network element
  • the unified data management network element when the configuration data in the unified data management network element is the first configuration data, the unified data management network element will The logo of the terminal device is added to the blacklist to prohibit the terminal device from accessing the network; when the configuration data in the unified data management network element is updated to the second configuration data, the unified data management network element will Removing the identification of the terminal device from the blacklist.
  • the configuration data management device is a unified data management network element
  • the unified data management network element sends second restriction indication information to the access and mobility management function device.
  • the configuration data management device is a unified data management network element, and the unified data management network element removes the first restriction instruction in the first configuration data and sends it to all The access and mobility management function device.
  • this application provides a device for updating configuration data.
  • the device may be a terminal device or a chip for the terminal device.
  • the device has the function of realizing the above-mentioned embodiments of the third aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a device for updating configuration data.
  • the device may be an access and mobility management function device or a chip for access and mobility management function network elements.
  • the device has the function of realizing the above-mentioned first aspect or the first and third aspects of the embodiments. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a device for updating configuration data.
  • the device may be a unified data management network element, or a chip used for a unified data management network element.
  • the device has the function of realizing the foregoing third aspect or the embodiments of the third aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a device for updating configuration data, including: a processor and a memory; the memory is used to store computer execution instructions, and when the device is running, the processor executes the computer execution instructions stored in the memory, So that the device executes the methods described in the above aspects.
  • the device can be a terminal device, or a chip for terminal equipment, or an access and mobility management network element, or a chip for access and mobility management, or a unified data management network element, or a unified data management Chip.
  • the present application provides an apparatus for updating configuration data, including: including units or means for executing each step of the above-mentioned aspects.
  • the device may be an access and mobility management network element, or a terminal device, or a unified data management network element.
  • the present application provides a device for determining update configuration data, including a processor and an interface circuit, and the processor is configured to implement the methods described in the foregoing aspects through the interface circuit.
  • the processor includes one or more.
  • the device may be a chip used for access and mobility management network elements, or terminal equipment, or unified data management network elements.
  • the present application provides an apparatus for updating configuration data, including a processor, configured to be connected to a memory, and configured to call a program stored in the memory to execute the methods described in the foregoing aspects.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • the device can be a terminal device, or a chip for terminal equipment, or an access and mobility management network element, or an access and mobility management network element, or a unified data management network element, or a unified data management The chip of the network element.
  • the present application also provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when run on a computer, cause a processor to execute the methods described in the foregoing aspects.
  • this application also provides a computer program product including instructions, which when run on a computer, causes the computer to execute the methods described in the above aspects.
  • the present application also provides a chip system, including a processor, configured to execute the methods described in the foregoing aspects.
  • Figure 1 is a schematic diagram of a possible network architecture applicable to this application
  • FIG. 2 is a schematic flowchart of a method for updating configuration data provided by this application
  • FIG. 3 is a schematic flowchart of another method for updating configuration data provided by this application.
  • FIG. 4 is a schematic flowchart of another method for updating configuration data provided by this application.
  • FIG. 5 is a schematic flowchart of another method for updating configuration data provided by this application.
  • FIG. 6 is a schematic diagram of a device for updating configuration data provided by this application.
  • FIG. 7 is a schematic diagram of another device for updating configuration data provided by this application.
  • FIG. 8 is a schematic diagram of a terminal device provided by this application.
  • FIG. 9 is a schematic structural diagram of an apparatus for updating configuration data provided by this application.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE frequency division duplex FDD
  • TDD LTE Time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • the terminal device in the embodiments of the present application may refer to a chip, user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication equipment, user Agent or user device.
  • the terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (personal digital assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminals in the public land mobile network (PLMN) that will evolve in the future Devices, etc., are not limited in the embodiment of the present application.
  • PLMN public land mobile network
  • the core network (CN) device in the embodiment of the present application may be a control plane anchor point of the terminal device, and provides functions such as registration area update for the terminal.
  • the core network device may include access and mobility management function entities (access and mobility management function, AMF).
  • AMF access and mobility management function
  • the core network device may be used for network equipment that provides functions such as core network access (core access) and mobility management for the terminal.
  • the specific function of the core network device may be similar to the function of the mobility management entity (MME) in the LTE system.
  • MME mobility management entity
  • the access network device in the embodiment of the present application may be a device used to communicate with a terminal device, and the access network device may be a radio access network (RAN) device.
  • the RAN equipment may include various types of base stations.
  • the base stations in the embodiments of the present application may include various forms of macro base stations, micro base stations, relay stations, access points, and so on.
  • the names of devices with base station functions may be different.
  • an LTE network it is called an evolved NodeB (evolved NodeB, eNB, or eNodeB)
  • 3rd generation, 3G 3rd generation
  • NodeB NodeB
  • 5G fifth generation
  • it may be referred to as a g node (g Node B, gNB), etc., which is not limited in the embodiment of the present application.
  • the access network equipment provides services for the cell
  • the terminal device communicates with the network equipment through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell.
  • the cell can be a cell corresponding to a network device (e.g. a base station).
  • the cell can belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here can include: Metro cell, micro cell ( Micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
  • Figure 1 is a schematic diagram of the 5G system architecture.
  • the system architecture shown in Figure 1 includes user equipment (UE), radio access network (RAN), access and mobility management function (AMF), session management network element ( session management function (SMF), user plane function (UPF), policy control function (PCF), unified data management network element (UDM), authentication server function entity ( authentication server function (AUSF) and data network module (data network, DN).
  • UE user equipment
  • RAN radio access network
  • AMF access and mobility management function
  • SMF session management network element
  • SMF session management function
  • UPF user plane function
  • PCF policy control function
  • UDM unified data management network element
  • authentication server function entity authentication server function (AUSF)
  • data network module data network, DN.
  • Access and mobility management function Mainly used for mobility management and access management, etc. It can be used to implement mobility management entity (mobility management entity, MME) functions in addition to session management Other functions, such as lawful monitoring and access authorization ⁇ authentication functions.
  • MME mobility management entity
  • Session management function Mainly used for session management, terminal device Internet Protocol (IP) address allocation and management, selection of manageable user plane functions, policy control, and termination of charging function interfaces Point and downlink data notification, etc.
  • IP Internet Protocol
  • UPF User Plane Function
  • the main functions enable data packet routing and forwarding, mobility anchors, and uplink classifiers to support routing traffic to the data network, branch points to support multi-homing PDU sessions, etc.
  • PCF Policy control function
  • Radio access network (Radio access network, (R)AN): It is used to provide network access functions for authorized users in a specific area, and can use transmission tunnels of different quality according to the user's level and service requirements.
  • (R)AN network elements can manage wireless resources, provide access services for terminal devices, and then complete the forwarding of control signals and user data between terminal devices and the core network.
  • (R)AN network elements can also be understood as traditional networks The interface between the base station, AMF network element and RAN equipment is called the N2 interface.
  • Authentication server function (authentication server function, AUSF): mainly used for user authentication, etc.
  • Application function It is used to interact with the 3GPP core network to provide services or services, including interaction with NEF and policy framework interaction.
  • the network exposure function NEF
  • the main functions include: safe and open services and capabilities provided by the 3GPP network function, which are internally open or open to third parties.
  • Translate or translate the information exchanged with AF and internal network function exchange moral information, such as AF service logo and internal 5G core network information such as DNN, S-NSSAI, etc.
  • Network exposure function Used to safely open services and capabilities provided by 3GPP network functions to the outside world.
  • Unified data management used to process user identification, support 3GPP authentication, access authentication, registration, and mobility management.
  • the UE may refer to the description of the terminal device or terminal device in this application, and the terminal device may also be a chip device.
  • a long-term key and related functions are stored in the terminal device or UE.
  • core network elements such as AMF, AUSF
  • each network element such as SMF, AF, UPF, etc.
  • the aforementioned network elements may also have other names, which are not specifically limited in the embodiment of the present application.
  • some or all of the above-mentioned network elements may use the terminology in 5G, or may be named in other ways, etc., which are uniformly explained here and will not be repeated in the following.
  • a non-public network is a system deployed for non-public use.
  • the NPN integrated by the public network may be an NPN network supported and deployed by the public network.
  • the closed access group (CG) technology mainly restricts the UE's access to the cell, and only allowed users (UE) can access the core network and other networks through the CAG cell.
  • the CAG mechanism allows a group of specific users to access one or more cells in a closed access group.
  • the closed access group is used in the NPN network served by the public network, denying the terminal that is not allowed to access the NPN network through the relevant cell.
  • a CAG cell can broadcast one or more CAG IDs, and the CAG ID is the CAG cell identifier.
  • the UE is configured with a CAG list that is allowed to access, that is, a list of CAG IDs of CAG cells that the UE is allowed to access. After the UE receives the broadcast CAG ID, if the received CAG ID is in the list of allowed CAG IDs for the UE, it attempts to access the core network through the current CAG cell.
  • a CAG only (CAG only) indication can also be configured in the UE. This indication is used to indicate that the UE can only access the network through the CAG cell.
  • the UE that can access the network only through the CAG cell is considered to be in the CAG only state, and the CAG only state is also It can be called an empty state.
  • the allowed CAG list of the UE is empty and is set to CAG only, because there is no accessible CAG cell in the UE, and it is set to CAG only, the UE cannot access the network, and the configuration update process cannot be performed. .
  • the UE is only allowed to be used in non-public network scenarios, it is set to CAG only. At the beginning, the UE is allowed to access within the scope of CAG A. However, after a period of time, the tasks within the scope of CAG A are finished, and the CAG A identifier needs to be deleted from the cells that the UE can access. After deletion, there is no accessible CAG cell in the UE. At this time, it is still CAG only, but the UE can no longer access the network.
  • This application defines that the terminal device is not only allowed to access the network through the CAG in the CAG list, that is, the terminal device in this state can still only be allowed to access the network through the CAG, but can use the CAG list that is not allowed to access
  • the CAG cell in, for example, at least one default CAG cell pre-configured for the UE or a default CAG cell issued by the network side to the UE; this state can also be that the terminal device is no longer restricted to access through the CAG cell
  • the network is a non-CAG only (not only CAG) state, and can also be referred to as a non-empty state, and the terminal device can access the network through a non-CAG cell.
  • the configuration data on the network side is that the terminal is only allowed to access the network through CAG, but the terminal device can use other cells that are not in the allowed access CAG list.
  • the configuration data of the UE in this application can also be called configuration information or subscription data or subscription information, including a list of CAG cells that the UE is allowed to access and an indication of whether access is only allowed through CAG, and the list of CAG cells , That is, the CAG list, including the ID of the CAG that the UE is allowed to access.
  • the indication of whether the UE is only allowed to access through CAG includes CAG only and non-CAG only indications.
  • CAG only indicates that the UE is only allowed to access through CAG, and the non-CAG only indication does not limit whether the UE is allowed to access through CAG.
  • the first configuration data in the embodiment of this application includes an empty CAG list and a first restriction indication, the first restriction indication is a CAG only indication;
  • the second configuration data in the embodiment of this application includes a CAG list that is not empty and CAG only indication; or the second configuration data includes a non-CAG only indication, and optionally an empty CAG list.
  • the configuration data sent by the AMF to the UE needs to have integrity protection.
  • the UE receives the message with integrity protection and the integrity check succeeds, the UE updates its configuration data according to the content in the configuration data.
  • Figure 2 is a schematic flow diagram of a method for updating configuration data.
  • the UDM sends the first message to the AMF; when the configuration data for the UE in the UDM is updated to have no accessible CAG cells, that is, the CAG list that allows the UE to access included in the configuration data is empty, and includes the first
  • the UDM sends a first message to the AMF.
  • the first restriction indication is used to configure the status of the UE to CAG only (empty state), that is, it is used to instruct the UE to access the network through CAG.
  • the first message may be a Nudm_SDM_Notification message. Used to notify the AMF that the configuration data of the UE has been updated.
  • the CAG list that the UE is allowed to access at this time that is, the empty CAG list, has not been configured for the UE.
  • the current configuration of the UE still stores the old CAG list, and the old CAG list may not be air.
  • UDM sends the updated configuration data, that is, the first configuration data, to AMF.
  • UDM carries the first configuration data through the first message, that is, carries the allowed CAG list.
  • the CAG list is empty, that is, No CAG ID available;
  • the UDM sends second restriction indication information.
  • the second restriction indication information can also be carried in the first message. After the second restriction indication information is sent to the AMF, it can be sent by the AMF to the UE to indicate that the UE can pass the CAG cell or any cell or any cell that is not in the CAG list.
  • the default cell accesses the network but only allows configuration data updates. UEs are not allowed to request user plane data service requests, and are not allowed to request control plane services that are not related to configuration data updates; UDM can also restrict this second
  • the indication information is included in the first configuration data of the UE or sent to the UE in other forms. The UE in the CAG only state and the CAG list is empty will no longer actively initiate user plane services according to the second restriction indication information.
  • the UE By configuring the UE with the second restriction indication information, the UE no longer actively initiates user plane services, and can only initiate configuration data updates through the network, which reduces the processing of the request information sent by the UE by the network side device, and reduces the network side
  • the device verifies the request information sent by the UE incorrectly and reduces the risk of network security.
  • the second restriction indication information is used to instruct the AMF network element to cancel the mobility restriction check on the UE, or have the above two indication functions at the same time.
  • the AMF receives a first message, and the first message may include the first configuration data permission.
  • the AMF when the AMF confirms that the CAG list in the first configuration data is empty and includes the first restriction indication, that is, the AMF can check whether the current configuration data of the UE on the network side is updated to no accessible CAG.
  • the cell that is, the CAG list is empty
  • the UE is set to CAG only (empty state). If it is, the AMF will no longer perform mobility restriction checks on the UE.
  • the AMF generates the second restriction indication information, or Report the second restriction indication information to UDM to synchronize the related restriction status; it should be noted that the AMF saves the list of CAGs that the UE is allowed to access, and the AMF receives the N2 message sent by the base station.
  • the mobility restriction is: the N2 message contains Information about the CAG cell that the UE accesses.
  • the cell information can be carried in the NAS container or by a specific cell in the N2 message. If the CAG cell the UE currently accesses is not in the allowed CAG list, AMF restricts mobility through mobility Reject the current UE's access request. If the mobility restriction check is cancelled, the AMF receives the UE's access request.
  • the AMF may not need to confirm whether the CAG list is empty, and according to the second restriction indication information, no more mobility restriction check is performed on the UE.
  • the AMF may send the first configuration data to the UE.
  • the first configuration data may not include the CAG only indication.
  • UDM does not include the second restriction indication information in the first configuration data of the UE in step 1
  • AMF can generate and send the second restriction indication information to the UE, that is, the second restriction indication information sent by the AMF to the UE It can be received from UDM, or it can be generated by AMF according to the empty CAG list and the first restriction indication.
  • the second restriction indication information is used to instruct the UE to access the network and only allow configuration data updates, the UE is not allowed to perform user plane data service requests, and is not allowed to request control plane services that are not related to configuration data updates.
  • the AMF may write the second restriction indication information in the context of the UE, and use the second restriction indication information to make the UE in a state where the CAG cell in the allowed CAG list is not restricted to access the network.
  • the AMF can send the first configuration data to the UE by initiating a configuration update process. S204.
  • the UE sends request information to the AMF, where the request information is used to request to update configuration data.
  • the UE receives the second restriction indication information, and optionally, the first configuration data is received, the UE can remain registered, but does not actively initiate user plane service requests or other control plane service requests unrelated to configuration data, allowing Initiate a configuration update to the network side through a CAG cell or any cell or default cell that is not in the CAG list.
  • the UE can maintain the registered state, periodically initiate a service request, and query whether the configuration data for the UE is updated on the network side.
  • the configuration data for the UE in the network side is updated, for example, updated to the second configuration data
  • the AMF allows the service request initiated by the UE to make the UE enter the connected state and complete the configuration update.
  • the UE is no longer restricted to CAG only, and/or the allowed CAG list is not empty.
  • the UE may remain in the registered state, but does not actively perform configuration update queries.
  • the paging process initiated by the network side causes the UE to enter the connected state and complete the configuration update.
  • the AMF When the AMF is in a state where it no longer performs mobility restriction checks on the UE, the AMF allows the UE to access the network through a CAG cell or any cell or default cell that is not in the CAG list. Because the UE has received the second restriction indication information sent by the AMF, the UE will no longer request user plane services and services that are not related to configuration updates, such as location service requests and small data transmission.
  • the AMF restricts the UE’s behavior and only allows the UE to perform registration and configuration updates, but if the UE requests user plane services, such as requesting to establish a session, the AMF rejects the request.
  • AMF rejects the request to further ensure the access restriction to the UE.
  • the context of the UE can be modified to allow only the UE to register and update the configuration data, so that AMF can restrict the behavior of the UE.
  • the AMF After receiving the request message sent by the UE, if the configuration data for the UE in the AMF is updated to the second configuration data, the AMF sends the second configuration data to the UE.
  • the AMF when the CAG list allowed by the configuration data of the UE on the AMF becomes empty and the CAG only indication is set, the AMF does not update the CAG information on the UE and the base station.
  • the AMF uses a specific reason value to reject the NAS request, which is different from the reason value for the UE to delete the CAG ID.
  • the AMF sets all or part of the service area as a non-allowable area, and the AMF only allows the UE to perform configuration updates. In the non-allowed area, the UE will not be allowed to initiate service requests and session management signaling to obtain UE services.
  • the network side configuration information is updated, that is, the configuration information is not "CAG Only and the allowed CAG cell is empty"
  • the AMF moves all or part of the UE's service area out of the non-allowed area.
  • the UE is configured through the AMF, so that the UE can still initiate a configuration update, and at the same time, the mobility restriction check requested by the AMF for the UE is cancelled, and the UE is granted access to the network for configuration update.
  • the UE when the UE has been updated that the CAG list is not empty, the UE is no longer restricted to only allow configuration updates, and resumes normal capabilities within the allowed access CAG cell range, and AMF also resumes mobility restrictions on the UE. Test.
  • FIG. 3 is a schematic diagram of the process of another embodiment of the present application. For related steps and term descriptions in the embodiment shown in FIG. 3, reference may be made to FIG. 2 and corresponding parts in other embodiments.
  • the method shown in Figure 3 includes:
  • the UDM sends a first message to the AMF.
  • the first message may be a Nudm_SDM_Notification message, which is used to notify the AMF that the configuration data of the UE has been updated.
  • UDM sends the updated first configuration data, including the empty CAG list to AMF.
  • the allowed CAG list can be carried in the first message.
  • the CAG list is empty, that is, no CAG ID is available.
  • the CAG list that the UE is allowed to access at this time that is, the empty CAG list, has not been configured for the UE, and the current configuration state of the UE is still the old CAG list; the relevant steps of S301 can also refer to the description of S201.
  • the AMF receives the first message and the allowed CAG list. After the AMF receives the allowed CAG list sent by UDM, it updates the previously stored CAG list of the UE. Because the CAG list is empty, AMF deletes the CAG ID in the previously stored CAG list;
  • the AMF sends the received first configuration data including the empty CAG list to the UE.
  • the AMF configures the UE so that the UE is not only allowed to access the network through the CAG in the list.
  • the AMF sends the ID of the default CAG cell to the UE.
  • the UE is restricted from accessing the network only through the default CAG cell, and the UE is blocked by receiving the default CAG cell. It is configured to not only be allowed to access the network through the CAG in the list, which is not empty.
  • AMF can send the ID of the default CAG cell to the UE through the configuration update process, and use the default CAG cell as the allowed CAG list. The UE can still remain in the CAG only state.
  • the default CAG cell can be configured to only allow the UE to access for configuration data update.
  • the AMF sends first indication information to indicate that the UE is no longer in the CAG only state, that is, the UE is configured to not only be allowed to pass the CAG in the list through the first indication information
  • the UE is no longer in the CAG only state, and an access request can be initiated through a non-allowed CAG cell or other public cell in the PLMN network.
  • the first indication information can be replaced by The first restriction indication (CAG only indication) in the first configuration data is included in the first configuration data and sent to the UE.
  • the UE is configured to not only be allowed to access the network through the CAG in the CAG list by receiving the default CAG ID or receiving the first indication information, and the UE may reply a configuration update complete message to the AMF;
  • the UE After the UE receives the default CAG ID, optionally, if the list of available CAGs also received by the UE is empty, the UE can use the cell corresponding to the default CAG ID to access the network and perform configuration updates.
  • the AMF may initiate a radio resource control (radio resource control, RRC) connection release (connection release) or deregistration process to change the current state of the UE from the connection
  • RRC radio resource control
  • connection release connection release
  • deregistration process to change the current state of the UE from the connection
  • the state becomes the idle state or the de-registered state, so that the UE cannot use other network services and releases the network service resources occupied by the UE.
  • the UE initiates a registration request or service request to the AMF; when a configuration update is required, one implementation is that the UE initiates request information.
  • the request information can be registration request information or service request information to determine whether the configuration data on the network side is There are changes.
  • the registration request information is used to request registration to the network, and the service request information is used to request service.
  • the UE may periodically send registration request information or service request information.
  • the UE may send request information through the special CAG cell;
  • the UE may send a registration request or a service request through a non-allowed CAG cell or another public cell in the PLMN network.
  • the AMF sends the updated CAG list to the UE through a registration request acceptance message or a service request acceptance message.
  • the AMF first obtains the latest configuration data for the UE including the CAG list, and the configuration data of the UE is synchronized between the AMF and the UDM so that the AMF obtains the updated CAG list.
  • AMF can actively send information to UDM to request an updated CAG list, and UDM can also actively send it to AMF synchronously after configuration data such as the CAG list is updated.
  • the UDM sends the allowed (allowed) CAG list to the AMF, carrying the allowed CAG ID.
  • the UDM may also send an indication AMF to indicate that the CAG list in the configuration data is not empty, or not to send the indication, and the AMF determines that it is not empty according to the received CAG list.
  • the configuration data for the UE is updated to the second configuration data
  • AMF accepts the registration request or service request, but in some cases, for example, the security context is inconsistent, the identity credential is SUCI, etc.
  • the primary authentication is triggered; the AMF receives the registration request or service request and sends the second Configure the data to the UE.
  • the second configuration data may also be included in a registration request acceptance message or a service request acceptance message replies to the UE, and the message needs to have integrity protection.
  • the AMF first negotiates the NAS security context with the UE through the NAS SMC process, and then responds to the UE with a confidentiality and integrity protection registration request acceptance message or service request acceptance message.
  • AMF accepts registration requests or service requests, and AMF can be configured as Only allow the UE to request configuration data updates subsequently to prevent the UE from initiating other service requests before completing the configuration data update.
  • the AMF can carry the updated CAG list in the request acceptance message, and can also send the CAG list configuration or cancel the CAG only restriction indication to the UE through the configuration update process.
  • Messages that carry a CAG list or instructions to cancel CAG only restrictions need to have confidentiality and integrity protection.
  • the AMF first negotiates the NAS security context with the UE through the NAS Security Mode Command (SMC, security mode command) process, and then responds to the UE with a message with integrity protection.
  • SMC NAS Security Mode Command
  • the AMF sends rejection information to the UE to reject the registration request or the service request.
  • the rejection message carries the second configuration data; a cause value can also be sent, and the cause value is used to instruct the UE to update the CAG list.
  • Messages that carry CAG list or cancellation of CAG only restrictions or Cause values need to have integrity protection.
  • the AMF directly uses the security context to protect the integrity of the message.
  • the AMF first negotiates the NAS security context with the UE through the NAS SMC process, and then replies to the UE with a rejection message with integrity protection.
  • the AMF When the AMF receives the configuration update complete message sent by the UE, optionally, the AMF initiates an RRC connection release or deregistration process, so that the UE releases network resources. When the UE needs to re-access to the network, it needs to select the CAG cell according to the updated configuration information. The base station and AMF will perform mobility verification based on the updated configuration information.
  • the S307 UE actively initiates a registration request or service request message.
  • the UE is in an idle state, and when the configuration data on the AMF is updated to the second configuration data, the AMF actively pages the UE. To update the configuration data on the UE.
  • the UE by configuring the UE, for example, assigning a default or special CAG cell ID, the UE can update the configuration data through the default CAG cell and the network side, or cancel the CAG ONLY state of the UE, so that the UE It can access the network with a non-CAG cell to update the configuration.
  • the default CAG cell is not included in the CAG list, and can also be used as a default configured CAG cell as a part of the CAG list stored by the UE.
  • Fig. 4 is a schematic diagram of the flow of another configuration data update method.
  • the method shown in Figure 4 includes:
  • the configuration data management device confirms that the configuration data of the UE is changed from CAG only, allowed CAG list is not empty, allowed CAG list is empty and no CAG only restriction, or allowed CAG list is not empty and no CAG only restriction is changed to CAG only, When the allowed CAG list is empty first configuration data, the first configuration data whose CAG is only and the allowed CAG list is empty is not sent to the UE.
  • the configuration data management device is AMF
  • AMF updates the UE's configuration data from UDM.
  • the UE's configuration data is indicated by CAG only restriction
  • the allowed CAG list is not empty or the allowed CAG list is empty and there is no CAG only restriction indication, or
  • the allowed CAG list is not empty and there is no CAG only restriction indication is transformed into the first configuration data
  • the first configuration data includes the first restriction indication and an empty CAG list, and the first restriction indication may be CAG
  • the only restriction indication is used to instruct the UE to access the network through the closed access group CAG.
  • the AMF deletes the old CAG ID in the stored UE configuration data and/or adds a CAG only restriction indication.
  • the AMF configures the UE so that the UE is not only allowed to access the network through the CAG in the CAG list;
  • the AMF does not send the updated first configuration data that the CAG list is empty to the UE, so that the non-empty CAG list stored in the UE will not be replaced by the empty CAG in the first configuration data.
  • the list is replaced, so that the UE is not only allowed to access the network through the empty CAG list in the first configuration data; optionally, in order to restrict the behavior of the UE, the AMF sets all or part of the service area to In the non-allowed area, the AMF only allows the UE to perform configuration updates. In the non-allowed area, the UE will not be allowed to initiate service requests and session management signaling to obtain UE services.
  • the network side configuration information is updated, that is, the configuration data is not a CAG Only restriction indication and the allowed CAG cell is empty, the AMF moves all or part of the UE's service area out of the non-allowed area.
  • the AMF removes the first restriction indication in the first configuration data, the AMF sends the first configuration data for removing the first restriction indication to the UE, and the removal of the first restriction indication
  • the first configuration data of is used to configure that the terminal device is no longer only allowed to access the network through CAG, that is, the UE is in the non-CAG only state; the AMF can replace the first restriction indication with the non-CAG only indication, and set the non-CAG
  • the only indication is included in the configuration data and sent to the UE together with the empty CAG list.
  • the AMF sends first indication information to the terminal device, where the first indication information is used to indicate that the terminal device is no longer only allowed to access the network through CAG.
  • the UMD When the configuration data management device is UDM, the UMD does not perform the UE configuration update process, and the UDM blacklists the user permanent identifier (subscription permanent identifier, SUPI) corresponding to the UE, and does not allow the UE to register in the network.
  • the user permanent identifier subscription permanent identifier, SUPI
  • the configuration data management apparatus triggers an RRC connection release or deregistration process, so that the network service resources occupied by the UE are released.
  • the UE sends a request message, which can be a registration request or a service request; when the UE receives the complete first configuration data, the current configuration data of the UE itself is still the old configuration data, that is, CAG only, allowed CAG list Is the old CAG ID, or the allowed CAG list is empty and has no CAG only restriction, or the allowed CAG list is the old CAG ID and has no CAG only restriction; or the configuration data with the first restriction indication removed, or received
  • the first indication information makes the UE in the non-CAG only state; and the configuration data in the configuration data management device, such as AMF or UDM, includes: CAG only, and the allowed CAG list is empty.
  • the UE still stores the available CAG ID or is in a non-CAG only state.
  • the UE periodically or randomly sends access registration requests or service requests through available CAG cells, or the UE periodically or randomly sends access requests through non-CAG cells. Enter the registration request or service request.
  • the AMF after receiving the request message sent by the UE, when the configuration data stored by the configuration data management device is not updated, that is, it is still CAG only, the allowed CAG list is empty, and the configuration data management device is AMF , The AMF will perform a mobility restriction check, and send a rejection message including a second reason value to the UE to reject the UE's request.
  • the second reason value is used to instruct the UE not to delete the CAG list stored by the UE.
  • AMF needs to keep the configuration data synchronized with UMD.
  • UDM can actively or be requested by AMF to send the latest configuration data of UE stored in UDM to AMF; if the configuration data management device is UDM, because the SUPI of the UE is still in UDM In the blacklist of, even if in the previous step, UDM did not send the configuration data with the most empty CAG list to AMF, and the AMF passed the mobility check, the UE could not be successfully registered;
  • the configuration data stored by the configuration data management apparatus when the configuration data stored by the configuration data management apparatus is updated, that is, the configuration information of the UE changes from CAG only, allowed CAG list to non-CAG only, or allowed CAG list to be non-empty.
  • AMF receives the registration request or service request from the UE.
  • UDM removes the SUPI corresponding to the UE from the blacklist, completing the normal registration process, and AMF will update the configuration
  • the information is sent to the UE through a registration request acceptance message or a service request acceptance message.
  • S307 For specific steps, please refer to S307, which will not be repeated here.
  • the AMF sends rejection information to the UE to reject the registration request or service request.
  • the rejection message carries the second configuration data; it may also send a first reason value, and the first reason value is used to instruct the UE to update the CAG list.
  • the configuration data management apparatus can accept the request message sent by the UE without sending updated configuration data to the UE.
  • Fig. 5 is a schematic diagram of a process in another embodiment of the present application.
  • the method shown in Figure 5 includes:
  • the UDM sends a first message to the AMF.
  • the first message may be a Nudm_SDM_Notification message, which is used to notify the AMF that the configuration data of the UE has been updated.
  • UDM sends the updated configuration data, that is, the empty CAG list to AMF.
  • the first message can carry the allowed CAG list and the CAG only indication.
  • the CAG list is empty, that is, no CAG list is available.
  • CAG ID It should be noted that the CAG list that the UE is allowed to access at this time, that is, the empty CAG list, and the CAG only restriction indication has not been configured for the UE, and the current configuration state of the UE is still the old CAG list or no_CAG_only.
  • allowed CAG list is When the UE configuration information in UDM is changed from CAG only, allowed CAG list is not empty, allowed CAG list is empty and no CAG only restriction, or allowed CAG list is not empty and no CAG only restriction is changed to CAG only, allowed CAG list is
  • UDM blacklists the SUPI corresponding to the UE and does not allow the UE to register in the network.
  • the first message may also carry a de-registration indication, which is used to instruct the AMF to perform a de-registration process after completing the configuration update process of the UE, thereby releasing the UE's network resources.
  • the CAG only restriction indication of the UE is changed to a non-CAG only indication, so that the UE can no longer be restricted to only access the network through the CAG cell.
  • the AMF receives a first message, and the first message may include a list of allowed CAGs and a non-CAG only indication.
  • the allowed CAG list sent by UDM it updates the previously stored CAG list of the UE. Because the CAG list is empty, AMF deletes the CAG ID in the previously stored CAG list; in addition, AMF can delete the received CAG list.
  • the CAG list is sent to the UE.
  • the AMF configures the UE so that the UE is not only allowed to access the network through the CAG in the list.
  • AMF sends a non-CAG only indication.
  • the UE is configured to be not only allowed to access the network through the CAG in the list.
  • the UE is no longer in the CAG only state. Initiate an access request to a non-CAG cell.
  • the UE receives a non-CAG only indication and an empty CAG list.
  • the UE is configured to not only be allowed to access the network through the CAG in the list and is not empty.
  • the UE may reply a configuration update complete message to the AMF;
  • the AMF may initiate a radio resource control (radio resource control, RRC) connection release (connection release) or deregistration process to change the current state of the UE from the connection
  • RRC radio resource control
  • connection release connection release
  • deregistration process to change the current state of the UE from the connection
  • the state becomes the idle state or the de-registered state, so that the UE cannot use other network services and releases the network service resources occupied by the UE.
  • the UE initiates a registration request or service request to the AMF; when a configuration update is required, one implementation is that the UE initiates registration request information or service request information to determine that the configuration data release on the network side has changed, and the registration request information is used for Request registration to the network, and service request information is used to request service.
  • the UE may periodically send registration request information or service request information.
  • the UE may send a registration request or service request through a non-CAG cell.
  • the SUPI corresponding to the UE is in the UDM blacklist, and the configuration information of the UE stored in the UDM is still CAG only and the allowed CAG list is empty, it can be considered that the configuration data has not been updated because the SUPI corresponding to the UE is still in In the UDM blacklist, the UE cannot successfully register with AMF; when the configuration information of the UE changes from CAG only, allowed CAG list to non-CAG only, or allowed CAG list is not empty, the corresponding SUPI is removed from the blacklist. This allows the UE to perform normal registration procedures.
  • the AMF sends the updated CAG list to the UE through a registration request acceptance message or a service request acceptance message.
  • the AMF first obtains the latest CAG list, and the UE's subscription data is synchronized between the AMF and UDM so that the AMF obtains new configuration information or subscription data that includes the latest CAG list.
  • AMF can send information to UDM to actively request the updated CAG list, and UDM can also actively send it to AMF synchronously after configuration data such as the CGA list is updated.
  • UDM sends the allowed CAG list to AMF, carrying the allowed CAG ID.
  • the UDM may also send an indication AMF to indicate that the CAG list in the configuration data is not empty, or not to send the indication, and the AMF determines that it is not empty according to the received CAG list.
  • the configuration data of the UE changes from CAG only, allowed CAG list to CAG only, allowed CAG list is not empty, the SUPI corresponding to the UE is removed from the UDM blacklist, so that the UE can perform the normal registration process, and the AMF accepts the registration Request or service request, but in some cases, such as the security context is inconsistent, the identity certificate is SUCI, etc., the main authentication is triggered; the AMF receives the registration request or service request, and sends new subscription data to the UE.
  • the new subscription data includes The updated CAG list.
  • the subscription data may also be included in the registration request acceptance message or service request acceptance message returned to the UE.
  • the configuration data of the UE changes from CAG only, allowed CAG list to CAG only, allowed CAG list is not empty, AMF and UDM only accept registration requests or service requests, and AMF can be configured to only allow subsequent requests from the UE
  • the configuration data is updated to prevent the UE from initiating other service requests before completing the configuration data update.
  • the AMF can carry the updated CAG list in the message of accepting the request, or it can send the configured CAG list to the UE through the configuration update process.
  • the configuration data of the UE is changed from CAG only, allowed CAG list to CAG only, and allowed CAG list is not empty.
  • AMF sends rejection information to UE to reject Registration request or service request.
  • the rejection message carries a new allowed CAG list; it can also send a Cause value, which is used to instruct the UE to update the CAG list.
  • the AMF initiates an RRC connection release or deregistration process, so that the UE releases network resources.
  • the S307 UE actively initiates a registration request or service request message.
  • the UE is in the idle state, and the configuration information on the AMF changes from CAG only, allowed CAG list to CAG only.
  • the allowed CAG list is not empty, AMF proactively page the UE and update the configuration data on the UE.
  • the CAG only state of the UE is cancelled, so that the UE can access the network with non-CAG cells for configuration updates, and UDM adds the UE's SUPI to the blacklist, so that the UE cannot pass the non-CAG cell.
  • CAG is normally connected to the network and can only be used for configuration updates.
  • the embodiments of the present application also provide a device for implementing any of the above methods.
  • a device is provided that includes units (or means) for implementing each step performed by the terminal device in any of the above methods.
  • another device is also provided, including a unit (or means) for implementing each step performed by the session management network element in any of the above methods.
  • FIG. 6 is a schematic diagram of an apparatus for updating configuration data provided by an embodiment of the application.
  • the device is used to perform various steps performed by the UE in any method embodiment of the present application.
  • This device is used for terminal equipment.
  • the device 600 includes a processing unit 610, a receiving unit 620, and a sending unit 630.
  • the processing unit 610 is used to update configuration data;
  • the receiving unit 620 is used to receive instructions sent by the network side, or restriction instructions or restriction information, or configuration data, or reason values, or configuration update messages, or rejection messages, or acceptance Messages, or related messages in the link release process, etc.;
  • the sending unit 630 is configured to send messages or information to the network side, including request messages, configuration update reply messages, and so on. It may also include a storage unit for storing configuration data and other information.
  • FIG. 7 is a schematic diagram of another device for updating configuration data provided by an embodiment of the application.
  • the device is used to perform each step performed by AMF or UDM in any method embodiment of the present application.
  • the device 700 includes a processing unit 710, a receiving unit 720, and a sending unit 730.
  • the processing unit 710 is configured to determine that the configuration data of the terminal device is the first configuration data, and to determine that the configuration data is updated to the second configuration data; it can also be used to configure the terminal device to be in a list that is not only allowed to pass the CAG The state of CAG access to the network, and is used to remove the restriction indication in the configuration message, or replace the restriction indication in the configuration message.
  • the receiving unit 720 is used to receive configuration data from UDM; the sending unit 730 is used to send configuration data to the terminal device.
  • the processing unit 710 is further configured to determine that the first configuration data does not occur to the terminal device.
  • the receiving unit 720 is used to receive a request message sent by the terminal device, and the sending unit 730 is used to send an accept message or a rejection message to accept or reject the request message.
  • the sending unit 730 is used to configure update messages; and send related messages in the connection release procedure.
  • the processing unit 710 is further configured to use the NAS security context to protect the confidentiality and/or integrity of the rejection message or the configuration update message.
  • the sending unit 730 is also used to send a reason value, a restriction indication, and other indication messages.
  • the second retention time is greater than the first retention time, and the second retention time is not less than a preset second threshold.
  • the device may also include a storage unit for storing configuration data.
  • each unit in the device can be all implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; part of the units can also be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware.
  • each unit can be a separate processing element, or it can be integrated in a certain chip of the device for implementation.
  • it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the device.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.
  • the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASICs), or, one or Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs), or a combination of at least two of these integrated circuits.
  • ASICs application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs Field Programmable Gate Arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above receiving unit is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device for sending signals to other devices.
  • the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the application.
  • the terminal device is used to implement the operation of the terminal device in the above embodiment.
  • the terminal equipment includes: an antenna 810, a radio frequency device 820, and a signal processing part 830.
  • the antenna 810 is connected to the radio frequency device 820.
  • the radio frequency device 820 receives the information sent by the access network device through the antenna 810, and sends the information sent by the access network device to the signal processing part 830 for processing.
  • the signal processing part 830 processes the information of the terminal equipment and sends it to the radio frequency device 820
  • the radio frequency device 820 processes the information of the terminal equipment and sends it to the access network equipment via the antenna 1310.
  • the signal processing part 830 is used to realize the processing of each communication protocol layer of the data.
  • the signal processing part 830 may be a subsystem of the terminal device, and the terminal device may also include other subsystems, such as a central processing subsystem, which is used to process the terminal device operating system and application layer; another example is the peripheral sub-system.
  • the system is used to realize the connection with other equipment.
  • the signal processing part 830 may be a separately provided chip.
  • the above devices may be located in the signal processing part 830.
  • the signal processing part 830 may include one or more processing elements 831, for example, a main control CPU and other integrated circuits.
  • the signal processing part 830 may also include a storage element 832 and an interface circuit 833.
  • the storage element 832 is used to store data and programs.
  • the program used to execute the method executed by the terminal device in the above method may or may not be stored in the storage element 832, for example, stored in a memory other than the signal processing part 830 During use, the signal processing part 830 loads the program into the cache for use.
  • the interface circuit 833 is used to communicate with the device.
  • the above devices may be located in the signal processing part 830, which may be implemented by a chip.
  • the chip includes at least one processing element and an interface circuit.
  • the processing element is used to execute each step of any method executed by the above terminal device.
  • the circuit is used to communicate with other devices.
  • the unit that implements each step in the above method can be implemented in the form of a processing element scheduler.
  • the device includes a processing element and a storage element, and the processing element calls a program stored by the storage element to execute the above method embodiments.
  • the storage element may be a storage element whose processing element is on the same chip, that is, an on-chip storage element.
  • FIG. 9 is a schematic structural diagram of a device provided by an embodiment of this application, which is used to implement the operations of the AMF network element or UDM netizen in the above embodiment.
  • it when it is an AMF network element, it includes: a processor 910, a memory 920, and an interface 930, and the processor 910, the memory 920, and the interface 930 are signally connected.
  • the method executed by the AMF network element in the above embodiment can be implemented by the processor 1410 calling a program stored in the memory 1420. That is, the device for AMF includes a memory and a processor, and the memory is used to store a program, which is called by the processor to execute the method executed by the AMF network element in the above method embodiment.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • the apparatus for the session management network element may be realized by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or, one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementations can be combined.
  • the embodiment of the present application also provides a system, which may include AMF and UDM. Optionally, it also includes RAN and UE.
  • the processor and transceiver described in this application can be implemented in integrated circuit (IC), analog IC, radio frequency integrated circuit RFIC, mixed signal IC, application specific integrated circuit (ASIC), printed circuit board ( printed circuit board, PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various 1C process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), and P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS nMetal-oxide-semiconductor
  • PMOS bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the device is described with AMF or UDM or terminal device as an example, the scope of the device described in this application is not limited to the access network device or terminal device, and the structure of the device may not be attached. Limitations of the graph.
  • the device can be a stand-alone device or can be part of a larger device.
  • the device may be:
  • the IC collection may also include storage components for storing data and/or instructions;
  • ASIC such as modem (MSM)
  • system and “network” in this article are often used interchangeably in this article.
  • the term “and/or” in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations.
  • the character "/" in this text generally means that the associated objects before and after are in an "or” relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B based on A does not mean that B is determined only based on A, and B can also be determined based on A and/or other information.
  • computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • machine-readable medium may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种更新配置数据的方法、装置和系统，其中该方法包括：当针对终端装置的配置数据为第一配置数据时，所述第一配置数据包括第一限制指示和空的封闭接入组CAG列表，所述第一限制指示用于指示所述终端装置通过封闭接入组CAG接入网络，所述CAG列表为允许所述终端装置接入的CAG ID的集合，接入与移动性管理功能装置配置所述终端装置处于并非只被允许通过所述CAG列表中的CAG接入网络的状态；当针对所述终端装置的所述配置数据更新为第二配置数据，其中所述第二配置数据中的CAG列表不为空或者不包括所述第一限制指示，所述接入与移动性管理功能装置发送所述第二配置数据给所述终端装置。

Description

更新配置数据的方法、装置和系统 技术领域
本申请涉及通信技术领域，并且更具体地，涉及一种更新配置数据的的方法、装置和系统。
背景技术
封闭接入组(closed access group，CAG)技术主要限制UE对小区的接入，只有允许接入的用户可以通过CAG小区接入核心网。接入网设备可以广播一个或者多个CAG ID，CAG ID为CAG小区标识。UE配置有一个允许接入的CAG列表，比如一个UE允许接入的CAG ID的列表。当UE收到广播的CAG ID后，如果在自己允许的CAG ID列表中，则尝试通过当前CAG小区接入核心网。UE中还可以配置一个CAG Only指示，该指示约束UE只可以通过CAG小区接入网络系统。
当UE允许的CAG列表为空，并且被设置为CAG only，因UE中无可接入的CAG小区，同时被设置为CAG only，UE再也无法接入到网络当中，也无法进行配置更新流程。
发明内容
本申请提供一种一种更新配置数据的方法及装置，用以实现对UE的配置更新。
第一方面，本申请提供一种更新配置数据的方法，包括：
当针对终端装置的配置数据为第一配置数据时，所述第一配置数据包括第一限制指示和空的封闭接入组CAG列表，所述第一限制指示用于指示所述终端装置通过封闭接入组CAG接入网络，所述CAG列表为允许所述终端装置接入的CAG ID的集合，接入与移动性管理功能装置配置所述终端装置处于并非只被允许通过所述CAG列表中的CAG接入网络的状态；
当针对所述终端装置的所述配置数据更新为第二配置数据，其中所述第二配置数据中的CAG列表不为空或者不包括所述第一限制指示，所述接入与移动性管理装置发送所述第二配置数据给所述终端装置。
在一种可能的实现方法中，所述接入与移动性管理功能装置发送移除所述第一限制指示的第一配置数据给所述终端装置，所述移除所述第一限制指示的第一配置数据用于配置所述终端装置不再只被允许通过CAG接入网络。
在一种可能的实现方法中，所述接入与移动性管理功能装置不发送所述第一配置数据给所述终端装置，所述空的CAG列表用于替换所述终端装置所存的不为空的CAG列表。
在一种可能的实现方法中，所述移除所述第一限制指示的第一配置数据中包括第一指示信息，所述第一指示信息用于指示所述终端装置不再只被允许通过CAG接入网络。
在一种可能的实现方法中，所述接入与移动性管理功能装置发送至少一个默认CAG的标识给所述终端装置，所述默认CAG用于所述终端装置更新配置数据。
在一种可能的实现方法中，所述接入与移动性管理装置使用NAS安全上下文对所述 拒绝消息或配置更新消息进行机密性和/或完整性保护。
在一种可能的实现方法中，所述接入与移动性管理装置中的NAS安全上下文不可用时，所述接入与移动性管理装置激活NAS安全上下文后，发送所述第二配置数据。
通过对UE进行配置，例如分配一个默认或特殊的CAG小区ID，使得UE可以通过该默认CAG小区和网络侧进行配置数据更新，或者取消UE的CAG only状态，使得UE可以同非CAG小区接入网络来进行配置更新。需要说明的是，该默认CAG小区不包含在CAG列表中，也可以作为一个默认配置的CAG小区，作为UE存储的CAG列表中的一部分。
第二方面，本申请提供一种更新配置数据的方法，其特征在于，包括：
当针对终端装置的配置数据为第一配置数据，所述第一配置数据包括第一限制指示和空的封闭接入组CAG列表，所述第一限制指示用于指示所述终端装置通过封闭接入组CAG接入网络，所述CAG列表为允许所述终端装置接入的CAG ID的集合，所述终端装置被配置为并非只被允许通过所述CAG列表中的CAG接入网络的状态；当针对所述终端装置的所述配置数据更新为第二配置数据，其中所述第二配置数据中的CAG列表不为空或者不包括所述第一限制指示，所述终端装置接收来自所述接入与移动性管理装置的第二配置数据。
第三方面，本申请提供另一种更新配置数据的方法，其特征在于，包括：
当配置数据管理装置中的针对终端装置的配置数据为第一配置数据时，所述第一配置数据包括第一限制指示和空的封闭接入组CAG列表，所述第一限制指示用于指示所述终端装置通过封闭接入组CAG接入网络，所述CAG列表为允许所述终端装置接入的CAG ID的集合，配置数据管理装置不将所述空的CAG标识列表发送给所述终端装置；
当针对所述终端装置的所述配置数据更新为第二配置数据，其中所述第二配置数据中的CAG列表不为空或者不包括所述第一限制指示，所述接入与移动性管理装置发送所述第二配置数据给所述终端装置。
在一种可能的实现方法中，所述配置数据管理装置为统一数据管理网元，当所述统一数据管理网元中的配置数据为所述第一配置数据，所述统一数据管理网元将所述终端装置的标志加入黑名单，禁止所述终端装置接入网络；当所述统一数据管理网元中的配置数据更新为所述第二配置数据，所述统一数据管理网元将所述将所述终端装置的标识移出所述黑名单。
在一种可能的实现方法中，所述所述配置数据管理装置为统一数据管理网元，所述统一数据管理网元发送第二限制指示信息给接入与移动性管理功能装置。
在一种可能的实现方法中，，所述所述配置数据管理装置为统一数据管理网元，所述统一数据管理网元移除第一配置数据中的所述第一限制指示后发送给所述接入与移动性管理功能装置。
第四方面，本申请提供一种更新配置数据的装置，该装置可以是终端设备，还可以是用于终端设备的芯片。该装置具有实现上述第三方面各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，本申请提供一种更新配置数据的装置，该装置可以是接入与移动性管理功能装置，还可以是用于接入与移动性管理功能网元的芯片。该装置具有实现上述第一方面 或第一方面以及第三方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，本申请提供一种更新配置数据的装置，该装置可以是统一数据管理网元，还可以是用于统一数据管理网元的芯片。该装置具有实现上述第三方面或第三方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，本申请提供一种更新配置数据的装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述各方面所述的方法。该装置可以是终端设备、或用于终端设备的芯片、或接入与移动性管理网元、或用于接入与移动性管理的芯片、或统一数据管理网元、或用于统一数据管理的芯片。
第八方面，本申请提供一种更新配置数据的装置，包括：包括用于执行上述各方面的各个步骤的单元或手段(means)。该装置可以是接入与移动性管理网元、或终端设备、或统一数据管理网元。
第九方面，本申请提供一种更新配置数据的确定装置，包括处理器和接口电路，所述处理器用于通过接口电路实现上述各方面所述的方法。该处理器包括一个或多个。该装置可以是用于接入与移动性管理网元、或终端设备、或统一数据管理网元的芯片。
第十方面，本申请提供一种更新配置数据的装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行上述各方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。该装置可以是终端设备、或用于终端设备的芯片、或接入与移动性管理网元、或用于接入与移动性管理网元、或统一数据管理网元、或用于统一数据管理网元的芯片。
第十一方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得处理器执行上述各方面所述的方法。
第十二方面，本申请还提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十三方面，本申请还提供一种芯片系统，包括：处理器，用于执行上述各方面所述的方法。
附图说明
图1为本申请适用的一种可能的网络架构示意图；
图2为本申请提供的一种更新配置数据的方法流程示意图；
图3为本申请提供的又一种更新配置数据的方法流程示意图；
图4为本申请提供的又一种更新配置数据的方法流程示意图；
图5为本申请提供的又一种更新配置数据的方法流程示意图；
图6为本申请提供的一种更新配置数据的装置示意图；
图7为本申请提供的又一种更新配置数据的装置示意图。
图8为本申请提供的一种终端设备示意图；
图9为本申请提供的一种更新配置数据的装置结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通信(global system for mobile communications，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)系统或新无线(new radio，NR)等、以及在未来可能出现的通信系统中。
本申请实施例中的终端装置可以指芯片、用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端装置还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端装置或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端装置等，本申请实施例对此并不限定。
本申请实施例中的核心网(core network，CN)设备可以是终端装置的控制面锚点，为终端提供注册区(registration area)更新等功能。例如，核心网装置可以包括接入及移动性管理功能实体(access and mobility management function，AMF)。核心网装置可以用于为终端提供核心网接入(core access)以及移动性管理等功能的网络设备。核心网装置的具体功能可以类似于LTE系统中的移动性管理实体(mobility management entity，MME)的功能。
本申请实施例中的接入网装置可以是用于与终端装置通信的设备，该接入网装置可以是无线接入网(radio access network，RAN)设备。RAN设备可以包括各种类型的基站。例如，本申请实施例的基站可包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具有基站功能的设备的名称可能会有所不同。例如在LTE网络中，称为演进的节点B(evolved NodeB，eNB或eNodeB)，在第三代(3rd generation，3G)网络中，称为节点B(Node B)等等。在第五代(5th generation，5G)网络中，可以称为g节点(g Node B，gNB)等，本申请实施例并不限定。
另外，在本申请实施例中，接入网络设备为小区提供服务，终端装置通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信。该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小和发射功率低的特点，适用于提供高速率的数据传输服务。
本申请实施例的技术方案具体可以应用在5G系统中，下面结合图1对5G系统进行介绍。
图1是5G系统的架构示意图。
图1所示的系统架构包括用户设备(user equipment，UE)、无线接入网络(radio access network RAN)、接入和移动管理网元(access and mobility management function，AMF)、会话管理网元(session management function，SMF)、用户面网元(user plane function，UPF)、策略控制网元(policy control function，PCF)、统一数据管理网元(unified data management，UDM)、鉴权服务器功能实体(authentication server function，AUSF)以及数据网络模块(data network，DN)。
其中，图1所示的系统架构中的核心网中的设备的主要作用如下：
接入和移动管理功能(access and mobility management function，AMF)：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如合法监听以及接入授权\鉴权等功能。
会话管理功能(session management function，SMF)：主要用于会话管理、终端装置的网络互连协议(Internet Protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
用户平面功能(User Plane Function，UPF)：主要功能使数据包路由和转发、移动性锚点、上行分类器来支持路由业务流到数据网络、分支点来支持多归属PDU会话等。
策略控制网元(policy control function，PCF)：主要功能是策略决策点，提供基于业务数据流和应用检测，门控，QoS和基于流的计费控制等规则。
(无线)接入网络(radio access network，(R)AN)：用于为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道。(R)AN网元能够管理无线资源，为终端装置提供接入服务，进而完成控制信号和用户数据在终端装置和核心网之间的转发，(R)AN网元也可以理解为传统网络中的基站，AMF网元与RAN设备之间的接口称为N2接口。
认证服务功能(authentication server function，AUSF)：主要用于用户鉴权等。
应用功能(application function，AF)：用于与3GPP核心网交互提供业务或者服务，包括与NEF交互，策略架构交互等。其中，网络开放功能(network exposure function，NEF)，主要功能包括：安全的开放3GPP网络功能提供的业务和能力，有内部开放，或者开放给第三方等。转化或翻译与AF交互的信息和内部网络功能交互德行信息，如AF服务标识和内部5G核心网信息如DNN，S-NSSAI等。
网络开放功能(network exposure function，NEF)：用于安全地向外部开放由3GPP网络功能提供的业务和能力等。
统一数据管理(unified data management，UDM)：用于处理用户标识，支持3GPP认证、，接入鉴权，注册以及移动性管理等。
UE可参考本申请关于终端装置或终端设备的描述，终端装置也可以为一种芯片装置。此外，该终端装置或UE中存储有长期密钥，和相关函数。UE在与核心网网元(如AMF、AUSF)进行双向鉴权的时候，会使用长期密钥和相关函数验证网络的真实性。
需要说明的是，图1中包括的各个网元(比如SMF、AF、UPF等)的命名仅是一个名字，名字对网元本身的功能不构成限定。在5G网络以及未来其它的网络中，上述各个网元也可以是其他的名字，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能是其他命名，等等，在此进行统 一说明，以下不再赘述。
应理解，上述应用于本申请实施例的网络架构仅是举例说明描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
非公共网络(non-public network,NPN)是部署的非公共用途的系统。由公网集成的NPN可以是由公共网络提供支持部署的NPN网络。封闭接入组(closed access group，CAG)技术主要限制UE对小区的接入，只有允许接入的用户(UE)可以通过CAG小区接入核心网等网络。CAG机制允许一组特定用户接入一个或多个封闭接入组的小区。封闭接入组用在由公共网络提供服务的NPN网络中，拒绝不被允许的终端通过相关小区接入NPN网络。一个CAG小区可以广播一个或者多个CAG ID，CAG ID为CAG小区标识。UE配置有一个允许接入的CAG列表，即该UE允许接入的CAG小区的CAG ID的列表。当UE收到广播的CAG ID后，如果接收到的CAG ID在UE所该允许的CAG ID列表中，则尝试通过当前CAG小区接入核心网。UE中还可以配置一个CAG only(仅CAG)指示，该指示用于指示UE只可以通过CAG小区接入网络，只可以通过CAG小区接入网络的UE被认为处于CAG only状态，CAG only状态也可以称为空状态。当UE被允许的CAG列表为空，并且被设置为CAG only，因UE中无可接入的CAG小区，同时被设置为CAG only，UE则无法接入到网络当中，也无法进行配置更新流程。
如果UE仅被允许在非公共网络场景中使用，被设置为CAG only。开始时，UE允许在CAG A的范围内进行接入。但是一段时间后，在CAG A范围的任务结束，需要将UE可以接入的小区中删除CAG A的标识。删除后，UE中无可接入的CAG小区，此时依然为CAG only，但UE无法再接入到网络当中。本申请定义了终端装置并非只被允许通过CAG列表中的CAG接入网络的状态，即处于该状态的终端装置可以依然只被允许通过CAG接入网络，但可以使用不在所允许接入CAG列表中的CAG小区，例如使用预先配置给UE的至少一个默认CAG小区的或由网络侧下发给UE的默认CAG小区；该状态也可以为，终端装置不再被限制为必须通过CAG小区接入网络，即为non CAG only(非仅CAG)状态，也可称为非空状态，终端装置可以通过非CAG小区接入网络。处于该状态的终端装置，网络侧的配置数据为所述终端只被允许通过CAG接入网络，但终端装置可以使用不在所允许接入CAG列表中的其他小区。
本申请中的UE的配置数据，也可以被称为配置信息或签约数据或签约信息，包括允许UE接入的CAG小区的列表和是否只被允许通过CAG接入的指示，该CAG小区的列表，即CAG列表，包括允许UE接入的CAG的ID。是否只被允许通过CAG接入的指示，包括CAG only和non CAG only指示，CAG only指示UE只被允许通过CAG接入，non CAG only指示不限定UE是否通过CAG接入。
本申请实施例中的第一配置数据，包括空的CAG列表和第一限制指示，第一限制指示为CAG only指示；本申请实施例中的第二配置数据，包括不为空的CAG列表和CAG only指示；或者第二配置数据包括non CAG only指示，可选的还包括空的CAG列表。
当AMF要修改UE上的CAG信息时，AMF向UE发送的配置数据需要有完整性保护。UE收到有完整性保护的消息并且完整性校验成功时，UE根据配置数据中的内容更新自身的配置数据。
图2是一种配置数据更新的方法流程示意图。
S201.UDM向AMF发送第一消息；当UDM中针对UE的配置数据更新为无可接入的CAG小区，即该配置数据中所包括的允许UE接入的CAG列表为空，以及包括第一限制指示时，UDM向AMF发送第一消息，第一限制指示用于配置UE的状态为CAG only(空状态)，即用于指示UE通过CAG接入网络,该第一消息可以为Nudm_SDM_Notification消息，用于通知AMF该UE的配置数据有更新。需要说明的时，此时的允许UE接入的CAG列表，即空的CAG列表，尚未配置给UE，UE当前的自身的配置存储的依然为旧的CAG列表，该旧的CAG列表可以不为空。
UDM发送更新的后的配置数据，即第一配置数据给AMF，可选的，UDM通过该第一消息携带该第一配置数据，即携带允许的CAG列表，此时的CAG列表为空，即无可用的CAG ID；
此外，可选的，UDM发送第二限制指示信息。该第二限制指示信息也可携带在第一消息中，该第二限制指示信息发送给AMF后，可以由AMF发送给UE，用于指示UE可以通过不在CAG列表中的CAG小区或任意小区或默认小区接入网络但只允许进行配置数据更新，UE不被允许请求用户面数据业务请求，以及不被允许请求控制面业务中与配置上数据更新无关的业务；UDM也可以将该第二限制指示信息包括在UE的第一配置数据中，或通过其它形式发送给UE，处于CAG only状态且CAG列表为空的UE根据第二限制指示信息，不再主动发起用户面业务。通过对该第二限制指示信息配置UE，使得该UE不再主动发起用户面业务，只能通过网络发起配置数据更新，减少了网络侧装置对UE发送的请求信息的处理，减少了因网络侧装置对UE发送的请求信息校验错误而使得网络安全性降低的风险。
此外，在另一种实施方式中，该第二限制指示信息用于指示AMF网元取消对UE的移动性限制校验，或者同时具有上述两种指示作用。
S202、AMF收到第一消息，该第一消息中可以包括允第一配置数据。
在一种实施方式中，当AMF确认第一配置数据中的CAG列表为空，以及包括第一限制指示，即AMF可以校验网络侧当前对UE的配置数据是否更新为无可接入的CAG小区(即CAG列表为空)且UE被设置为CAG only(空状态)，如果是，则AMF不再对UE进行移动性限制校验，可选的，AMF生成第二限制指示信息，也可以向UDM报告该第二限制指示信息以同步相关的限制状态；需要说明的是，AMF中保存UE允许接入的CAG列表，AMF接收基站发送的N2消息，该移动性限制为：N2消息中包含UE接入的CAG小区信息，该小区信息可以在NAS容器中携带，也可以由N2消息中的特定信元携带，如果UE当前接入的CAG小区不在允许的CAG列表中，AMF通过移动性限制拒绝当前UE的接入请求。如 果取消移动性限制校验，则AMF接收UE的接入请求。
在另一种实施方式中，当步骤S201中UDM已经发送第二限制指示信息给AMF时，
AMF可以不需要再去确认CAG列表是否为空，根据该第二限制指示信息，不再对UE进行移动性限制校验。
S203、可选的，AMF可以将第一配置数据发给UE。该第一配置数据中也可以不包括CAG only指示。此外，当UDM在步骤1中未将该第二限制指示信息包含在UE的第一配置数据中，AMF可以生成和发送第二限制指示信息给UE，即AMF发送给UE的第二限制指示信息，可以是从UDM接收到的，也可以是AMF根据空的CAG列表和第一限制指示所生成的。该第二限制指示信息用于指示UE接入网络只允许进行配置数据更新，UE不被允许不能执行请求用户面数据业务请求，以及不被允许请求控制面业务中与配置上数据更新无关的业务，AMF可以将第二限制指示信息写在UE的上下文中，通过第二限制指示信息使得UE处于不限制在允许的CAG列表中的CAG小区接入网络的状态。AMF可以通过发起配置更新流程，将该第一配置数据发给UE。S204、可选的，UE向AMF发送请求信息，所述请求信息用于请求更新配置数据。当UE收到第二限制指示信息后，以及可选的，接收到了第一配置数据，UE可以保持注册态，但不主动发起用户面业务请求或其它与配置数据无关的控制面业务请求，允许通过不在CAG列表中的CAG小区或任意小区或默认小区向网络侧发起配置更新。
UE可以保持注册态，周期性地发起服务请求，查询网络侧针对该UE的配置数据是否更新。当网络侧中针对UE的配置数据更新时，例如更新为第二配置数据，AMF允许UE发起的服务请求，使UE进入连接态，并完成配置更新。该第二配置数据中，UE不再被限制为CAG only，和/或允许的CAG列表不为空。
在另一种实施方式中，UE可以保持注册态，但不主动进行配置更新查询。当AMF上有配置更新时，通过网络侧发起的寻呼过程，使UE进入连接态，并完成配置更新。
S205、当针对UE的配置数据更新为第二配置数据，AMF向UE发送第二配置数据。
当AMF处于不再对UE进行移动性限制校验的状态时，AMF允许UE通过不在CAG列表中的CAG小区或任意小区或默认小区接入网络。因为UE已经接收到了AMF发送的第二限制指示信息，UE不会再去请求用户面服务以及请求与配置更新无关的业务如定位服务请求、小数据传输等。可选的，AMF限制UE的行为，只允许UE进行注册和配置更新，但如果UE请求用户面服务，如请求建立会话时，AMF拒绝该请求，当UE的请求控制面服务，请求与配置更新无关的业务如定位服务请求、小数据传输等时，AMF拒绝该请求，以进一步保证对UE的接入限制，其中可以通过修改UE的上下文，将只允许UE进行注册和配置数 据的更新，使得AMF能够限制UE的行为。
当接收到UE发送的请求消息后，如果AMF中的针对UE的配置数据更新为第二配置数据，AMF发送该第二配置数据给UE。
在另一种可能的实现方式中，当AMF上的针对UE的配置数据允许的CAG list变为空且CAG only指示被设定，AMF不更新UE和基站上的CAG信息。当UE发起服务请求或者注册请求时，AMF使用特定的原因值来拒绝NAS请求，该原因值不同于让UE删除CAG ID的原因值。为了限制UE的行为，AMF将所有或者部分服务区设置为非允许区域，AMF只允许UE进行配置更新。在非允许区域的UE，UE将不允许发起服务请求和会话管理信令来获取UE服务。当网络侧配置信息更新后，即配置信息不为“CAG Only且允许的CAG小区为空”，AMF将UE的所有或者部分服务区移出非允许区域。
本实施例通过AMF对UE进行配置，使得UE依然能够发起发起配置更新，同时取消AMF对UE请求的移动性限制校验，准予了UE接入网络进行配置更新。
此外，当UE已经更新为CAG列表不为空，UE不再被限制为只允许进行配置更新，在允许的接入的CAG小区范围内恢复正常的能力，AMF也恢复对UE的移动性限制校验。
图3是在本申请另一实施例的流程的示意图，图3所示的实施例中的相关步骤和术语描述可以参考图2以及其它的实施例中对应的部分。图3所示的方法包括：
S301、UDM向AMF发送第一消息，该第一消息可以是Nudm_SDM_Notification消息，用于通知AMF该UE的配置数据有更新。UDM发送更新的后的第一配置数据，包括空的CAG列表给AMF，可选的，可以通过该第一消息中携带允许的CAG列表，此时的CAG列表为空，即无可用的CAG ID。需要说明的时，此时的允许UE接入的CAG列表，即空的CAG列表，尚未配置给UE，UE当前的配置状态依然为旧的CAG列表；S301的相关步骤也可参考S201的描述。
S302、AMF收到第一消息，以及允许的CAG列表。AMF收到UDM发送的允许的CAG列表后，更新之前所存储的UE的CAG列表，因为该CAG列表为空，AMF删除之前存储的CAG列表中的CAG ID；
此外，可选的，AMF将收到的包括空的CAG列表的第一配置数据发送给UE。
S303、AMF配置该UE使得该UE处于并非只被允许通过所述列表中的CAG接入网络的状态。
在一种实施方式中，AMF发送默认的CAG小区的ID给UE，通过发送该默认的CAG小区ID,限制UE只能通过该默认的CAG小区接入网络，UE通过接收该默认的CAG小区被配置为并非只被允许通过所述列表中的CAG接入网络的非空状态，。AMF可以通过配置更新流程，由网络侧发送默认的CAG小区的ID给UE侧，使用默认的CAG小区作为允许的CAG列表，UE依然可以继续处于CAG only状态。此外，可选的，可以配置该默认的CAG小区只允许UE接入进行配置数据更新。
在另一种实施方式中，AMF发送第一指示信息，用于指示所述UE不再处于CAG only状态，即UE通过该第一指示信息被配置为并非只被允许通过所述列表中的CAG接入网络的非空状态，通过该第一指示信息，UE不再处于CAG only状态，可以通过非允许的CAG小区或者PLMN网络中其它公用小区发起接入请求，该第一指示信息可以通过替换第一配置数据中的第一限制指示(CAG only指示)，包含在第一配置数据中发送给UE。
S304、UE通过接收默认CAG ID，或接收第一指示信息，被配置为并非只被允许通过所述CAG列表中的CAG接入网络的状态，UE可回复配置更新完成消息给AMF；
UE接收到该默认CAG ID后，可选的，如果UE也接收到的可使用的CAG列表为空，但UE可使用该默认CAG ID对应的小区接入网络，进行配置更新。
S305、可选的，AMF可以在收到UE发送的配置更新完成消息后，发起无线资源控制(radio resource control，RRC)连接释放(connection release)或者去注册deregistration流程，将UE当前的状态从连接态变为空闲态或者去注册态，使UE无法使用其他的网络服务，释放UE占用的网络服务资源。
S306、UE向AMF发起注册请求或者服务请求；需要进行配置更新时，一种实现方式为，UE发起请求信息，该请求信息可以为注册请求信息或服务请求信息，来确定网络侧的配置数据是否有变化，注册请求信息用于请求注册到网络，服务请求信息用于请求服务。UE可周期性的发送注册请求信息或服务请求信息。
在一种实施方式中，当UE接收有至少一个默认CAG小区ID，UE可以通过该特殊CAG小区发送请求信息；
在另外一种实施方式中，如果UE接收有第一指示信息，则UE可以通过非允许的CAG小区或者PLMN网络中其他公用小区发送注册请求或者服务请求。
S307、AMF将更新后的CAG列表通过注册请求接受消息或服务请求接受消息发给UE。
AMF先获取最新的包括CAG列表的针对UE的配置数据，AMF和UDM之间同步UE的配置数据使得AMF获得更新最新的CAG列表。AMF可以主动向UDM发送信息请求更新后的CAG列表，UDM也可以在CAG列表等配置数据更新后主动同步发送给AMF。UDM向AMF发送allowed(允许的)CAG list，携带允许的CAG ID。当UE的配置信息不变时，AMF会进行移动性限制，拒绝UE注册请求或者服务请求。此外，UDM还可以发送指示AMF，指示配置数据中的CAG列表不为空，或者不发送该指示，由AMF根据接收到的CAG列表确定不为空。
当AMF或者UDM中UE的配置配置数据由CAG only，allowed CAG list为空转变为CAG only，allowed CAG list不为空，或者取消CAG only限制时，即针对UE的配置数据更新为第二配置数据时，在一种实施方式中，AMF接受注册请求或者服务请求，但在一些情况下，比如安全上下文不一致、身份凭证为SUCI等原因，触发主认证；AMF接收注册请求或者服务请求，发送第二配置数据给UE。可选的，该第二配置数据也可以包括在回复给UE的注册请求接受消息或服务请求接受消息中，该消息需要有完整性保护。当AMF上没有可用的NAS安全上下文时，AMF先通过NAS SMC流程同UE协商NAS安全上下文，之后回复UE带机密性和完整性保护的注册请求接受消息或服务请求接受消息。
此外，UE的配置配置数据由CAG only，allowed CAG list为空转变为CAG only，allowed CAG list不为空，或者取消CAG only限制时，AMF才接受注册请求或服务请求， 并且AMF可以被配置为只允许UE后续请求配置数据更新，以防止UE在完成配置数据更新前发起其它业务请求。AMF可以在接受请求的消息中携带更新后的CAG list，也可以通过配置更新流程将配CAG list或者取消CAG only限制的指示发送给UE。携带有CAG list或者取消CAG only限制的指示的消息需要有机密性和完整性保护。当AMF上没有可用的NAS安全上下文时，AMF先通过NAS Security Mode Command(SMC,安全模式命令)流程同UE协商NAS安全上下文，之后回复UE带完整性保护的消息。
当针对UE的配置配置数据更新为第二配置数据，在另一种实现方式中，AMF发送拒绝信息给UE，来拒绝注册请求或者服务请求。拒绝消息中，携带该第二配置数据；还可以发送原因(cause)值，该Cause值用于指示UE更新CAG列表。携带有CAG list或者取消CAG only限制的指示或者Cause值的消息需要有完整性保护。当AMF上有可用的NAS安全上下文时，AMF直接使用该安全上下文对消息进行完整性保护。当AMF上没有可用的NAS安全上下文时，AMF先通过NAS SMC流程同UE协商NAS安全上下文，之后回复UE带完整性保护的拒绝消息。
通过在拒绝消息或接受消息中携带新的allowed CAG list或取消CAG only限制的指示，免去了再发起配置更新流程来更新CAG list给UE，节省了系统信令。
S308、当AMF接收UE发送的配置更新完成消息，可选的，AMF发起RRC connection release或者deregistration流程，使得UE释放网络资源。当UE需要重新接入到网络中时，需要按照更新后的配置信息，选择CAG小区。基站和AMF会根据更新后的配置信息进行移动性校验。
此外，针对配置更新，S307的UE主动发起注册请求或服务请求消息外，在另一种实现方式中，UE处于空闲态，AMF上的配置数据更新为第二配置数据时，AMF主动寻呼UE，更新UE上的配置数据。
在本实施例的方案，通过对UE进行配置，例如分配一个默认或特殊的CAG小区ID，使得UE可以通过该默认CAG小区和网络侧进行配置数据更新，或者取消UE的CAG ONLY状态，使得UE可以同非CAG小区接入网络来进行配置更新。需要说明的是，该默认CAG小区不包含在CAG列表中，也可以作为一个默认配置的CAG小区，作为UE存储的CAG列表中的一部分。
图4是在另一种配置数据更新方法的流程的示意图。图4所示的实施例中的相关步骤和术语描述可以参考图2或图3以及其它附图所示的实施例中对应的部分。图4所示的方法包括：
S401、配置数据管理装置确认UE的配置数据由CAG only，allowed CAG list不为空或者allowed CAG list为空且无CAG only限制，或者allowed CAG list不为空且无CAG only限制转变为CAG only，allowed CAG list为空的第一配置数据时，不将该CAG only且allowed CAG列表为空的第一配置数据发送给UE。
当该配置数据管理装置为AMF时，AMF从UDM更新UE的配置数据，当UE的配置数据由CAG only限制指示，allowed CAG list不为空或者allowed CAG list为空且无CAG only限制指示，或者allowed CAG list不为空且无CAG only限制指示转变为第一配置数据时，所述第一配置数据包括第一限制指示和空的封闭接入组CAG列表，所述第一限制指示可以为CAG only限制指示，用于指示所述UE通过封闭接入组CAG接入网络。可选的，AMF删除所存储的UE配置数据中的旧的CAG ID和/或增加CAG only的限制指示。
S402、当该配置数据管理装置为AMF时，AMF配置UE使得UE处于并非只被允许通过所述CAG列表中的CAG接入网络的状态；
在一种实施方式中，AMF通过不将该更新后的CAG列表为空的第一配置数据发给UE，使得UE所存的不为空的CAG列表不会被第一配置数据中的空的CAG列表替换掉，使得UE处于并非只被允许通过所述第一配置数据中的空的CAG列表中接入网络的状态；可选的，为了限制UE的行为，AMF将所有或者部分服务区设置为非允许区域，AMF只允许UE进行配置更新。在非允许区域的UE，UE将不允许发起服务请求和会话管理信令来获取UE服务。当网络侧配置信息更新后，即配置数据不为CAG Only限制指示且允许的CAG小区为空，AMF将UE的所有或者部分服务区移出非允许区域。
在另一种实施方式中，AMF移除第一配置数据中的第一限制指示，AMF发送移除所述第一限制指示的第一配置数据给UE，所述移除所述第一限制指示的第一配置数据用于配置所述终端装置不再只被允许通过CAG接入网络，即使得UE处于non CAG only状态；AMF可以通过non CAG only指示替换掉该第一限制指示，将non CAG only指示包含在配置数据中，和空的CAG列表一同发送给UE。
在另一种实施方式中，AMF向所述终端装置发送第一指示信息，所述第一指示信息用于指示所述终端装置不再只被允许通过CAG接入网络。
当该配置数据管理装置为UDM时，UMD不执行UE配置更新流程，UDM将UE对应的(subscription permanent identifier,SUPI)用户永久标识列入黑名单，不允许UE注册到网络当中。
S403、可选的，当针对UE的配置数据为第一配置数据时，配置数据管理装置触发RRC connection release或者deregistration流程，使得释放UE占用的网络服务资源。
S404、UE发送请求消息，该请求消息可以为注册请求或服务请求；当UE被接收到完整的第一配置数据，UE自身当前的配置数据仍为旧的配置数据，即CAG only，allowed CAG list为旧的CAG ID，或者allowed CAG list为空且无CAG only限制，或者allowed CAG list为旧的CAG ID且无CAG only限制；或者接收到了移除了第一限制指示的配置数据，或者收到了第一指示信息，使得UE处于non CAG only状态；而配置数据管理装置，如AMF或UDM中的配置数据包括：CAG only，allowed CAG list为空。此时UE仍存储有可用的CAG ID,或处于处于non CAG only状态，UE周期或随机的通过可用的CAG小区发送接入注册请求或服务请求，或者UE周期或随机的通过非CAG小区发送接入注册请求或服务请求。
可选的，S405(a)、接收到UE发送的请求消息后，当配置数据管理装置所存储的配置数据没有更新，即依然为CAG only，allowed CAG list为空，配置数据管理装置为AMF时，AMF会进行移动性限制校验，发送包括第二原因值的拒绝消息给UE来拒绝UE的请求，所述第二原因值用于指示UE不删除所述UE所存的CAG列表。另外，AMF需要和UMD保持配置数据的同步，UDM可以主动或被AMF请求，将UDM所存储的UE的最新的配置数据发送给AMF；如果配置数据管理装置为UDM，因为UE的SUPI依然在UDM的黑名单中，即使在之前的步骤中，UDM没有将最CAG列表为空的配置数据发送给AMF，AMF通过了移动性校验，UE也无法通过注册成功；
可选的，S405(b)、当配置数据管理装置所存储的配置数据有更新，即UE的配置信息由CAG only，allowed CAG list为空转变为non CAG only或者allowed CAG list不为空 的第二配置数据时，AMF接收UE对的注册请求或服务请求，当UE对应的SUPI在UDM的黑名单中时，UDM将UE对应的SUPI移出黑名单，完成正常注册流程，AMF将更新后的配置信息通过注册请求接受消息或服务请求接受消息发给UE。具体步骤可参照S307，此处不再赘述。
或者，AMF发送拒绝信息给UE，来拒绝注册请求或者服务请求。当所述终端装置的NAS security可用时，拒绝消息中携带第二配置数据；还可以发送第一原因值，该第一原因值用于指示UE更新CAG列表。
通过在拒绝消息或接受消息中携带新的allowed CAG list，免去了再发起配置更新流程来更新CAG list给UE，节省了系统信令。
可选的，S405(c),当所更新的配置数据和UE当前存储的配置数据相同时，也就是说，和UE当前存储的CAG列表(即配置数据更新装置所存储的旧CAG列表)相同时，配置数据管理装置可以接受UE发送的请求消息，不需要发送更新的配置数据给UE。
图5是在本申请另一实施例的流程的示意图，图5所示的实施例中的相关步骤和术语描述可以参考图2-4所示的实施例中对应的部分。图5所示的方法包括：
S501、UDM向AMF发送第一消息，该第一消息可以是Nudm_SDM_Notification消息，用于通知AMF该UE的配置数据有更新。UDM发送更新的后的配置数据，即空的CAG列表给AMF，可选的，可以通过该第一消息中携带允许的CAG列表和CAG only指示，此时的CAG列表为空，即无可用的CAG ID。需要说明的时，此时的允许UE接入的CAG列表，即空的CAG列表，以及CAG only限制指示尚未配置给UE，UE当前的配置状态依然为旧的CAG列表或者no_CAG_only。
当UDM中UE的配置信息由CAG only，allowed CAG list不为空或者allowed CAG list为空且无CAG only限制，或者allowed CAG list不为空且无CAG only限制转变为CAG only，allowed CAG list为空的第一配置数据时，UDM将UE对应的SUPI列入黑名单，不允许UE注册到网络当中。还可通过第一消息携带去注册指示，该去注册指示用于指示AMF在完成UE的配置更新流程后，执行去注册流程，从而释放UE的网络资源。此外，在UDM发送给AMF的UE的配置信息中，将UE的CAG only限制指示更改为non CAG only指示，使得UE能够不再限制为仅通过CAG小区接入网络。
S502、AMF收到第一消息，该第一消息中可以包括允许的CAG列表和non CAG only指示。AMF收到UDM发送的允许的CAG列表后，更新之前所存储的UE的CAG列表，因为该CAG列表为空，AMF删除之前存储的CAG列表中的CAG ID；此外，AMF可将收到的空的CAG列表发送给UE。
S503、AMF配置该UE使得该UE处于并非只被允许通过所述列表中的CAG接入网络的状态。
AMF发送non CAG only指示，UE通过该指示信息被配置为并非只被允许通过所述列表中的CAG接入网络的非空状态，通过该non CAG only指示，UE不再处于CAG only 状态，可以对非CAG小区发起接入请求。
S504、UE接收non CAG only指示，以及空的CAG列表，UE被配置为并非只被允许通过所述列表中的CAG接入网络的非空状态，UE可回复配置更新完成消息给AMF；
S505、可选的，AMF可以在收到UE发送的配置更新完成消息后，发起无线资源控制(radio resource control，RRC)连接释放(connection release)或者去注册deregistration流程，将UE当前的状态从连接态变为空闲态或者去注册态，使UE无法使用其他的网络服务，释放UE占用的网络服务资。
S506、UE向AMF发起注册请求或者服务请求；需要进行配置更新时，一种实现方式为，UE发起注册请求信息或服务请求信息，来确定网络侧的配置数据释放有变化，注册请求信息用于请求注册到网络，服务请求信息用于请求服务。UE可周期性的发送注册请求信息或服务请求信息。
UE可以通过非CAG小区发送注册请求或者服务请求。
S507、如果UE对应的SUPI在UDM的黑名单中，且UDM存储的UE的配置信息依然是CAG only，allowed CAG list为空，则可以认为配置数据没有更新，因为此时UE对应的SUPI依然在UDM的黑名单中，所以UE无法通过AMF注册成功；当UE的配置信息由CAG only，allowed CAG list为空转变为non CAG only或者allowed CAG list不为空时，将对应的SUPI移出黑名单，使得UE可以进行正常的注册流程。
S508、AMF将更新后的CAG列表通过注册请求接受消息或服务请求接受消息发给UE。
AMF先获取最新的CAG列表，AMF和UDM之间同步UE的签约数据使得AMF获得更新包括最新的CAG列表的新的配置信息或签约数据。AMF可以向UDM发送信息主动请求更新后的CAG列表，UDM也可以在CGA列表等配置数据更新后主动同步发送给AMF。UDM向AMF发送allowed CAG list，携带允许的CAG ID。当UE的配置信息不变时，此时UE对应的SUPI依然在UDM的黑名单中，所以UE无法通过AMF注册成功，拒绝UE注册请求或者服务请求。此外，UDM还可以发送指示AMF，指示配置数据中的CAG列表不为空，或者不发送该指示，由AMF根据接收到的CAG列表确定不为空。
当UE的配置配置数据由CAG only，allowed CAG list为空转变为CAG only，allowed CAG list不为空，则UE对应的SUPI被移出UDM黑名单，使得UE可以进行正常的注册流程，AMF接受注册请求或者服务请求，但在一些情况下，比如安全上下文不一致、身份凭证为SUCI等原因，触发主认证；AMF接收注册请求或者服务请求，发送新的签约数据给UE，该新的签约数据包括了更新后的CAG列表。可选的，该签约数据也可以包括在回复给UE的注册请求接受消息或服务请求接受消息中。
此外，UE的配置配置数据由CAG only，allowed CAG list为空转变为CAG only，allowed CAG list不为空，AMF和UDM才接受注册请求或服务请求，并且AMF可以被配置为只允许UE后续请求配置数据更新，以防止UE在完成配置数据更新前发起其它业务请求。AMF可以在接受请求的消息中携带更新后的CAG list，也可以通过配置更新流程将配CAG list发送给UE。
在另一种实现方式中，UE的配置配置数据由CAG only，allowed CAG list为空转变为CAG only，allowed CAG list不为空，在一种实现方式中，AMF发送拒绝信息给UE，来拒绝注册请求或者服务请求。拒绝消息中，携带新的allowed CAG list；还可以发送Cause 值，该Cause值用于指示UE更新CAG列表。
通过在拒绝消息或接受消息中携带新的allowed CAG list，免去了再发起配置更新流程来更新CAG list给UE，节省了系统信令。
S509、当UE接收AMF发送的配置更新完成消息，可选的，AMF发起RRC connection release或者deregistration流程，使得UE释放网络资源。
此外，针对配置更新，S307的UE主动发起注册请求或服务请求消息外，在另一种实现方式中，UE处于空闲态，AMF上的配置信息从CAG only，allowed CAG list为空转变为CAG only，allowed CAG list不为空时，AMF主动寻呼UE，更新UE上的配置数据。
在本实施例的方案，通过对UE进行配置，取消UE的CAG only状态，使得UE可以同非CAG小区接入网络来进行配置更新，并且UDM将UE的SUPI加入黑名单，使得UE无法通过非CAG正常接入网络，只能用于配置更新。本申请实施例还提供用于实现以上任一种方法的装置，例如，提供一种装置包括用以实现以上任一种方法中终端装置所执行的各个步骤的单元(或手段)。再如，还提供另一种装置，包括用以实现以上任一种方法中会话管理网元所执行的各个步骤的单元(或手段)。
例如，请参考图6，其为本申请实施例提供的一种更新配置数据的装置的示意图。该装置用于执行本申请任一方法实施例中UE所执行各个步骤。该装置用于终端设备。如图6所示，该装置600包括处理单元610，接收单元620和发送单元630。处理单元610，用于更新配置数据；接收单元620，用于接收网络侧发送的指示信息，或者限制指示或者限制信息，或者配置数据，或者原因值，或者配置更新消息，或者拒绝消息，或者接受消息，或者链接释放流程中的相关消息等；发送单元630，用于向网络侧发送消息或信息，包括请求消息，配置更新回复消息等。还可以包括存储单元，用于存储配置数据等信息。
例如，请参考图7，其为本申请实施例提供的又一种更新配置数据的装置的示意图。该装置用于执行本申请任一方法实施例中AMF或UDM所执行各个步骤。当该装置用于接入与移动性管理功能网元，如图12所示，该装置700包括处理单元710、接收单元720和发送单元730。处理单元710，用于确定终端装置的配置数据为第一配置数据，以及确定所述配置数据更新为第二配置数据；还可用于配置所述终端装置处于并非只被允许通过所述CAG列表中的CAG接入网络的状态，以及用于移除配置消息中的限制指示，或替换配置消息中的限制指示。接收单元720用于接收来自UDM的配置数据；发送单元730用于发送配置数据给终端装置。
在一种可能的实现方法中，处理单元710，还用于确定不发生第一配置数据给终端装置。
在一种可能的实现方法中，接收单元720用于接收终端装置发送的请求消息，发送单元730用于发送接受消息或拒绝消息来接受或拒绝请求消息。
在一种可能的实现方法中，所发送单元730用于配置更新消息；以及发送连接释放流程中的相关消息。
在一种可能的实现方法中，处理单元710，还用于用NAS安全上下文对所述拒绝消息或配置更新消息进行机密性和/或完整性保护。
在一种可能的实现方法中，发送单元730还用于发送原因值、限制指示和其他指示消息等。所述第二存留时间大于所述第一存留时间，所述第二存留时间不小于预设的第二阈值。
该装置还可以包括存储单元，用于存储配置数据。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元(例如接收单元)是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元(例如发送单元)是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
请参考图8，其为本申请实施例提供的一种终端设备的结构示意图。该终端设备用于实现以上实施例中终端设备的操作。如图13所示，该终端设备包括：天线810、射频装置820、信号处理部分830。天线810与射频装置820连接。在下行方向上，射频装置820通过天线810接收接入网设备发送的信息，将接入网设备发送的信息发送给信号处理部分830进行处理。在上行方向上，信号处理部分830对终端设备的信息进行处理，并发送给射频装置820，射频装置820对终端设备的信息进行处理后经过天线1310发送给接入网设备。
信号处理部分830用于实现对数据各通信协议层的处理。信号处理部分830可以为该终端设备的一个子系统，则该终端设备还可以包括其它子系统，例如中央处理子系统，用于实现对终端设备操作系统以及应用层的处理；再如，周边子系统用于实现与其它设备的连接。信号处理部分830可以为单独设置的芯片。可选的，以上的装置可以位于信号处理部分830。
信号处理部分830可以包括一个或多个处理元件831，例如，包括一个主控CPU和其它集成电路。此外，该信号处理部分830还可以包括存储元件832和接口电路833。存储元件832用于存储数据和程序，用于执行以上方法中终端设备所执行的方法的程序可能存储，也可能不存储于该存储元件832中，例如，存储于信号处理部分830之外的存储器中，使用时信号处理部分830加载该程序到缓存中进行使用。接口电路833用于与装置通信。 以上装置可以位于信号处理部分830，该信号处理部分830可以通过芯片实现，该芯片包括至少一个处理元件和接口电路，其中处理元件用于执行以上终端设备执行的任一种方法的各个步骤，接口电路用于与其它装置通信。在一种实现中，实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现，例如该装置包括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中终端设备执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件，即片内存储元件。
请参考图9，其为本申请实施例提供的一种装置的结构示意图，用于实现以上实施例中AMF网元或UDM网友的操作。如图14所示，当为AMF网元时，包括：处理器910，存储器920，和接口930，处理器910、存储器920和接口930信号连接。
以上实施例中AMF网元执行的方法可以通过处理器1410调用存储器1420中存储的程序来实现。即，用于AMF的装置包括存储器和处理器，存储器用于存储程序，该程序被处理器调用，以执行以上方法实施例中的AMF网元执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。用于会话管理网元的装置可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
本申请实施例还提供了一种系统，该系统可包括AMF和UDM。可选的，还包括RAN，以及UE。
本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种1C工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor,CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor,PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
虽然在以上的实施例描述中，装置以AMF或UDM或者终端装置为例来描述，但本申请中描述的装置的范围并不限于接入网装置或者终端装置，而且装置的结构可以不受附图的限制。装置可以是独立的设备或者可以是较大设备的一部分。例如所述设备可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选地，该IC集合也可以包括用于存储数据和/或指令的存储部件；
(3)ASIC，例如调制解调器(MSM)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端、蜂窝电话、无线设备、手持机、移动单元，网络设备等等；
(6)其他等等。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符 “/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本申请实施例的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (41)

  1. 一种更新配置数据的方法，其特征在于，包括：
    当针对终端装置的配置数据为第一配置数据时，所述第一配置数据包括第一限制指示和空的封闭接入组CAG列表，所述第一限制指示用于指示所述终端装置通过封闭接入组CAG接入网络，所述CAG列表为允许所述终端装置接入的CAG ID的集合，接入与移动性管理功能装置配置所述终端装置处于并非只被允许通过所述CAG列表中的CAG接入网络的状态；
    当针对所述终端装置的所述配置数据更新为第二配置数据，其中所述第二配置数据中的CAG列表不为空或者不包括所述第一限制指示，所述接入与移动性管理装置发送所述第二配置数据给所述终端装置。
  2. 根据权利要求1所述的方法，其特征在于，所述接入与移动性管理功能装置配置所述终端装置为并非只被允许通过所述CAG列表中的CAG接入网络的状态，包括：
    所述接入与移动性管理功能装置发送移除所述第一限制指示的第一配置数据给所述终端装置，所述移除所述第一限制指示的第一配置数据用于配置所述终端装置不再只被允许通过CAG接入网络。
  3. 根据权利要求1所述的方法，其特征在于，所述接入与移动性管理功能装置配置所述终端装置为并非只被允许通过所述CAG列表中的CAG接入网络的状态，包括：
    所述接入与移动性管理功能装置不发送所述第一配置数据给所述终端装置，所述空的CAG列表用于替换所述终端装置所存的不为空的CAG列表。
  4. 根据权利要求2所述的方法，其特征在于，包括：
    所述移除所述第一限制指示的第一配置数据中包括第一指示信息，所述第一指示信息用于指示所述终端装置不再只被允许通过CAG接入网络。
  5. 根据权利要求1所述的方法，其特征在于，所述接入与移动性管理功能装置配置所述终端装置为并非只被允许通过所述CAG列表中的CAG接入网络的状态，包括：
    所述接入与移动性管理功能装置发送至少一个默认CAG的标识给所述终端装置，所述默认CAG用于所述终端装置更新配置数据。
  6. 根据权利要求1-5任一所述的方法，其特征在于，所述接入与移动性管理装置发送所述第二配置数据给所述终端装置，包括：
    所述接入与移动性管理装置接收到所述终端装置的请求消息后，发送拒绝消息给所述终端装置，所述拒绝消息包含所述第二配置数据。
  7. 根据权利要求1至5中任一项所述的方法，其特征在于，所述接入与移动性管理装置发送所述第二配置数据给所述终端装置，包括：
    所述接入与移动性管理装置接收到所述终端装置的请求消息后，接受所述请求消息，发送配置更新消息给所述终端装置，所述配置更新消息携带所述第二配置数据；
    当所述接入与移动性管理装置接收所述终端装置的配置更新回复消息后，所述接入与移动性管理功能装置发起连接释放流程，所述连接释放流程用于使得所述终端装置从连接态变为空闲态或去注册态。
  8. 根据权利要求6所述的方法，其特征在于，所述接入与移动性管理装置发送第一 原因值给所述终端装置，所述第一原因值用于指示所述终端装置更新为第二配置数据。
  9. 根据权利要求6至8任一所述的方法，其特征在于，所述接入与移动性管理装置使用NAS安全上下文对所述拒绝消息或配置更新消息进行机密性和/或完整性保护。
  10. 根据权利要求9所述的方法，其特征在于，所述接入与移动性管理装置中的NAS安全上下文不可用时，所述接入与移动性管理装置激活NAS安全上下文后，发送所述第二配置数据。
  11. 根据权利要求1至10任一项所述的方法，其特征在于，所述方法还包括：
    当针对终端装置的配置数据为所述第一配置数据，所述接入与移动性管理功能装置接收到所述终端装置发送的请求消息时，所述接入与移动性管理功能装置发送包括第二原因值的拒绝消息给所述终端装置，所述第二原因值用于指示所述终端装置不删除所述终端装置所存的CAG列表。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述方法还包括：当针对终端装置的配置数据为所述第一配置数据，所述接入与移动性管理功能装置发起连接释放流程，所述连接释放流程用于使得所述终端装置从连接态变为空闲态或去注册态。
  13. 根据权利要求1-12中任一项所述的方法，其特征在于，所述方法还包括：当针对终端装置的配置数据为所述第一配置数据，所述接入与移动性管理功能装置允许所述终端装置接入网络更新配置数据。
  14. 根据权利要求11中所述的方法，其特征在于，所述接入与移动性管理功能装置拒绝所述终端装置的服务请求和会话管理信令请求，仅允许所述终端装置更新配置数据。
  15. 根据权利要求1至14中任一所述的方法，其特征在于，所述接入与移动性管理功能装置将所述终端装置的所有服务区均设置为非允许区域。
  16. 一种更新配置数据的方法，其特征在于，包括：
    当针对终端装置的配置数据为第一配置数据，所述第一配置数据包括第一限制指示和空的封闭接入组CAG列表，所述第一限制指示用于指示所述终端装置通过封闭接入组CAG接入网络，所述CAG列表为允许所述终端装置接入的CAG ID的集合，所述终端装置被配置为并非只被允许通过所述CAG列表中的CAG接入网络的状态；
    当针对所述终端装置的所述配置数据更新为第二配置数据，其中所述第二配置数据中的CAG列表不为空或者不包括所述第一限制指示，所述终端装置接收来自所述接入与移动性管理装置的第二配置数据。
  17. 根据权利要求16所述的方法，其特征在于，所述终端装置被配置为并非只被允许通过所述CAG列表中的CAG接入网络的状态，包括：
    所述终端装置接收来自所述接入与移动性管理功能装置的移除所述第一限制指示的第一配置数据，所述移除所述第一限制指示的第一配置数据用于配置所述终端装置不再只被允许通过CAG接入网络。
  18. 根据权利要求16所述的方法，其特征在于，所述终端装置被配置为并非只被允许通过所述CAG列表中的CAG接入网络的状态，包括：
    所述终端装置接收来自所述接入与移动性管理功能装置的第一指示信息，所述第一指示信息用于指示所述终端装置不再只被允许通过CAG接入网络。
  19. 根据权利要求16所述的方法，其特征在于，所述终端装置被配置为并非只被允许通过所述CAG列表中的CAG接入网络的状态，包括：
    所述终端装置接收来自所述接入与移动性管理功能装置的至少一个默认CAG的标识给，所述默认CAG用于所述终端装置更新配置数据。
  20. 根据权利要求16至19任一所述的方法，其特征在于，所述终端装置接收来自所述接入与移动性管理装置的第二配置数据，包括：
    所述终端装置向所述接入与移动性管理装置发送请求消息，所述终端装置接收来自所述接入与移动性管理装置发送的拒绝消息，所述拒绝消息包含所述第二配置数据。
  21. 根据权利要求20所述的方法，其特征在于，所述终端装置接收来自所述接入与移动性管理装置的第一原因值，所述所述第一原因值用于指示所述终端装置更新为第二配置数据。
  22. 根据权利要求16至19任一所述的方法，其特征在于，所述终端装置向所述接入与移动性管理装置发送请求消息后，接收所述接入与移动性管理装置发送的配置更新消息，所述配置更新消息携带所述第二配置数据；
    所述终端装置向所述接入与移动性管理装置发送配置更新回复消息后，通过所述接入与移动性管理功能装置发起的连接释放流程，从连接态变为空闲态或去注册态。
  23. 根据权利要求16至22任一所述的方法，其特征在于，当针对终端装置的配置数据为所述第一配置数据，所述终端装置向所述接入与移动性管理功能装置发送请求消息后，所述终端装置接收来自所述接入与移动性管理功能装置的包括第二原因值的拒绝消息，所述第二原因值用于指示所述终端装置不删除所述终端装置所存的CAG列表。
  24. 根据权利要求16至23任一所述的方法，其特征在于，当针对终端装置的配置数据为所述第一配置数据，所述终端装置通过所述接入与移动性管理功能装置发起的所述连接释放流程从连接态变为空闲态或去注册态。
  25. 一种更新配置数据的方法，其特征在于，包括：
    当配置数据管理装置中的针对终端装置的配置数据为第一配置数据时，所述第一配置数据包括第一限制指示和空的封闭接入组CAG列表，所述第一限制指示用于指示所述终端装置通过封闭接入组CAG接入网络，所述CAG列表为允许所述终端装置接入的CAG ID的集合，配置数据管理装置不将所述空的CAG标识列表发送给所述终端装置；
    当针对所述终端装置的所述配置数据更新为第二配置数据，其中所述第二配置数据中的CAG列表不为空或者不包括所述第一限制指示，所述接入与移动性管理装置发送所述第二配置数据给所述终端装置。
  26. 根据权利要求25所述的方法，其特征在于，所述配置数据管理装置为统一数据管理网元，当所述统一数据管理网元中的配置数据为所述第一配置数据，所述统一数据管理网元将所述终端装置的标志加入黑名单，禁止所述终端装置接入网络；当所述统一数据管理网元中的配置数据更新为所述第二配置数据，所述统一数据管理网元将所述将所述终端装置的标识移出所述黑名单。
  27. 根据权利要求25或26所述的方法，其特征在于，所述所述配置数据管理装置为统一数据管理网元，所述统一数据管理网元发送第二限制指示信息给接入与移动性管理功能装置。
  28. 根据权利要求25至27任一所述的方法，其特征在于，所述所述配置数据管理装置为统一数据管理网元，所述统一数据管理网元移除第一配置数据中的所述第一限制指示后发送给所述接入与移动性管理功能装置。
  29. 一种接入与移动性管理功能装置，其特征在于，所述装置用于执行权利要求1-15任一所述的方法。
  30. 一种接入与移动性管理功能装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求1-15任一所述的方法。
  31. 一种通信装置，其特征在于，所述通信装置用于执行权利要求16-24任一所述的方法。
  32. 一种通信装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求16-24任一所述的方法。
  33. 一种配置数据管理装置装置，其特征在于，所述通信装置用于执行权利要求25-28任一所述的方法。
  34. 一种配置数据管理装置装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求25-28任一所述的方法。
  35. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序，所述程序被处理器调用时，权利要求1-15任一所述的方法被执行。
  36. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序，所述程序被处理器调用时，权利要求16-24任一所述的方法被执行。
  37. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序，所述程序被处理器调用时，权利要求25-28任一所述的方法被执行。
  38. 一种计算机程序，其特征在于，当所述程序被处理器调用时，权利要求1-15任一所述的方法被执行。
  39. 一种计算机程序，其特征在于，当所述程序被处理器调用时，权利要求16-24任一所述的方法被执行。
  40. 一种计算机程序，其特征在于，当所述程序被处理器调用时，权利要求25-28任一所述的方法被执行。
  41. 一种通信系统，所述系统包括权利要求29所述的移动性管理功能装置，还包括统一数据管理网元，所述统一数据管理网元用于向所述移动性管理功能装置发送针对终端装置的配置数据。
PCT/CN2019/109528 2019-09-30 2019-09-30 更新配置数据的方法、装置和系统 WO2021062664A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
PCT/CN2019/109528 WO2021062664A1 (zh) 2019-09-30 2019-09-30 更新配置数据的方法、装置和系统
EP20872648.9A EP4030828A4 (en) 2019-09-30 2020-08-11 METHOD AND DEVICE FOR UPDATING CONFIGURATION DATA AND SYSTEM
BR112022006079A BR112022006079A2 (pt) 2019-09-30 2020-08-11 Método de atualização de dados de configuração, aparelho e sistema
CN202080068459.9A CN114451016B (zh) 2019-09-30 2020-08-11 更新配置数据的方法、装置和系统
PCT/CN2020/108497 WO2021063115A1 (zh) 2019-09-30 2020-08-11 更新配置数据的方法、装置和系统
US17/708,841 US20220225098A1 (en) 2019-09-30 2022-03-30 Configuration Data Update Method, Apparatus, and System

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/109528 WO2021062664A1 (zh) 2019-09-30 2019-09-30 更新配置数据的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2021062664A1 true WO2021062664A1 (zh) 2021-04-08

Family

ID=75337602

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2019/109528 WO2021062664A1 (zh) 2019-09-30 2019-09-30 更新配置数据的方法、装置和系统
PCT/CN2020/108497 WO2021063115A1 (zh) 2019-09-30 2020-08-11 更新配置数据的方法、装置和系统

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/108497 WO2021063115A1 (zh) 2019-09-30 2020-08-11 更新配置数据的方法、装置和系统

Country Status (5)

Country Link
US (1) US20220225098A1 (zh)
EP (1) EP4030828A4 (zh)
CN (1) CN114451016B (zh)
BR (1) BR112022006079A2 (zh)
WO (2) WO2021062664A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125812A (zh) * 2021-11-12 2022-03-01 中国联合网络通信集团有限公司 一种数据同步方法、装置、服务器及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220345989A1 (en) * 2019-06-24 2022-10-27 Samsung Electronics Co., Ltd. Method and apparatus for managing closed access group information

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104782205A (zh) * 2012-10-02 2015-07-15 Lg电子株式会社 在无线通信系统中支持载波聚合组的方法和设备
US10225833B2 (en) * 2014-03-24 2019-03-05 Lg Electronics Inc. Communication method for dual connectivity and apparatus using same
CN109804679A (zh) * 2016-10-13 2019-05-24 Lg电子株式会社 在无线通信系统中由终端执行的侧链路同步信号发送方法以及使用该方法的终端
CN110100407A (zh) * 2017-10-03 2019-08-06 联发科技股份有限公司 无线通信中基于码本的上行链路传输

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296451B (zh) * 2008-06-03 2012-02-29 中兴通讯股份有限公司 一种更新终端的内部用户组列表的方法
US8924535B2 (en) * 2008-12-23 2014-12-30 Qualcomm Incorporated Maintaining closed subscriber group information for access control
WO2011085222A2 (en) * 2010-01-08 2011-07-14 Interdigital Patent Holdings, Inc. Method and apparatus for adding csg identities to a white list in connected mode
WO2018141117A1 (zh) * 2017-02-06 2018-08-09 华为技术有限公司 一种数据处理方法、装置及系统
EP3788826B1 (en) * 2019-03-28 2022-06-08 Ofinno, LLC Core paging handling
US11490291B2 (en) * 2019-03-28 2022-11-01 Ofinno, Llc Handover for closed access group
PL3791648T3 (pl) * 2019-03-29 2023-10-16 Beijing Xiaomi Mobile Software Co., Ltd. Obsługa przywoływania ran
CN110213808B (zh) * 2019-05-06 2022-08-12 腾讯科技（深圳）有限公司 网络接入控制方法、装置、计算机可读介质及电子设备
US20220345989A1 (en) * 2019-06-24 2022-10-27 Samsung Electronics Co., Ltd. Method and apparatus for managing closed access group information
KR20210020696A (ko) * 2019-08-16 2021-02-24 삼성전자주식회사 무선통신 시스템에서 액세스 제어, 관리 및 보호 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104782205A (zh) * 2012-10-02 2015-07-15 Lg电子株式会社 在无线通信系统中支持载波聚合组的方法和设备
US10225833B2 (en) * 2014-03-24 2019-03-05 Lg Electronics Inc. Communication method for dual connectivity and apparatus using same
CN109804679A (zh) * 2016-10-13 2019-05-24 Lg电子株式会社 在无线通信系统中由终端执行的侧链路同步信号发送方法以及使用该方法的终端
CN110100407A (zh) * 2017-10-03 2019-08-06 联发科技股份有限公司 无线通信中基于码本的上行链路传输

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTERDIGITAL, INC.: "CAG-only indication and empty Allowed CAG list S2-1907416", 3GPP TSG-SA WG2 MEETING #134, 28 June 2019 (2019-06-28), XP051752377 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125812A (zh) * 2021-11-12 2022-03-01 中国联合网络通信集团有限公司 一种数据同步方法、装置、服务器及存储介质
CN114125812B (zh) * 2021-11-12 2023-07-18 中国联合网络通信集团有限公司 一种数据同步方法、装置、服务器及存储介质

Also Published As

Publication number Publication date
BR112022006079A2 (pt) 2022-06-21
US20220225098A1 (en) 2022-07-14
CN114451016B (zh) 2024-04-23
EP4030828A4 (en) 2022-10-26
EP4030828A1 (en) 2022-07-20
CN114451016A (zh) 2022-05-06
WO2021063115A1 (zh) 2021-04-08

Similar Documents

Publication Publication Date Title
US20230093339A1 (en) Session Management Method, Apparatus, and System
KR102415681B1 (ko) 통신 방법 및 통신 디바이스
WO2019223526A1 (zh) 上下文管理方法及装置
JP2018512811A (ja) 近接サービスリレーの選択
CN111050318B (zh) 终端信息的传递方法及相关产品
US20220225098A1 (en) Configuration Data Update Method, Apparatus, and System
CN115065988B (zh) 中继传输的方法、中继终端和远端终端
CN115669208A (zh) 指示对漫游用户的紧急服务支持的系统和方法
WO2020034919A1 (zh) 定位方法和通信装置
WO2020102989A1 (zh) 注册的方法、终端设备和网络设备
KR20220163924A (ko) 무선 통신 방법, 단말 기기 및 네트워크 기기
US20210227379A1 (en) Method for processing change in radio capability of terminal apparatus and apparatus
KR20230021114A (ko) 통신 방법 및 관련 디바이스
EP3975623B1 (en) Information transmission methods and devices
CN111757417B (zh) 网络接入方法和设备
WO2021129803A1 (zh) 一种信息处理方法及通信装置
WO2023051430A1 (zh) 通信的方法和装置
CN118338290A (zh) 更新配置数据的方法、装置和系统
CN113543157B (zh) 网络资源控制的方法及设备
US20220353882A1 (en) Transmission priority determination method and terminal device
EP4290900A1 (en) Information processing method and apparatus, communication device, and readable storage medium
TWI773554B (zh) 用於基於切片的存取禁止的方法和使用其的用戶設備
US20230422198A1 (en) Periodic Registration Update Procedure for Non-Allowed Service Areas
WO2022151050A1 (zh) 一种网络接入方法、电子设备及存储介质
WO2023070446A1 (zh) 一种注册网络切片的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19947715

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19947715

Country of ref document: EP

Kind code of ref document: A1