WO2021063413A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2021063413A1
WO2021063413A1 PCT/CN2020/119660 CN2020119660W WO2021063413A1 WO 2021063413 A1 WO2021063413 A1 WO 2021063413A1 CN 2020119660 W CN2020119660 W CN 2020119660W WO 2021063413 A1 WO2021063413 A1 WO 2021063413A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
restricted
management network
registration
terminal device
Prior art date
Application number
PCT/CN2020/119660
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 EP20872702.4A priority Critical patent/EP4030818A4/en
Publication of WO2021063413A1 publication Critical patent/WO2021063413A1/zh
Priority to US17/707,438 priority patent/US20220225212A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/02—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration by periodical registration
    • 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
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • 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
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • This application relates to the field of mobile communication technology, and in particular to a communication method and device applied in a third-party contract data configuration scenario.
  • LTE long term evolution
  • 3GPP third generation partnership project proposes a fifth generation (5th generation, 5G) communication network.
  • Next Gen is the abbreviation of the next-generation (ie 5G) mobile communication system architecture, which is composed of UE, AN, Core and data network. Among them, UE, AN, and Core are the main components of the architecture.
  • 5G next-generation
  • NPN non-public network
  • NPN can be understood as a private network under a 5G network that only supports access by private network users, and is a 5G network deployed in a non-public manner. It can be realized by relying on the support of 5G PLMN, or it can be realized without relying on the network function of 5G PLMN. In the former case, NPN can be implemented using network slicing in 5G PLMN. In order to prevent unauthorized UEs from attempting to access and select NPN, the CAG function is additionally used. In the latter case, the NPN network (5G network) is deployed independently and does not rely on the 5G PLMN network.
  • the NPN network uses 5G PLMN ID+NID to identify, NID is Network identifier, where PLMN ID can be an inherent The value can also be a specific value of the PLMN operator deploying this NPN.
  • the NPN network needs to support the online account opening of the terminal device, that is, the terminal device configures third-party contract data on the terminal device through the NPN network when it is initially activated, and this third-party contract data is located in a third-party configuration server independent of the NPN network.
  • the network does not have a mechanism for managing and controlling UEs that need to configure third-party subscription data.
  • This application provides a communication method and device, which are used to implement network management and control of terminal equipment.
  • the present application provides a communication method, including: an access management network element receives a registration request from a terminal device; the access management network element obtains configuration type indication information, and determines to perform acceptance according to the configuration type indication information. Restricted registration; the access management network element starts a restricted registration timer; after the restricted registration timer expires, the access management network element initiates a de-registration process to de-register the terminal device from the network.
  • the registration duration of the terminal device is limited by the restricted timer. If the terminal device has not been registered from the network within the time allowed by the restricted timer, the network will force the terminal device to register to prevent the terminal device Long-term malicious stay or access to other services, this solution is simple to implement and easy to deploy.
  • the obtaining, by the access management network element, the configuration type indication information includes:
  • the access management network element obtains the configuration type indication information from the registration request; or
  • the access management network element obtains the configuration type indication information from the N2 message from the access network element, where the N2 message includes the registration request; or
  • the access management network element requests the user subscription data of the terminal device from the data management network element, and receives the configuration type indication information returned by the data management network element.
  • the method before the access management network element starts the restricted registration timer, the method includes: the access management network element obtains a restricted policy, and according to the restricted policy The restricted registration timer information in the data management network element determines the restricted registration timer; wherein, the access management network element obtains the restricted policy by one or more of the following methods: obtains the receiving service from the data management network element Restricted policy, obtains the locally configured restricted policy, or obtains the restricted policy from the PCF.
  • the method further includes: the access management network element determines the duration of a periodic registration timer or a mobile reachable timer according to the duration of the restricted registration timer, where: The duration of the periodic registration timer or the mobility reachable timer is less than or equal to the duration of the restricted registration timer.
  • the method further includes: the access management network element determines the duration of the restricted registration timer according to the duration of a periodic registration timer or a mobility reachable timer, where: The duration of the periodic registration timer or the mobility reachable timer is less than or equal to the duration of the restricted registration timer.
  • the method further includes: the access management network element receives a NAS message from the terminal device, where the NAS message includes a session establishment request for requesting establishment of a first session.
  • the NAS message further includes DNN information that the terminal device requests to access, and the restricted policy includes allowed DNN information
  • the method further includes: the access management network element It is determined whether the DNN information requested by the terminal device to be accessed meets the allowed DNN information, and if so, the establishment process of the first session is executed.
  • the restricted policy includes SMF selection information
  • the method further includes: the access management network element selects an SMF to provide services for the first session according to the SMF selection information.
  • the restricted policy includes a roaming policy
  • the method further includes: the access management network element determines, according to the roaming policy, that the roaming mode supported by the first session is the local breakout mode Or Home routed mode, selecting SMF to provide service for the first session according to the supported roaming mode.
  • the restricted policy includes the number of allowed sessions, and the method further includes:
  • the access management network element determines that the number of sessions established by the terminal device is equal to or exceeds the allowed number of sessions, and the access management network element rejects the NAS message.
  • the present application provides a communication method, including: a terminal device sends a registration request to the network to register in the network; the terminal device sends a session establishment request to the network to establish a first session; the terminal device passes The first session receives third-party contract data from a third-party configuration server; after receiving the third-party contract data, the terminal device initiates a session release process and a de-registration process; the terminal device uses the third party The contract data is re-registered to the network.
  • the terminal device after receiving the third-party contract data, the terminal device initiates a session release process and a de-registration process, and uses the third-party contract data to re-register to the network to avoid the terminal device staying in the network for a long time.
  • the registration request carries a configuration type indication
  • the configuration type indication is used to indicate that the registration is a restricted registration.
  • the terminal device sends a registration request to the network through a radio resource control RRC access message, the RRC access message carries a configuration type indication, and the configuration type indication is used to indicate that the registration is accepted. Registration only.
  • the terminal device sends the session establishment request to the network through a NAS message, and the NAS message includes the DNN that the terminal device requests to access, and the terminal device requests to access the network.
  • the imported DNN is a restricted DNN.
  • the session establishment request message includes the service provider identification SP-ID.
  • this application provides a communication method, including: a data management network element receives a request for obtaining user subscription data sent by an access management network element, where the request carries a user identification; the data management network element determines that the The user subscription data corresponding to the user identifier is configuration subscription data; the data management network element sends a configuration type indication to the access management network element, and the configuration type indication is used to indicate that the registration is a restricted registration.
  • the data management network element determines that the user subscription data corresponding to the user identifier is configuration subscription data; the data management network element sends a configuration type indication to the access management network element, and the configuration type indication It is used to indicate that the registration is a restricted registration, so that the subsequent access management network element can perform restricted registration management to prevent the terminal device from staying maliciously for a long time or accessing other services.
  • This solution is simple to implement and easy to deploy.
  • the user subscription data corresponding to the user identifier includes instruction information, and the instruction information indicates that the user subscription data is configuration subscription data.
  • the method includes: the data management network element obtains a restricted policy, and sends the restricted policy to the access management network element, and the restricted policy includes restricted registration Timer information, where the restricted registration timer information is used to determine the restricted timer.
  • the method includes: the data management network element obtains the device identification of the terminal device, and according to the device identification of the terminal device and the shared subscription data
  • the use record in the data determines whether the terminal device is allowed to use the shared subscription data, wherein the use record includes the use history record of the terminal device that has been registered; if not allowed, the access management network element is notified Reject the terminal device.
  • judging whether to allow the terminal device to use the shared subscription data according to the device identifier of the terminal device and the usage record of the shared subscription data includes:
  • the terminal device If it is determined that the terminal device is an unregistered terminal device, allow the terminal device to use the shared subscription data; or
  • the terminal device is not allowed to use the shared subscription data
  • the terminal device If the number of registrations of the terminal device exceeds the threshold, the terminal device is not allowed to use the shared subscription data.
  • the restricted policy further includes one or more of the following information: allowed DNN information, session management network element/user plane network element selection information, roaming policy, allowed session Number, or allowed QOS parameter information.
  • this application provides a device, which may be an access management network element, or a chip or a circuit.
  • the device has the functions of implementing the foregoing first aspect or any possible implementation manner of the first aspect and various 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 including: a processor and a memory; the memory is used to store instructions, and when the device is running, the processor executes the instructions stored in the memory, so that the device executes the first Aspect or any implementation of the first aspect in a communication method. It should be noted that the memory may be integrated in the processor or independent of the processor.
  • the present application provides a device that includes a processor, the processor is configured to couple with a memory, read instructions in the memory, and execute any one of the first aspect or the first aspect according to the instructions.
  • the communication method in the implementation mode.
  • this application provides a device, which may be a terminal device, or a chip or a circuit.
  • the device has the functions of realizing the foregoing second aspect or any possible implementation manner of the second aspect and various 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 including: a processor and a memory; the memory is used to store instructions, and when the device is running, the processor executes the instructions stored in the memory, so that the device executes the second Aspect or the communication method in any implementation manner of the second aspect.
  • the memory may be integrated in the processor or independent of the processor.
  • the present application provides a device that includes a processor, the processor is configured to couple with a memory, read instructions in the memory, and execute any one of the second aspect or the second aspect according to the instructions.
  • the communication method in the implementation mode.
  • this application provides a device, which may be a terminal device, or a chip or a circuit.
  • the device has the functions of realizing the foregoing third aspect or any possible implementation manner of the third aspect and various 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 including: a processor and a memory; the memory is used to store instructions, and when the device is running, the processor executes the instructions stored in the memory, so that the device executes the above-mentioned first
  • the memory may be integrated in the processor or independent of the processor.
  • the present application provides a device that includes a processor, the processor is configured to couple with a memory, read instructions in the memory, and execute any of the third aspect or any of the third aspects according to the instructions.
  • a communication method in an implementation mode.
  • this application also provides a readable storage medium in which a program or instruction is stored, and when it runs on a computer, any communication method in the above aspects is executed.
  • this application also provides a computer program product containing instructions, which when run on a computer, causes the computer to execute any communication method in the above-mentioned aspects.
  • this application also provides a system, which includes an access management network element, and the access management network element can be used to perform the above-mentioned first aspect or any one of the methods of the first aspect or this application
  • the steps in the solution provided by the embodiment are executed by the access management network element.
  • the system may further include a data management network element, and the data management network element may be used to execute any method of the third aspect or the third aspect, or the solution provided in the embodiment of the present application Steps performed by the data management network element.
  • the system may also include other devices that interact with the access management network element and/or data management network element in the solution provided in the embodiments of the present application, for example, SMF, PCF, or terminal equipment, etc. Wait.
  • other devices that interact with the access management network element and/or data management network element in the solution provided in the embodiments of the present application, for example, SMF, PCF, or terminal equipment, etc. Wait.
  • Figure 1 is a schematic diagram of a possible network architecture provided by this application.
  • FIG. 2 is a schematic diagram of a communication method provided by this application.
  • FIG. 3 is an example diagram of a communication method provided by this application.
  • Figure 4 is a schematic diagram of a device provided by this application.
  • FIG. 5 is a schematic diagram of a communication device provided by this application.
  • FIG. 6 is a schematic diagram of a chip provided by this application.
  • FIG. 7 is a schematic diagram of a terminal device provided by this application.
  • At least one means one or more, and “plurality” means two or more.
  • the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • words such as “first” and “second” are used to distinguish the same or similar items with substantially the same function and effect. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not limit the difference.
  • NPN network non-public network, also called private network
  • PLMN network public network
  • the NPN network can be understood as a private network, such as an internal network built by a company, school, or factory. Terminal devices that have not signed a contract with the NPN network are not allowed to access the NPN network.
  • a PLMN network is generally a network operated by an operator that meets the requirements of the 3rd generation partnership project (3rd generation partnership project, 3GPP) standard, referred to as the 3GPP network.
  • 3rd generation partnership project 3rd generation partnership project
  • the 3GPP network includes but is not limited to the 5th generation mobile communication technology (the 5th generation, 5G) network, fourth-generation mobile communication technology (4th-generation, 4G) network, third-generation mobile communication technology (3rd-generation, 3G) network, or second-generation wireless telephone technology (2-generation wireless telephone technology, 2G) Network, etc.
  • the NPN network can also be constructed based on the 3GPP standard requirements, and it can be understood that the NPN network can also be a 3GPP network.
  • the method provided in the embodiments of the present application can be applied to either an NPN network or a public network. In this application, the application of the method to an NPN network is mainly used as an example for description.
  • Fig. 1 is an example of a communication system provided by an embodiment of the application.
  • the communication system provided by the embodiment of the present application may generally include the following devices, network elements, and networks:
  • Terminal device 110 It can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, mobile stations, MS), terminal (terminal), user equipment (UE), soft terminal, etc. For example, water meters, electricity meters, sensors, etc.
  • the (radio access network, RAN) network element 120 used to provide network access functions for authorized terminals in a specific area, and can use transmission tunnels of different quality according to the level of the terminal and service requirements.
  • the RAN network element can manage wireless resources, provide access services for the terminal, and then complete the forwarding of control signals and terminal data between the terminal and the core network.
  • the network element can also be understood as a base station in a traditional network.
  • the RAN network element in the NPN network can also control unauthorized terminal devices to try to access or select the NPN network.
  • User plane network element 130 used for packet routing and forwarding and quality of service (QoS) processing of user plane data, etc.
  • the user plane network element may be a user plane function (UPF) network element.
  • the user plane network element may still be a UPF network element, or may also have other names, which is not limited in this application.
  • Data network network element 140 used to provide a network for transmitting data.
  • the data network element may be a data network (DN) network element.
  • the data network network element may still be a DN network element, or may also have other names, which is not limited by this application.
  • Access management network element 150 Mainly used for mobility management and access management, etc., and can be used to implement other functions other than session management in the mobility management entity (mobility management entity, MME) function, for example, legal Monitoring and access authorization/authentication functions.
  • the access management network element may be an access management function (access and mobility management function, AMF) network element.
  • AMF access management function
  • the access management network element may still be an AMF network element, or may also have other names, which is not limited in this application.
  • Session management network element 160 Mainly used for session management, terminal equipment Internet Protocol (IP) address allocation and management, selection and management of user plane functions, policy control and charging function interface endpoints, and downlink Data notification, etc.
  • the session management network element may be a session management function (session management function, SMF) network element.
  • SMF session management function
  • the session management network element may still be an SMF network element, or may also have other names, which is not limited in this application.
  • Policy control network element 170 A unified policy framework used to guide network behavior, and provide policy rule information for control plane function network elements (such as AMF, SMF network elements, etc.).
  • the policy control network element may be a policy and charging rules function (PCRF) network element.
  • the policy control network element may be a policy control function (PCF) network element.
  • PCF policy control function
  • the policy control network element may still be a PCF network element, or may also have other names, which is not limited in this application.
  • binding support network element 180 used to find the PCF associated with the session.
  • the binding support network element may be a binding support function (BSF) network element.
  • BSF binding support function
  • the binding support network element may still be a BSF network element, or may also have other names, which is not limited in this application.
  • Authentication server 190 used for authentication services, generating keys to realize two-way authentication for terminal devices, and supporting a unified authentication framework.
  • the authentication server may be an authentication server function (authentication server function, AUSF) network element.
  • the authentication server function network element may still be an AUSF network element, or may also have other names, which is not limited in this application.
  • Data management network element 1100 used to process terminal device identification, access authentication, registration, and mobility contract management, etc.
  • the data management network element may be a unified data management (UDM) network element.
  • UDM unified data management
  • unified data management may still be UDM network elements, or may also have other names, which are not limited by this application.
  • Application network element 1110 used for data routing affected by applications, access to network open function network elements, and interaction with the policy framework for policy control, etc.
  • the application network element may be an application function (AF) network element.
  • AF application function
  • the application network element may still be an AF network element, or may also have other names, which is not limited by this application.
  • Network storage network element 1120 used to maintain real-time information of all network functional entities and services in the network.
  • the network storage network element may be a network repository function (NRF) network element.
  • NRF network repository function
  • the network storage network element may still be an NRF network element, or may also have other names, which is not limited by this application.
  • embodiments of the present application are not limited to the foregoing system architecture, and can also be applied to other future communication systems, such as the 6th generation (6G) system architecture.
  • 6G 6th generation
  • the names of the various network elements used in the above embodiments of the present application may maintain the same function in the future communication system, but the names will change.
  • the aforementioned communication system may also include other network elements, equipment, network entities, or network subsystems, such as binding support function (BSF) network elements, etc.
  • BSF binding support function
  • the various network elements in the embodiment of the present application may be a communication device, or a chip or a chip system that can be used in the communication device, which is not limited in the embodiment of the present application.
  • the terminal device (terminal) in the embodiment of the present application may be a device used to implement a wireless communication function, such as a terminal device or a chip that can be used in a terminal device.
  • the terminal equipment may be user equipment (UE), access terminal, terminal unit, terminal station, mobile station, mobile station, remote station, remote terminal, mobile equipment, wireless Communication equipment, terminal agent or terminal device, etc.
  • the access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and wireless communication.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • Functional handheld devices computing devices or other processing devices connected to wireless modems, vehicle-mounted devices or wearable devices, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, industrial control (industrial) Wireless terminal in control), wireless terminal in self-driving (self-driving), wireless terminal in remote medical (remote medical), wireless terminal in smart grid (smart grid), wireless terminal in transportation safety (transportation safety) Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal can be mobile or fixed.
  • the access network equipment in the embodiments of the present application usually includes equipment used to access the core network, such as base stations, broadband network gateways (BNG), aggregation switches, and non-third-generation partnership plans. (3rd generation partnership project, 3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and so on.
  • various network elements or network devices or terminal devices in the embodiments of the present application may also be referred to as communication devices, which may be a general-purpose device or a dedicated device, which is not specifically limited in the embodiments of the present application.
  • the related functions of the policy control network element or network device in the embodiment of the present application can be implemented by one device, or by multiple devices, or by one or more functional modules in one device.
  • the embodiments of this application do not specifically limit this. It is understandable that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (for example, a cloud platform) Virtualization function.
  • the AMF network element may be abbreviated as AMF
  • the SMF network element is abbreviated as SMF
  • the UDM network element is abbreviated as UDM. That is, the AMF described later in this application can be replaced with an access management network element, SMF can be replaced with a session management network element, UDM can be replaced with a data management network element, and other network elements are similar.
  • the device is an AMF entity, an SMF entity, or a UDM entity as examples to describe the method for UPF selection or SMF selection.
  • the chip in the AMF entity and the chip in the SMF entity are described.
  • the implementation method of the chip in the UDM entity please refer to the specific descriptions of the SMF entity, AMF entity, and NRF entity respectively, and the introduction will not be repeated.
  • the user signs a contract with a third party, but the terminal device used by the user is not configured with third-party contract data when it is factory-set.
  • the third-party contract data is located in a third-party configuration server independent of the NPN network. Therefore, when the terminal device is initially activated, it needs to obtain third-party contract data through the NPN network.
  • NPN can allow terminal devices to register on the network and obtain third-party contract data, but these terminal devices need to be managed and controlled, for example, to separate terminal devices from the network in a timely manner. Prevent terminal devices from staying maliciously for a long time or prohibit terminal devices from accessing other services.
  • the communication method, device and system provided in this application for specific content, please refer to the description in the subsequent embodiments.
  • This user subscription data allows a single terminal device to use, such as the subscriber identity module (SIM) card mode currently in use in the market.
  • SIM subscriber identity module
  • Shared subscription data user subscription data that can be shared by multiple terminal devices. For example, there are multiple terminal devices under a certain user, and the multiple terminal devices share the same user subscription data.
  • Configure subscription data The terminal device uses this user subscription data to access the network.
  • the network allows the terminal device to configure and prohibits business.
  • Service contract data The terminal device uses this user contract data to access the network, and the network allows the terminal device to update the contract configuration, and the terminal device can perform business normally.
  • the user subscription data can have multiple types at the same time.
  • the user subscription data can be shared subscription data and configuration subscription data, which means that the user subscription data is used by multiple terminal devices after the user signs, and the network side allows the terminal The equipment is configured and business is prohibited.
  • the terminal device initiates a registration process to register to the network, and the AMF enables the restricted registration timer to allow
  • the terminal device establishes a session within the registration timer, interacts with the third-party configuration server, and obtains third-party contract data.
  • the terminal device can actively release the session and deregister; or, after the restricted registration timer expires, the AMF initiates the terminal device to initiate the de-registration process to unregister the terminal device from the network .
  • the method includes:
  • Step 201 The terminal device sends a registration request to the network. Specifically, the terminal device sends a radio resource control (radio resource control, RRC) message to the RAN, and the RRC message includes a registration request.
  • RRC radio resource control
  • the registration request carries a user ID
  • the user ID is an ID that can uniquely indicate the user.
  • it can be any one or more of the following: mobile station international ISDN number (MSISDN), public subscription identifier (generic public subscription identifier, GPSI), international mobile subscriber identity (international mobile subscriber identity, IMSI), subscription permanent identifier (SUPI), subscription hidden identifier (Subscription Concealed Identifier, SUCI).
  • MSISDN mobile station international ISDN number
  • public subscription identifier generator public subscription identifier
  • GPSI global information service provider
  • IMSI international mobile subscriber identity
  • SUPI subscription permanent identifier
  • subscription hidden identifier Subscribescription Concealed Identifier
  • the registration request also includes configuration type indication information.
  • the configuration type indication information is used to indicate that the registration is a restricted registration (or special registration, configuration registration, online signup registration, etc.), that is, to notify subsequent network elements (such as AMF) to perform restricted registration.
  • the configuration type indication information includes any one or more of the following: the value of the registration type set as restricted registration, the indication used to indicate that the terminal device supports restricted registration (indication of the terminal equipment capability), and the indication used to indicate the execution of restricted registration The identification of the cell or the terminal device set to a special value.
  • the RRC message also includes configuration type indication information.
  • Step 202 The RAN receives the RRC message, selects an AMF, and sends a registration request to the selected AMF.
  • the AMF receives the registration request from the terminal device.
  • the RAN sends an N2 message to the AMF, and the N2 message includes the registration request.
  • the AMF receives the N2 message sent by the RAN, and the N2 message includes the registration request.
  • the N2 message may also include configuration type indication information. That is, the RAN adds the configuration type indication information to the N2 message.
  • the RAN may specifically select an AMF that supports restricted registration according to the configuration type indication.
  • Step 203 the AMF obtains the device identifier of the terminal device from the terminal device.
  • the device identifier of the terminal device can identify a terminal device that accesses a 5G network, and can be an identifier configured when the terminal device leaves the factory.
  • the equipment identification of a terminal device can be any one or more of the following: permanent equipment identifier (PEI), international mobile equipment identity (IMEI), or international mobile equipment identification software version (international mobile equipment identity, IMEI) mobile equipment identity software version, IMEISV).
  • the AMF can obtain the device identity of the terminal device through the Identity request/response message. That is, the AMF sends an Identity request message to the terminal device to request to obtain the device identity of the terminal device; the terminal device returns an Identity request response message, which carries the device identity (for example, PEI).
  • the AMF sends an Identity request message to the terminal device to request to obtain the device identity of the terminal device; the terminal device returns an Identity request response message, which carries the device identity (for example, PEI).
  • Step 204 The AMF sends a request for obtaining user subscription data to UDM, and the request for obtaining user subscription data includes a user identification.
  • the request for obtaining user subscription data further includes the device identifier of the terminal device.
  • the AMF sends the above information to the UDM through the Nudm_SDM_Get request message.
  • Step 205 UDM obtains user subscription data corresponding to the user identifier.
  • step 205 may also include one or more of the following optional steps:
  • Step 205a the UDM determines that the user subscription data corresponding to the user identifier is the configuration subscription data.
  • the user subscription data corresponding to the user identifier includes instruction information
  • the instruction information indicates that the user subscription data is configuration subscription data
  • the UDM determines the user subscription data corresponding to the user identifier as configuration subscription data according to the instruction information.
  • Step 205b Optionally, UDM determines that the user subscription data corresponding to the user ID is shared subscription data, UDM obtains the device ID of the terminal device, and judges whether the terminal device is allowed to use the sharing based on the device ID of the terminal device and the usage record in the shared subscription data The subscription data, wherein the usage record includes the usage history record of the terminal device that has been registered. If it is not allowed, notify the AMF to reject the terminal device, and the subsequent process can refer to the existing process; or, if it is allowed, go to step 206.
  • judging whether to allow the terminal device to use the shared subscription data according to the device identifier of the terminal device and the usage record of the shared subscription data can be specifically in any of the following ways:
  • the terminal device is allowed to use the shared subscription data
  • the terminal device is not allowed to use the shared subscription data
  • the terminal device If the number of registrations of the terminal device does not exceed the threshold, the terminal device is allowed to use the shared subscription data; if the number of registrations of the terminal device exceeds the threshold, the terminal device is not allowed to use the shared subscription data;
  • the terminal device If the terminal device has not registered in a certain period of time in the past, such as within two hours, the terminal device is allowed to use the shared subscription data; or
  • the terminal device If the terminal device has registered within a certain period of time in the past, such as within two hours, the terminal device is not allowed to use the shared subscription data.
  • the device identification of the terminal device and the usage record in the shared subscription data it is determined whether the terminal device is allowed to use the shared subscription data, which can prevent the same terminal device from obtaining configuration information through restricted registration multiple times without limitation.
  • Step 206 The UDM sends the user subscription data corresponding to the user ID to the AMF.
  • the UDM determines that the user subscription data corresponding to the user ID is configuration subscription data
  • the UDM sends a configuration type indication to the AMF, and the configuration type indication is used to indicate that the registration is a restricted registration.
  • the configuration type is indicated as a newly added cell, which is used to instruct to perform restricted registration.
  • UDM determines that the user subscription data corresponding to the user ID is configuration subscription data
  • UDM also obtains the restricted policy and sends the restricted policy to AMF.
  • the restricted policy includes restricted registration timer information, such as duration, or settings The method of limited registration timer duration.
  • the UDM sends the above information to the AMF through the Nudm_SDM_Get response message.
  • Step 207 The AMF obtains the configuration type indication information, and determines to perform restricted registration according to the configuration type indication information;
  • the manner in which the AMF obtains the configuration type indication information may specifically be any one of the following methods or a combination of multiple methods:
  • Manner 1 If the configuration type indication information is carried in the registration request, the AMF obtains the configuration type indication information from the registration request. In this manner, step 207 and steps 204-206 are not related to each other.
  • step 207 and steps 204-206 are not related to each other.
  • Mode 3 AMF requests user subscription data from UDM, and receives the configuration type indication information returned by UDM.
  • the configuration type indication information returned by UDM For the specific content of this mode, please refer to the description in steps 204-206.
  • AMF executes the registration process
  • the AMF starts a restricted registration timer
  • the AMF can start the restricted registration timer during the registration process or after the registration process is completed.
  • the AMF obtains the restricted policy, and determines the restricted registration timer according to the restricted registration timer information in the restricted policy.
  • the AMF obtains the restricted policy through one or more of the following methods: obtains the restricted policy from the UDM, obtains the locally configured restricted policy, or obtains the restricted policy from the PCF.
  • the restricted policy includes restricted registration timer information.
  • the AMF obtains the first restricted policy from UDM, or obtains the locally configured second restricted policy, and obtains the third restricted policy from PCF, and combines the above one or more strategies to determine the final restricted policy.
  • the restricted policy may also include one or a combination of the following information: allowed DNN information, SMF selection information, roaming strategy, or the number of allowed sessions.
  • the AMF determines the duration of the restricted registration timer according to the duration of the periodic registration timer or the mobile reachable timer, where the periodic registration timer or the mobile reachable timer The duration of is less than or equal to the duration of the restricted registration timer.
  • the method further includes: the AMF determines the duration of the periodic registration timer or the mobility reachable timer according to the duration of the restricted registration timer, where the duration of the periodic registration timer or the mobility reachable timer is less than or equal to The duration of the restricted registration timer. That is, the AMF adjusts the duration of the periodic registration timer or the mobile reachable timer according to the duration of the restricted registration timing.
  • the benefit of the periodical registration timer or the mobility reachable timer being less than or equal to the duration of the restricted registration timer is to reduce the mobility management update signaling of the restricted registration terminal device, save network resources, and reduce network load.
  • the AMF allows the terminal device to establish a session within the time of the restricted registration timer, interact with the third-party configuration server, and obtain third-party contract data. If the terminal device completes the configuration of the third-party subscription data, it can actively release the session and deregister (refer to step 214a); or, after the restricted registration timer expires, the AMF forces the terminal device to deregister (refer to step 214b).
  • the terminal device initiates a session establishment process. Specifically, the terminal device sends a NAS message to the AMF, and the NAS message includes a session establishment request for requesting the establishment of the first session.
  • the NAS message also includes the DNN that the terminal device requests to access.
  • the DNN may be a restricted DNN. Restricted DNN means that the network can only allow terminal devices to use, or terminal devices can only request the use of services associated with this DNN, but cannot use other non-associated services.
  • the service associated with the restricted DNN is the online configuration service.
  • the restricted DNN may be pre-configured on the terminal device.
  • the session establishment request message carries the service provider ID (Service Provider-ID, SP-ID).
  • the AMF receives a NAS message from the terminal device, where the NAS message includes a session establishment request, which is used to request the establishment of the first session.
  • the method further includes: AMF judging the DNN that the terminal device requests to access in the NAS message Whether the allowed DNN information is satisfied (that is, it is judged whether the DNN requested by the terminal device is included in the allowed DNN information). If it is not satisfied, the AMF sends a rejection message to the terminal device. Or, if it is satisfied, the subsequent step 213 is executed.
  • the method further includes: the AMF selects the SMF according to the SMF to provide services for the first session.
  • restricted SMF refers to an SMF that supports a service associated with a restricted DNN, such as an SMF that supports an online configuration service.
  • the method further includes: the AMF determines according to the roaming policy that the roaming mode supported by the first session is the local break out mode or the home routed mode, and according to the supported roaming mode Choose to select SMF to provide services for the first session. For example, when the first session supports the local breakout mode, the AMF selects the V-SMF in the service network to provide services for the first session; or, when the first session supports the home routed mode, the AMF selects the H-SMF in the home network as The first session provides services.
  • the method further includes: AMF determines that the number of sessions established by the terminal device is equal to or exceeds the number of sessions allowed in the restricted policy, and the AMF sends The terminal device sends a rejection message.
  • the rejection message may carry a reason value to notify the terminal device that the number of sessions is limited.
  • the subsequent step 212 is executed.
  • the AMF executes the subsequent establishment process of the first session to complete the establishment of the first session.
  • the terminal device After the first session is established, the terminal device receives third-party subscription data from the third-party configuration server through the first session. Then go to step 214a or 214b.
  • the terminal device After receiving the third-party contract data, the terminal device initiates a session release process and a deregistration process.
  • the AMF initiates a de-registration process to de-register the terminal device from the network.
  • the AMF can initiate the deregistration process after the restricted registration timer expires.
  • the registration process unregisters the terminal device from the network.
  • the terminal device uses the third-party contract data to request registration to the network again.
  • the third-party contract data includes contract credentials, such as user certificates, device certificates, user names, passwords, tokens, etc.; in addition, it can also include the service provider identification SP-ID to indicate the service provider corresponding to the contract credentials ; in addition, it can also include network access and selection information, such as network selection strategy (supported PLMN ID or PLMN ID + NPN ID, priority), access information (such as a list of CAGs allowed, only through CAG/NPN Instruction for cell access to the network), special user identification (used to instruct the network to perform external authentication or for the network to query internal subscriptions to determine external authentication), or instruction information to instruct the terminal device to construct a special user identification.
  • network selection strategy supported PLMN ID or PLMN ID + NPN ID, priority
  • access information such as a list of CAGs allowed, only through CAG/NPN Instruction for cell access to the network
  • special user identification used to instruct the network to perform external authentication or for the network to query internal subscriptions to determine external authentication
  • the limited timer is used to limit the length of time for the terminal device to perform third-party contract data configuration with the third-party configuration server. If the terminal device still resides in the network after the allowed time is exceeded, the network forces the terminal The device goes to register to prevent the terminal device from staying maliciously for a long time or accessing other services. This solution is simple to implement and easy to deploy.
  • FIG. 3 a schematic diagram of another communication method provided by an embodiment of the present application, the network side allows the terminal device to establish a restricted second session, and restricts the terminal device's business (for example, the terminal device can only communicate with the network allowed through the second session).
  • Third-party configuration server interaction includes the following steps:
  • the existing general registration can be used, or the registration shown in steps 201-209 in FIG. 2 can be used.
  • the terminal device sends a NAS message to the AMF, where the NAS message includes a session establishment request, which is used to request the establishment of a second session.
  • the NAS message also includes a restricted DNN.
  • the SP-ID is also included in the session establishment request.
  • the terminal device can carry the identification SP-ID of the third-party configuration server to indicate the third-party configuration server that the network will communicate with; it can be used in steps 205, 206, 207, and 208;
  • the AMF receives the NAS message.
  • the specific process refer to step 211.
  • the AMF sends an N11 message to the SMF, and the N11 message includes the aforementioned session establishment request.
  • the N11 message also includes: restricted DNN and SUPI.
  • the session establishment request also includes SP-ID;
  • SMF obtains the AS information of the third-party configuration server from UDM,
  • the SMF sends a Nudm_SDM_Get request to the UDM.
  • the Nudm_SDM_Get request includes SUPI, and the UDM obtains the subscription configuration AS information in the shared subscription according to the SUPI.
  • the Nudm_SDM_Get request sent by the SMF to the UDM may further include the SP-ID; then the UDM obtains the AS information of the third-party configuration server of a specific SP according to the SUPI and the SP-ID;
  • UDM feeds back the third-party contracted configuration AS information to the SMF, and sends a Nudm_SDM_Get response.
  • the Nudm_SDM_Get response includes the AS information of the third-party configuration server;
  • SMF obtains the AS information of the third-party configuration server from DN-AAA;
  • SMF performs secondary authentication of the PDU session to obtain the AS information of the third-party configuration server from DN-AAA
  • the SMF/terminal device sends the SP-ID to the DN-AAA, and obtains the AS information of the third-party configuration server of the specific SP from the DN-AAA;
  • SMF interacts with PCF to obtain AS information of a third-party configuration server from PCF;
  • the PCF can dynamically obtain the subscription configuration AS information from the NEF/AF at any time (for example, before the process starts);
  • the SMF may send the SP-ID to the PCF, and obtain the AS information of the third-party configuration server of the specific SP from the PCF.
  • SMF according to the locally configured AS information of the third-party configuration server, the AS information of the third-party configuration server in the user subscription data in step 305, the AS information of the third-party configuration server in the secondary authentication data in step 306, step 307
  • One or more of the AS information of the third-party configuration server in the policy data to determine the AS information of the third-party configuration server of the restricted DNN, such as port, target address, QoS, IP address, duration, etc.; set the rules of the session , Such as QoS Rule and PDR/FAR, restrict the service information of the second session;
  • SMF can select a specific UPF based on the restricted DNN
  • the SMF continues to perform the session establishment process to complete the establishment of the second session, which is a restricted session;
  • the SMF can also set the PDR/FAR routing rule in the UPF and the QoS rule on the terminal device according to the session rule set in step 308 and the existing process.
  • the terminal device and the third-party configuration server interact to receive third-party contract data from the third-party configuration server.
  • the terminal device After receiving the third-party contract data, the terminal device initiates a session release process and a deregistration process. This step is similar to step 214a.
  • the terminal device uses the third-party contract data to request registration to the network again. For specific description, refer to step 215.
  • each network element described above includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiments of the present application can divide functional modules into mobility management network elements, terminals, data management network elements, authentication service function network elements, or external entities according to the foregoing method examples.
  • each functional module can be divided corresponding to each function, or Two or more functions are integrated in one processing module, and the above-mentioned integrated modules can be implemented in the form of hardware or software function modules.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 4 shows a schematic diagram of a possible logical structure of the communication device involved in the foregoing embodiment.
  • the communication device includes: a processing module 401 and a communication module 402.
  • the processing module 401 is used to control and manage the actions of the communication device.
  • the processing module 401 is used to perform information/data processing steps on the communication device.
  • the communication module 402 is used to support the communication device to send or receive information/data.
  • the communication module can be further divided into a sending module and a receiving module.
  • the communication device may further include a storage module 403 for storing program codes and data that the communication device can use.
  • the communication device is an access management network element, such as AMF, or a chip applied to an access management network element.
  • the communication module 402 is used to support the communication device to execute the processing steps executed by the access management network element in the above-mentioned embodiments of FIG. 2 and FIG. 3.
  • the communication module 402 is used to support the communication device to execute the steps of sending and receiving information/data performed by the access management network element in the steps in the above-mentioned embodiments of FIG. 2 and FIG. 3.
  • the details are as follows:
  • the processing module is used to obtain configuration type indication information, determine to perform restricted registration according to the configuration type indication information; start a restricted registration timer;
  • the processing module is used to initiate a de-registration process through the communication module to de-register the terminal device from the network.
  • the processing module is configured to: obtain the configuration type indication information from the registration request; or obtain the configuration type indication information from the N2 message from the access network element, where the N2 message includes the registration request; or, through the communication module Request the user subscription data of the terminal device from the data management network element, and receive the configuration type indication information returned by the data management network element.
  • the processing module is used to obtain the restricted policy, and determine the restricted registration timer according to the restricted registration timer information in the restricted policy; wherein, the processing module obtains the restricted policy by one or more of the following methods : Obtain the restricted policy from the data management network element through the communication module and obtain the locally configured restricted policy, or obtain the restricted policy from the PCF through the communication module.
  • the processing module is configured to: receive a NAS message from the terminal device through the communication module, where the NAS message includes a session establishment request for requesting establishment of the first session.
  • the NAS message also includes DNN information that the terminal device requests to access, and the restricted policy includes allowed DNN information.
  • the processing module is used to: Whether the DNN information requested by the terminal device for access meets the allowed DNN information, if so, Then the process of establishing the first session is executed.
  • the restricted policy includes SMF selection information
  • the processing module is configured to select the SMF to provide services for the first session according to the SMF selection information.
  • the restricted policy includes a roaming policy
  • the processing module is configured to: according to the roaming policy, determine whether the roaming mode supported by the first session is the local breakout mode or the home routed mode, and select the SMF to provide services for the first session according to the supported roaming mode.
  • the restricted policy includes a processing module for the number of allowed sessions: determining that the number of sessions established by the terminal device is equal to or exceeding the number of allowed sessions, and rejecting the NAS message through the communication module.
  • the communication device is a terminal device, such as a UE, or a chip applied to an access management network element.
  • the communication module 402 is used to support the communication device to execute the processing steps executed by the terminal device in the above-mentioned embodiments of FIG. 2 and FIG. 3.
  • the communication module 402 is configured to support the communication device to execute the steps of sending and receiving information/data performed by the terminal device in the steps in the above-mentioned embodiments of FIG. 2 and FIG. 3.
  • the details are as follows:
  • the communication module is used to send a registration request to the network to register in the network; to send a session establishment request to the network to establish a first session; and to receive third-party contract data from a third-party configuration server through the first session;
  • the processing module After the communication module receives the third-party contract data, the processing module initiates the session release process and the de-registration process through the communication module; uses the third-party contract data to re-register to the network through the communication module.
  • the registration request carries a configuration type indication
  • the configuration type indication is used to indicate that the registration is a restricted registration.
  • the communication module is configured to send a registration request to the network through an RRC access message, the RRC access message carries a configuration type indication, and the configuration type indication is used to indicate that the registration is a restricted registration.
  • the communication module is used for the terminal device to send a session establishment request to the network through a NAS message.
  • the NAS message includes the DNN that the terminal device requests to access, and the DNN that the terminal device requests to access is a restricted DNN.
  • the communication device is a data management network element, such as UDM, or a chip applied to a data management network element.
  • the communication module 402 is used to support the communication device to execute the processing steps executed by the data management network element in the above-mentioned embodiments of FIG. 2 and FIG. 3.
  • the communication module 402 is used to support the communication device to execute the steps of sending and receiving information/data performed by the data management network element in the steps in the above-mentioned embodiments of FIG. 2 and FIG. 3.
  • the details are as follows:
  • the communication module is configured to receive a request for obtaining user subscription data sent by an access management network element, and the request carries a user identifier;
  • the processing module is used to determine that the user subscription data corresponding to the user ID is configuration subscription data; send a configuration type indication to the access management network element through the communication module, and the configuration type indication is used to indicate that the registration is a restricted registration.
  • the user subscription data corresponding to the user identifier includes instruction information, and the instruction information indicates that the user subscription data is configuration subscription data.
  • the processing module is used for the data management network element to obtain the restricted policy, and send the restricted policy to the access management network element through the communication module, and the restricted policy includes restricted registration timer information and restricted registration timer information Used to determine the restricted timer.
  • the processing module is also used to obtain the device identification of the terminal device, and determine whether the terminal device is allowed to use the shared subscription data according to the device identification of the terminal device and the usage record in the shared subscription data, wherein, the usage record includes the usage history record of the terminal device that has been registered; if not allowed, the communication module informs the access management network element to reject the terminal device.
  • the processing module 401 may be a processor or a controller, for example, a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, Hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 402 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 403 may be a memory.
  • the processing module 401 is the processor 51 or the processor 55
  • the communication module 402 is the communication interface 53
  • the storage module 403 is the memory 42
  • the communication device involved in this application may be the communication device shown in FIG. 5.
  • FIG. 5 shows a schematic diagram of the hardware structure of a communication device in an embodiment of the present application.
  • the structure of the access management network element, the data management network element, and the terminal device can refer to the structure shown in FIG. 5.
  • the communication device includes a processor 51, a communication line 54 and at least one communication interface (in FIG. 5, the communication interface 53 is only used as an example for illustration).
  • the communication device may further include a memory 52.
  • the processor 51 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of this application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 54 may include a path to transmit information between the aforementioned components.
  • the communication interface 53 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 52 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrical erasable programmable read-only memory (electrical erasable programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc Storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by Any other medium accessed by the computer, but not limited to this.
  • the memory can exist independently and is connected to the processor through the communication line 54. The memory can also be integrated with the processor.
  • the memory 52 is used to store computer-executable instructions for executing the solution of the present application, and the processor 51 controls the execution.
  • the processor 51 is configured to execute computer-executable instructions stored in the memory 52, so as to implement a communication method provided in the following embodiments of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 51 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5.
  • the communication device may include multiple processors, such as the processor 51 and the processor 55 in FIG. 5.
  • processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the specific structure of the execution body of a communication method is not particularly limited in the embodiment of this application, as long as the program recorded with the code of a communication method of the embodiment of this application can be run according to this application.
  • One communication method in the application embodiment is sufficient for communication, which is not limited in this application.
  • FIG. 6 is a schematic structural diagram of a chip 600 provided by an embodiment of the present application.
  • the chip 60 includes one or more (including two) processors 601 and a communication interface 603.
  • the chip 60 further includes a memory 604.
  • the memory 604 may include a read-only memory and a random access memory, and provides operation instructions and data to the processor 601.
  • a part of the memory 604 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 604 stores the following elements, execution modules or data structures, or their subsets, or their extended sets.
  • the corresponding operation is executed by calling the operation instruction stored in the memory 604 (the operation instruction may be stored in the operating system).
  • One possible implementation is that the structures of the chips used in the access management network element, the data management network element, and the terminal equipment are similar, and different devices can use different chips to achieve their respective functions.
  • the processor 601 controls the processing operations of any one of the access management network element, the data management network element, and the terminal device.
  • the processor 601 may also be referred to as a central processing unit (CPU).
  • the memory 604 may include a read-only memory and a random access memory, and provides instructions and data to the processor 601. A part of the memory 604 may also include NVRAM.
  • the memory 604, the communication interface 603, and the memory 604 are coupled together through a bus system 602, where the bus system 602 may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • various buses are marked as the bus system 602 in FIG. 6.
  • the method disclosed in the foregoing embodiment of the present application may be applied to the processor 601 or implemented by the processor 601.
  • the processor 601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method can be completed by an integrated logic circuit of hardware in the processor 601 or instructions in the form of software.
  • the aforementioned processor 601 may be a general-purpose processor, digital signal processing (DSP), ASIC, ready-made programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistors. Logic devices, discrete hardware components.
  • DSP digital signal processing
  • FPGA ready-made programmable gate array
  • Logic devices discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 604, and the processor 601 reads the information in the memory 604, and completes the steps of the foregoing method in combination with its hardware.
  • the communication interface 630 is used to perform the steps of receiving and sending corresponding network elements in the embodiment shown in FIG. 2 and FIG. 3.
  • the processor 601 is configured to execute the processing steps of the corresponding network element in the embodiment shown in FIG. 2 and FIG. 3.
  • the above communication unit may be a communication interface of the device for receiving signals from other devices.
  • the communication unit is a communication interface used by the chip to receive or send signals from other chips or devices, such as a pin of the chip.
  • FIG. 7 shows a simplified schematic diagram of a possible design structure of a terminal device involved in an embodiment of the present application.
  • the terminal 700 includes a transmitter 701, a receiver 702, and a processor 703.
  • the processor 703 may also be a controller, which is represented as "controller/processor 703" in FIG. 7.
  • the terminal 700 may further include a modem processor 705, where the modem processor 705 may include an encoder 706, a modulator 707, a decoder 708, and a demodulator 709.
  • the transmitter 701 adjusts (for example, analog conversion, filtering, amplification, and up-conversion, etc.) to output samples and generates an uplink signal, which is transmitted via an antenna to the DNS, P-CSCF.
  • the antenna receives the downlink signal.
  • the receiver 702 adjusts (eg, filters, amplifies, down-converts, and digitizes, etc.) the signal received from the antenna and provides input samples.
  • the encoder 706 receives service data and signaling messages to be transmitted on the uplink, and processes the service data and signaling messages (for example, formatting, encoding, and interleaving).
  • the modulator 707 further processes (e.g., symbol mapping and modulation) the encoded service data and signaling messages and provides output samples.
  • the demodulator 709 processes (e.g., demodulates) the input samples and provides symbol estimates.
  • the decoder 708 processes (e.g., deinterleaves and decodes) the symbol estimates and provides decoded data and signaling messages sent to the terminal 700.
  • the encoder 706, the modulator 707, the demodulator 709, and the decoder 708 can be implemented by a synthesized modem processor 705. These units are processed according to the radio access technology adopted by the radio access network (for example, the access technology of LTE and other evolved systems). It should be noted that when the terminal 700 does not include the modem processor 705, the foregoing functions of the modem processor 705 may also be performed by the processor 703.
  • the processor 703 controls and manages the actions of the terminal device 700, and is used to execute the processing procedure performed by the terminal device 700 in the foregoing embodiment of the present application.
  • the terminal device 703 is also used to perform the processing procedures of the terminal device in the methods shown in Figs. 3 and 4 and/or other procedures of the technical solutions described in this application.
  • the terminal device 700 may further include a memory 704, and the memory 704 is used to store program codes and data of the terminal device 700.
  • the embodiment of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores instructions. When the instructions are executed, the functions of accessing the management network element as shown in FIG. 2 and FIG. 3 are realized.
  • the embodiment of the present application provides a computer-readable storage medium, and the computer-readable storage medium stores instructions. When the instructions are executed, the functions of the terminal devices in FIG. 2 and FIG. 3 are realized.
  • the embodiment of the present application provides a computer-readable storage medium, and the computer-readable storage medium stores instructions.
  • the instructions When the instructions are executed, the functions of the data management network elements in FIG. 2 and FIG. 3 are realized.
  • the embodiment of the present application provides a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of accessing the management network element as shown in FIG. 2 and FIG. 3 are realized.
  • the embodiments of the present application provide a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the terminal devices in FIG. 2 and FIG. 3 are realized.
  • the embodiment of the present application provides a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the data management network elements shown in FIG. 2 and FIG. 3 are realized.
  • An embodiment of the present application provides a chip, which is applied to a network management network element.
  • the chip includes at least one processor and a communication interface, the communication interface is coupled with at least one processor, and the processor is used to run instructions to implement 3. Access the function of the management network element.
  • the embodiment of the present application provides a chip, which is applied to a Donor node.
  • the chip includes at least one processor and a communication interface, the communication interface is coupled to at least one processor, and the processor is used to execute instructions to implement the implementation shown in Figs. 2 and 3 The function of the terminal device in the middle.
  • An embodiment of the present application provides a chip, which is applied to an IAB node.
  • the chip includes at least one processor and a communication interface, the communication interface is coupled to at least one processor, and the processor is used to execute instructions to implement The function of the data management network element.
  • An embodiment of the present application provides a communication system, which includes: an access management network element and a data management network element.
  • the access management network element is used to perform any of the steps performed by the access management network element in Figures 2 and 3
  • the data management network element is used to perform any of the steps in Figures 2 and 3 that are managed by the data Steps performed by the network element.
  • the embodiment of the present application also provides a computer-readable storage medium.
  • the methods described in the foregoing method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium or transmitted on a computer-readable medium as one or more instructions or codes.
  • Computer-readable media may include computer storage media and communication media, and may also include any media that can transfer a computer program from one place to another.
  • a storage medium may be any available medium that can be accessed by a computer.
  • the computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used for carrying or with instructions or data structures
  • the required program code is stored in the form of and can be accessed by the computer.
  • any connection is properly termed a computer-readable medium.
  • coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave
  • coaxial cable, fiber optic cable , Twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of the medium.
  • Magnetic disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and blu-ray disks, where disks usually reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included in the scope of computer-readable media.
  • the embodiment of the present application also provides a computer program product.
  • the methods described in the foregoing method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on the computer, the processes or functions described in the above method embodiments are generated in whole or in part.
  • the above-mentioned computer may be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium It can be any usable medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more usable mediums.
  • the usable medium can be a magnetic medium, (for example, a floppy disk, hard disk, tape), optical disk, etc. Medium (for example, DVD), or semiconductor medium (for example, Solid State Disk (SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor.
  • the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
  • the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. achieve.
  • the steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other storage medium in the art.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium, and can store and write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium can be arranged in an ASIC, and the ASIC can be arranged in a terminal device.
  • the processor and the storage medium may also be arranged in different components in the terminal device.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Abstract

本申请提供一种通信方法及装置。该方法包括：接入管理网元接收来自终端设备的注册请求，接入管理网元获得配置类型指示信息，根据所述配置类型指示信息确定执行受限注册并启动受限注册定时器；所述受限注册定时器到期后，所述接入管理网元发起去注册流程将所述UE从网络中去注册。通过该方法，可以防止终端设备长时间恶意驻留或者接入其他业务，且此方案实现简单，容易部署实现。

Description

一种通信方法及装置
本申请要求于2019年9月30日提交中国国家知识产权局、申请号为201910945824.9、发明名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种应用于第三方签约数据配置场景下的通信方法及装置。
背景技术
当前，用户可接入的公共陆地移动网络(public land mobile network，PLMN)有多种，比如长期演进(long term evolution，LTE)通信网络。这些公共陆地移动网络为用户的通话业务、视频业务、网页业务等提供业务数据传输的通道。然而，随着车联网、虚拟现实、移动办公、物联网等新型业务的爆发式发展，要求移动网络提供光纤般的接入速率、低时延的使用体验、千亿设备的连接能力、超高流量密度、超高连接数密度和超高移动性等多场景的一致服务。为此，第三代合作伙伴项目(3rd generation partnership project，3GPP)提出第五代(5th generation，5G)通信网络。Next Gen(或NG)是下一代(即5G)移动通信系统架构简称，由UE，AN，Core和数据网络构成，其中，UE，AN，Core是构成架构的主要成分。
随着需求的发展，3GPP提出非公共网络(Non-public network，NPN)，NPN可以理解为仅支持私网用户接入的5G网络下的私有网络，是一种非公用部署的5G网络。其可以依赖5G PLMN的支持实现，也可以不依赖与5G PLMN的网络功能实现。在前者情况下，NPN可以使用5G PLMN中的网络切片实现，为了阻止非授权UE尝试接入和选择NPN，额外使用CAG功能。在后者情况下，NPN网络(5G网络)独立部署，不依赖5G PLMN网络，NPN网络使用5G PLMN ID+NID来标识，NID为Network identifier，其中PLMN ID可以为第三方运营商预留的固有值，也可以是部署此NPN的PLMN运营商的特定值。
NPN网络需要支持终端设备的在线开户，即终端设备在初始启用时通过NPN网络在终端设备上配置第三方签约数据，此第三方签约数据位于独立于NPN网络的第三方配置服务器中。但是，现有技术中网络没有对需要配置第三方签约数据的UE进行管理控制的机制。
发明内容
本申请提供一种通信方法及装置，用于实现网络对终端设备的管理控制。
第一方面，本申请提供一种通信方法，包括：接入管理网元接收来自终端设备的注册请求；所述接入管理网元获得配置类型指示信息，根据所述配置类型指示信息确定执行受限注册；所述接入管理网元启动受限注册定时器；所述受限注册定时器到期后，所述接入管理网元发起去注册流程将所述终端设备从网络中去注册。
由上述描述可知，通过受限定时器限制终端设备的注册时长，如果在受限定时器限制 允许的时间内，终端设备还没有从网络中去注册，则网络强制终端设备去注册，防止终端设备长时间恶意驻留或者接入其他业务，此方案实现简单，容易部署实现。
在一种可能的实现方式中，，所述接入管理网元获得所述配置类型指示信息包括：
所述接入管理网元从所述注册请求中获得所述配置类型指示信息；或者
所述接入管理网元从来自接入网网元的N2消息中获得所述配置类型指示信息，其中所述N2消息包括所述注册请求；或者
所述接入管理网元向数据管理网元请求所述终端设备的用户签约数据，接收数据管理网元返回的所述配置类型指示信息。
在一种可能的实现方式中，所述接入管理网元启动所述受限注册定时器之前，所述方法包括：所述接入管理网元获取受限策略，并根据所述受限策略中的受限注册定时器信息确定受限注册定时器；其中，所述接入管理网元通过以下一种或多种方式获取所述受限策略：从所述数据管理网元获取所述受限策略，获取本地配置的所述受限策略，或者从PCF获取所述受限策略。
在一种可能的实现方式中，，所述方法还包括:所述接入管理网元根据所述受限注册定时器的时长确定周期性注册定时器或者移动可达定时器的时长，其中，所述周期性注册定时器或者所述移动可达定时器的时长小于或者等于所述受限注册定时器的时长。
在一种可能的实现方式中，，所述方法还包括:所述接入管理网元根据周期性注册定时器或者移动可达定时器的时长确定所述受限注册定时器的时长，其中，所述周期性注册定时器或者所述移动可达定时器的时长小于或者等于所述受限注册定时器的时长。
在一种可能的实现方式中，所述方法还包括：所述接入管理网元接收来自所述终端设备的NAS消息，所述NAS消息包括会话建立请求，用于请求建立第一会话。
在一种可能的实现方式中，，所述NAS消息还包括终端设备请求接入的DNN信息，且所述受限策略包括允许的DNN信息，所述方法还包括：所述接入管理网元判断所述终端设备请求接入的DNN信息是否满足所述允许的DNN信息，如果满足，则执行所述第一会话的建立流程。
在一种可能的实现方式中，所述受限策略包括SMF选择信息，所述方法还包括：所述接入管理网元根据所述SMF选择信息选择SMF为所述第一会话提供服务。
在一种可能的实现方式中，所述受限策略包括漫游策略，所述方法还包括：所述接入管理网元根据所述漫游策略确定所述第一会话支持的漫游模式为Local breakout模式或者Home routed模式，根据所述支持的漫游模式选择SMF为所述第一会话提供服务。
在一种可能的实现方式中，所述受限策略包括允许的会话个数，所述方法还包括：
所述接入管理网元确定所述终端设备建立的会话个数等于或超过所述允许的会话个数，接入管理网元拒绝所述NAS消息。
第二方面，本申请提供一种通信方法，包括：终端设备向网络发送注册请求以注册到网络中；所述终端设备向所述网络发送会话建立请求以建立第一会话；所述终端设备通过所述第一会话接收来自第三方配置服务器的第三方签约数据；在接收完所述第三方签约数据之后，所述终端设备发起会话释放流程以及去注册流程；所述终端设备使用所述第三方签约数据重新注册到网络。
由上述描述可知，终端设备在接收完所述第三方签约数据之后，发起会话释放流程以 及去注册流程，使用所述第三方签约数据重新注册到网络，以免出现终端设备长期驻留在网络中。
在一种可能的实现方式中，所述注册请求中携带配置类型指示，所述配置类型指示用于指示该注册为受限注册。
在一种可能的实现方式中，所述终端设备通过无线资源控制RRC接入消息向网络发送注册请求，所述RRC接入消息携带配置类型指示，所述配置类型指示用于指示该注册为受限注册。
在一种可能的实现方式中，所述终端设备通过NAS消息向所述网络发送所述会话建立请求，所述NAS消息中包括所述终端设备请求接入的DNN，其中所述终端设备请求接入的DNN为受限DNN。
在一种可能的实现方式中，所述会话建立请求消息包括业务提供者标识SP-ID。
第三方面，本申请提供一种通信方法，包括：数据管理网元接收接入管理网元发送的获取用户签约数据的请求，所述请求中携带用户标识；所述数据管理网元确定所述用户标识对应的用户签约数据为配置签约数据；所述数据管理网元向所述接入管理网元发送配置类型指示，所述配置类型指示用于指示该注册为受限注册。
由上述描述可知，所述数据管理网元确定所述用户标识对应的用户签约数据为配置签约数据；所述数据管理网元向所述接入管理网元发送配置类型指示，所述配置类型指示用于指示该注册为受限注册，则以便后续接入管理网元进行受限注册管理，防止终端设备长时间恶意驻留或者接入其他业务，此方案实现简单，容易部署实现。
在一种可能的实现方式中，所述用户标识对应的用户签约数据中包括指示信息，所述指示信息指示所述用户签约数据为配置签约数据。
在一种可能的实现方式中，所述方法包括：所述数据管理网元获取受限策略，并向所述接入管理网元发送所述受限策略，所述受限策略包括受限注册定时器信息，所述受限注册定时器信息用于确定受限定时器。
在一种可能的实现方式中，如果所述用户签约数据为共享签约数据，则所述方法包括：所述数据管理网元获取终端设备的设备标识，根据所述终端设备的设备标识以及共享签约数据中的使用记录判断是否允许所述终端设备使用所述共享签约数据，其中，所述使用记录中包括已经注册过的终端设备的使用历史记录；如果不允许，通知所述接入管理网元拒绝所述终端设备。
在一种可能的实现方式中，根据所述终端设备的设备标识以及所述共享签约数据的使用记录判断是否允许所述终端设备使用所述共享签约数据包括：
如果确定所述终端设备为未注册的终端设备，则允许所述终端设备使用所述共享签约数据；或者
如果确定所述终端设备的为已经注册过的终端设备，则不允许所述终端设备使用所述共享签约数据；
如果所述所述终端设备的注册次数未超过门限，则允许所述终端设备使用所述共享签约数据；或者
如果所述所述终端设备的注册次数超过门限，则不允许所述终端设备使用所述共享签约数据。
在一种可能的实现方式中，所述受限策略还包括以下信息中的一个或多个的组合：允许的DNN信息，会话管理网元/用户面网元选择信息，漫游策略，允许的会话个数，或允许的QOS参数信息。
第四方面，本申请提供一种装置，该装置可以是接入管理网元，也可以是芯片或电路。该装置具有实现上述上述第一方面或第一方面的任一可能的实现方式以及各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，本申请提供一种装置，包括：处理器和存储器；该存储器用于存储指令，当该装置运行时，该处理器执行该存储器存储的该指令，以使该装置执行上述第一方面或第一方面的任一实现方式中中通信方法。需要说明的是，该存储器可以集成于处理器中，也可以是独立于处理器之外。
第六方面，本申请提供一种装置，该装置包括处理器，所述处理器用于与存储器耦合，并读取存储器中的指令并根据所述指令执行上述第一方面或第一方面的任一实现方式中通信方法。
第七方面，本申请提供一种装置，该装置可以是终端设备，也可以是芯片或电路。该装置具有实现上述第二方面或第二方面的任一可能的实现方式以及各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，本申请提供一种装置，包括：处理器和存储器；该存储器用于存储指令，当该装置运行时，该处理器执行该存储器存储的该指令，以使该装置执行上述第二方面或第二方面的任一实现方式中的通信方法。需要说明的是，该存储器可以集成于处理器中，也可以是独立于处理器之外。
第九方面，本申请提供一种装置，该装置包括处理器，所述处理器用于与存储器耦合，并读取存储器中的指令并根据所述指令执行上述第二方面或第二方面的任一实现方式中的通信方法。
第十方面，本申请提供一种装置，该装置可以是终端设备，也可以是芯片或电路。该装置具有实现上述第三方面或第三方面的任一可能的实现方式以及各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十一方面，本申请提供一种装置，包括：处理器和存储器；该存储器用于存储指令，当该装置运行时，该处理器执行该存储器存储的该指令，以使该装置执行上述第三方面或第三方面的任一实现方式中的通信方法。需要说明的是，该存储器可以集成于处理器中，也可以是独立于处理器之外。
第十二方面，本申请提供一种装置，该装置包括处理器，所述处理器用于与存储器耦合，并读取存储器中的指令并根据所述指令执行上述第三方面或第三方面的任一实现方式中的通信方法。
第十三方面，本申请还提供一种可读存储介质，所述可读存储介质中存储有程序或指令，当其在计算机上运行时，使得上述各方面的任意通信方法被执行。
第十四方面，本申请还提供一种包含指令的计算机程序产品，当其在计算机上运行时， 使得计算机执行上述各方面中的任意通信方法。
第十五方面，本申请还提供一种系统，该系统包括接入管理网元，所述接入管理网元元元可用于执行上述第一方面或第一方面的任一方法中或者本申请实施例提供的方案中由接入管理网元执行的步骤。
在一个可能的设计中，所述系统还可以包括数据管理网元，所述数据管理网元可用于执行上述第第三方面或第三方面的任一方法，或者本申请实施例提供的方案中由数据管理网元执行的步骤。
在一个可能的设计中，该系统还可以包括本申请实施例提供的方案中与该接入管理网元和/或数据管理网元进行交互的其他设备，例如，SMF，PCF，或者终端设备等等。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请提供的一种可能的网络架构示意图；
图2为本申请提供的一种通信方法示意图；
图3为本申请提供的一种通信方法的示例图；
图4为本申请提供的一种装置示意图；图；
图5为本申请提供的一种通信设备示意图；
图6为本申请提供的一种芯片示意图；
图7为本申请提供的一种终端设备示意图；
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
目前，通信领域中提出NPN网络的概念，NPN网络(非公共网络，也称私网)是为了 与PLMN网络(公网)区分而提出的一种概念。NPN网络可以理解为私有的网络，例如公司、学校或者工厂搭建的内部网络，未与NPN网络签约的终端设备不允许接入NPN网络。PLMN网络一般为运营商运营的符合第三代合作伙伴项目(3rd generation partnership project，3GPP)标准要求的网络，简称3GPP网络，通常3GPP网络包括但不限于第五代移动通信技术(the 5th generation，5G)网络、第四代移动通信技术(4th-generation，4G)网络、第三代移动通信技术(3rd-generation，3G)网络或第二代无线电话技术(2-generation wireless telephone technology，2G)网络等。需要说明的是，NPN网络也可以基于3GPP标准要求构建，可以理解NPN网络也可以为一种3GPP网络。本申请实施例提供的方法即可适用于NPN网络也可适用于公网，本申请中主要以将该方法应用于NPN网络为例进行说明。
图1为本申请实施例提供的通信系统的一个示例。参考图1，本申请实施例提供的通信系统通常可以包括如下设备、网元和网络：
1、终端设备110：可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端，移动台(mobile station，MS)，终端(terminal)，用户设备(user equipment，UE)，软终端等等。例如，水表、电表、传感器等。
2、(无线)接入网(radio access network，RAN)网元120：用于为特定区域的授权终端提供入网功能，并能够根据终端的级别，业务的需求等使用不同质量的传输隧道。RAN网元能够管理无线资源，为终端提供接入服务，进而完成控制信号和终端数据在终端和核心网之间的转发，网元也可以理解为传统网络中的基站。
NPN网络中的RAN网元还能够控制非授权终端设备尝试接入或选择NPN网络。
3、用户面网元130：用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、数据网络网元140：用于提供传输数据的网络。在5G通信系统中，该数据网络网元可以是数据网络(data network，DN)网元。在未来通信系统中，数据网络网元仍可以是DN网元，或者，还可以有其它的名称，本申请不做限定。
5、接入管理网元150：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。在5G通信系统中，该接入管理网元可以是接入管理功能(access and mobility management function，AMF)网元。在未来通信系统中，接入管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
6、会话管理网元160：主要用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择和管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。在5G通信系统中，该会话管理网元可以是会话管理功能(session management function，SMF)网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
7、策略控制网元170：用于指导网络行为的统一策略框架，为控制面功能网元(例如 AMF，SMF网元等)提供策略规则信息等。在4G通信系统中，该策略控制网元可以是策略和计费规则功能(policy and charging rules function，PCRF)网元。在5G通信系统中，该策略控制网元可以是策略控制功能(policy control function，PCF)网元。在未来通信系统中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
8、绑定功能网元180：用于查找会话所关联的PCF。在5G通信系统中，该绑定支持网元可以是绑定支持功能(binding support function，BSF)网元。在未来通信系统中，绑定支持网元仍可以是BSF网元，或者，还可以有其它的名称，本申请不做限定。
9、认证服务器190：用于鉴权服务、产生密钥实现对终端设备的双向鉴权，支持统一的鉴权框架。在5G通信系统中，该认证服务器可以是认证服务器功能(authentication server function，AUSF)网元。在未来通信系统中，认证服务器功能网元仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
10、数据管理网元1100：用于处理终端设备标识，接入鉴权，注册以及移动性的签约管理等。在5G通信系统中，该数据管理网元可以是统一数据管理(unified data management，UDM)网元。在未来通信系统中，统一数据管理仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
11、应用网元1110：用于进行应用影响的数据路由，接入网络开放功能网元，与策略框架交互进行策略控制等。在5G通信系统中，该应用网元可以是应用功能(application function，AF)网元。在未来通信系统中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
12、网络存储网元1120：用于维护网络中所有网络功能实体和服务的实时信息。在5G通信系统中，该网络存储网元可以是网络注册功能(network repository function，NRF)网元。在未来通信系统中，网络存储网元仍可以是NRF网元，或者，还可以有其它的名称，本申请不做限定。
需要说明的是，本申请实施例并不限定于上述的系统架构，还可以应用于未来其它的通信系统，例如第六代通信(the 6th generation，6G)系统架构等。并且，本申请实施例上述所使用的各个网元的名称，在未来通信系统中，可能保持功能相同，但名称会改变。
此外，虽然图1未示出，但上述通信系统还可能包括其他网元、设备、网络实体或网络子系统，如绑定支持功能(binding surpport function，BSF)网元等，本申请实施例不再赘述。
可选的，本申请实施例中的各种网元，可以是通信设备，也可以是可用于该通信设备中的芯片或芯片系统等，本申请实施例对此不作限定。
需要说明的是，上述各种网元可以是不同的通信设备，也可以是同一台通信设备中不同的通信装置、模块或子系统，本申请实施例对此不做限定。
可选的，本申请实施例中的终端设备(terminal)，可以是用于实现无线通信功能的设备，例如终端设备或者可用于终端设备中的芯片等。其中，终端设备可以是5G网络或者未来演进的PLMN中的用户设备(user equipment，UE)、接入终端、终端单元、终端站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、终端代理或终端装置等。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol， SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备或可穿戴设备，虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。终端可以是移动的，也可以是固定的。
可选的，本申请实施例中的接入网设备通常包括用于接入核心网的设备，例如基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非第三代合作伙伴计划(3rd generation partnership project，3GPP)接入设备等。其中，基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
可选的，本申请实施例中的各种网元或网络设备或终端设备也可以称之为通信装置，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例中的策略控制网元或网络设备的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是硬件与软件的结合，或者是平台(例如，云平台)上实例化的虚拟化功能。
进一步地，可以将AMF网元简称为AMF，SMF网元简称为SMF，UDM网元简称为UDM。即本申请后续所描述的AMF均可替换为接入管理网元，SMF均可替换为会话管理网元，UDM均可替换为数据管理网元，其他网元类似。
为方便说明，在本申请中，以装置为AMF实体、SMF实体、UDM实体为例，对用于UPF选择或SMF选择的方法进行说明，对于装置为AMF实体内的芯片、SMF实体内的芯片、或为UDM实体内的芯片的实现方法，可参考装置分别为SMF实体、AMF实体、NRF实体的具体说明，不再重复介绍。
用户与第三方签约，但是该用户所使用的终端设备在出厂设置时，并没有配置第三方签约数据，其中，第三方签约数据位于独立于NPN网络的第三方配置服务器中。因此终端设备在初始启用时，需要通过NPN网络获得第三方签约数据。NPN对于这类需要获取第三方签约数据的终端设备，可以允许终端设备注册到网络中并获取第三方签约数据，但需要对这些终端设备进行管控，例如，及时的将终端设备从网络中分离，防止终端设备长时间恶意驻留或者禁止终端设备接入其他业务。为了解决上述问题，本申请提供的一种通信方法，装置和系统，具体内容可以参见后续实施例中的描述。
首先，对用户签约数据的不同类型介绍如下：
私有签约数据：此用户签约数据允许单个终端设备使用，如现在市场中正在用的用户识别模块(subscriber identity module，SIM)卡模式。
共享签约数据：多个终端设备可以共同使用的用户签约数据。例如某个用户下有多个终端设备，则该多个终端设备共用同一用户签约数据。
配置签约数据：终端设备使用此用户签约数据接入网络，网络允许终端设备进行配置， 禁止开展业务。
业务签约数据：终端设备使用此用户签约数据接入网络，网络允许终端设备更新签约配置，并且终端设备可以正常开展业务。
其中，用户签约数据可以同时有多种类型，例如，用户签约数据可以是共享签约数据且是配置签约数据，表示用户签约后，多个终端设备共同使用的该用户签约数据，且网络侧允许终端设备进行配置，禁止开展业务。
基于图1的网络架构，如图2所示，为本申请提供的一种通信方法，可用于解决上述问题，终端设备发起注册流程注册到网络中，AMF启用限制注册定时器，允许在受限注册定时器的时间内终端设备建立会话，与第三方配置服务器交互并获取第三方签约数据。当终端设备完成第三方签约数据的配置后，终端设备可以主动释放会话并去注册；或者，在受限注册定时器过期后，AMF发起去终端设备发起去注册流程将终端设备从网络中去注册。该方法包括：
步骤201、终端设备向网络发送注册请求。具体的，终端设备向RAN发送无线资源控制(radio resource control，RRC)消息，RRC消息包括注册请求。
其中，注册请求中携带用户标识，用户标识为能够唯一指示该用户的标识，例如可以是以下任意一项或多项：移动台国际ISDN号(mobile station international ISDN number，MSISDN)、公共订阅标识符(generic public subscription identifier，GPSI)、国际移动用户识别码(international mobile subscriber identity，IMSI)、订阅永久标识符(subscription permanent identifier，SUPI)，签约隐藏标识符(Subscription Concealed Identifier，SUCI)。如果该用户标识对应的用户签约数据为共享签约数据，则多个终端设备在注册请求中可以带有相同的用户标识。
可选的，注册请求中还包括配置类型指示信息。其中，配置类型指示信息用于指示该注册为受限注册(或特殊注册，配置注册，在线(Online Signup)签约注册等)，即通知后续的网元(例如AMF)执行受限注册。配置类型指示信息包括以下任意一项或多项：设为受限注册的注册类型值、用于指示终端设备支持受限注册的指示(终端设备能力的指示indication)、用于指示执行受限注册的信元或设为特殊值的终端设备的标识。
可选的，RRC消息中还包括配置类型指示信息。
步骤202、RAN接收RRC消息，选择AMF，向选择的AMF发送注册请求。相应的，AMF接收来自终端设备的注册请求。
具体的，RAN向AMF发送N2消息，N2消息中包括注册请求。相应的，AMF接收RAN发送的N2消息，该N2消息中包括注册请求。
可选的，如果RRC消息中包括配置类型指示信息，则N2消息中还可以包括配置类型指示信息。即RAN将配置类型指示信息加入N2消息中。
可选的，如果RRC消息中包括配置类型指示信息，RAN具体可以根据配置类型指示选择支持受限注册的AMF。
步骤203、可选的，AMF向终端设备获取终端设备的设备标识。
其中，终端设备的设备标识为可以标识一个接入5G网络的终端设备，可以是终端设备出厂时配置的标识。例如，终端设备的设备标识可以是以下任意一项或多项：永久设备标识(permanent equipment identifier，PEI)，国际移动设备标识(international mobile  equipment identity，IMEI)，或者国际移动设备标识软件版本(international mobile equipment identity software version，IMEISV)。
具体的，AMF可以通过Identity请求/响应消息，获取终端设备的设备标识。即，AMF向终端设备发送Identity请求消息，请求获取终端设备的设备标识；终端设备返回Identity请求响应消息，携带设备标识(例如，PEI)。
步骤204、AMF向UDM发送获取用户签约数据的请求，获取用户签约数据的请求中包括用户标识。
可选的，获取用户签约数据的请求还包括终端设备的设备标识。
具体的，AMF通过Nudm_SDM_Get请求消息向UDM发送上述信息。
步骤205、UDM获取用户标识对应的用户签约数据。
其中，步骤205还可以包括以下一个或多个可选的步骤：
步骤205a，可选的，UDM确定用户标识对应的用户签约数据为配置签约数据。其中，用户标识对应的用户签约数据中包括指示信息，指示信息指示用户签约数据为配置签约数据，UDM根据指示信息确定用户标识对应的用户签约数据为配置签约数据包括：。
步骤205b，可选的，UDM确定用户标识对应的用户签约数据为共享签约数据，UDM获取终端设备的设备标识，根据终端设备的设备标识以及共享签约数据中的使用记录判断是否允许终端设备使用共享签约数据，其中，使用记录中包括已经注册过的终端设备的使用历史记录。如果不允许，通知AMF拒绝终端设备，后续的流程可以参考现有流程；或者，如果允许，则进入步骤206。
具体的，根据终端设备的设备标识以及共享签约数据的使用记录判断是否允许终端设备使用共享签约数据具体可以为以下任一方式：
如果确定终端设备为未注册的终端设备，则允许终端设备使用共享签约数据；
如果确定终端设备的为已经注册过的终端设备，则不允许终端设备使用共享签约数据；
如果终端设备的注册次数未超过门限，则允许终端设备使用共享签约数据；如果终端设备的注册次数超过门限，则不允许终端设备使用共享签约数据；
如果终端设备在过去一定的时间段内没有注册过，如两个小时内，则允许终端设备使用共享签约数据；或者
如果终端设备在过去一定的时间段内注册过，如两个小时内，则不允许终端设备使用共享签约数据。
根据终端设备的设备标识以及共享签约数据中的使用记录判断是否允许终端设备使用共享签约数据，可以防止同一个终端设备不受限的多次通过受限注册获取配置信息。
步骤206、UDM向AMF发送用户标识对应的用户签约数据。
可选的，如果UDM确定用户标识对应的用户签约数据为配置签约数据，UDM向AMF发送配置类型指示，配置类型指示用于指示该注册为受限注册。例如，配置类型指示为新增的信元，用于指示执行受限注册。
可选的，如果UDM确定用户标识对应的用户签约数据为配置签约数据，UDM还获取受限策略，并向AMF发送受限策略，受限策略包括受限注册定时器信息，如时长，或者设置受限注册定时器时长的方式。
具体的，UDM通过Nudm_SDM_Get响应消息向AMF发送上述信息。
步骤207、AMF获得配置类型指示信息，根据配置类型指示信息确定执行受限注册；
其中，AMF获得配置类型指示信息的方式，具体可以是以下任一方式或者多个方式的组合：
方式一：如果注册请求中携带配置类型指示信息，则AMF从注册请求中获得配置类型指示信息。在该方式中步骤207与步骤204-206没有先后关系。
方式二：如果N2消息携带配置类型指示信息，则AMF从N2消息中获得配置类型指示信息。在该方式中步骤207与步骤204-206没有先后关系。
方式三：AMF向UDM请求用户签约数据，接收UDM返回的配置类型指示信息，该方式的具体内容可以参考步骤204-206中的描述。
208、AMF执行注册流程；
209、AMF启动受限注册定时器；
其中，AMF可以在注册过程中，或者注册过程完成后，启动受限注册定时器。
具体的，AMF启动受限注册定时器之前，AMF获取受限策略，并根据受限策略中的受限注册定时器信息确定受限注册定时器。具体的，AMF通过以下一种或多种方式获取受限策略：从UDM获取受限策略，获取本地配置的受限策略，或者从PCF获取受限策略。其中，受限策略包括受限注册定时器信息。例如，AMF从UDM获取第一受限策略，或获取本地配置的第二受限策略，以及从PCF获取第三受限策略，综合以上一种或者多种策略，确定最终的受限策略。其中，受限策略还可以包括以下信息中的一个或多个的组合：允许的DNN信息，SMF选择信息，漫游策略，或者允许的会话个数。
具体的，在AMF启动受限注册定时器之前，AMF根据周期性注册定时器或者移动可达定时器的时长确定受限注册定时器的时长，其中，周期性注册定时器或者移动可达定时器的时长小于或者等于受限注册定时器的时长。
可选的，方法还包括:AMF根据受限注册定时器的时长确定周期性注册定时器或者移动可达定时器的时长，其中，周期性注册定时器或者移动可达定时器的时长小于或者等于受限注册定时器的时长。即AMF根据受限注册定时的时长调整周期性注册定时器或者移动可达定时器的时长。
周期性注册定时器或者移动可达定时器的时长小于或者等于受限注册定时器的时长的好处在于减少受限注册终端设备的移动管理更新信令，节省网络资源，降低网络负荷。
由于启动了受限注册定时器，因此AMF在受限注册定时器的时间内允许终端设备建立会话，与第三方配置服务器交互，获取第三方签约数据。如果终端设备完成第三方签约数据的配置可以主动释放会话并去注册(参考步骤214a)；或者，在受限注册定时器过期后，AMF强制终端设备去注册(参考步骤214b)。
210、终端设备发起会话建立流程。具体的，终端设备向AMF发送NAS消息，NAS消息中包括会话建立请求，用于请求建立第一会话。
可选的，NAS消息中还包括终端设备请求接入的DNN。具体的，该DNN可以为受限DNN。受限DNN是指网络只能允许终端设备使用，或者终端设备只能请求使用与此DNN关联的服务，而不能使用其他非关联的服务。例如，此实施例中，受限DNN关联的服务即在线配置服务。其中，该受限DNN可以是预先配置在终端设备上。
可选的，会话建立请求消息携带业务提供者的标识(Service Provider-ID，SP-ID)。
211、AMF接收来自终端设备的NAS消息，NAS消息包括会话建立请求，用于请求建立第一会话。
可选的，如果NAS消息还包括终端设备请求接入的DNN，且AMF在步骤206中获得的受限策略包括允许的DNN信息，方法还包括：AMF判断NAS消息中终端设备请求接入的DNN否满足允许的DNN信息(即判断终端设备请求接入的DNN是否在允许的DNN信息中)。如果不满足，则AMF向终端设备发送拒绝消息。或者，如果满足，则执行后续步骤213。
可选的，如果AMF在步骤206中获得的受限策略包括SMF选择信息，方法还包括：AMF根据SMF选择SMF为第一会话提供服务。例如，受限的SMF。受限的SMF是指SMF支持受限DNN关联的服务的SMF，如支持在线配置服务的SMF。
可选的，如果AMF在步骤206中获得的受限策略包括漫游策略，方法还包括：AMF根据漫游策略确定第一会话支持的漫游模式为Local Break out模式或者home routed模式，根据支持的漫游模式选择选择SMF为第一会话提供服务。例如，当第一会话支持Local breakout模式时，AMF选择服务网络中的V-SMF为第一会话提供服务；或者，当第一会话支持支持Home routed模式，AMF选择归属网络中的H-SMF为第一会话提供服务。
可选的，如果AMF在步骤206中获得的受限策略包括允许的会话个数，方法还包括：AMF确定终端设备建立的会话个数等于或超过受限策略中允许的会话个数，AMF向终端设备发送拒绝消息。可选的，该拒绝消息可以携带原因值，通知终端设备会话个数受限。或者，如果AMF确定终端设备建立的会话个数不超过受限策略中允许的会话个数，则执行后续步骤212。
212、AMF执行后续第一会话的建立过程，完成第一会话的建立。
此处可以参考现有技术相同，或者，也可以参考图4实施例中的描述。
213、第一会话建立后，终端设备通过第一会话接收来自第三方配置服务器的第三方签约数据。后续进入步骤214a，或者214b。
214a、在接收完第三方签约数据之后，终端设备发起会话释放流程以及去注册流程。
214b、受限注册定时器到期后，AMF发起去注册流程将终端设备从网络中去注册。
如果终端设备在接收完第三方签约数据之后，并没有主动发起会话释放流程以及去注册流程(终端设备可能还发起了其他的业务)，则AMF可以在受限注册定时器到期后，发起去注册流程将终端设备从网络中去注册。
215、终端设备使用第三方签约数据重新请求注册到网络。
具体的，第三方签约数据包括签约凭证，例如是用户证书、设备证书、用户名、密码、token等；此外，还可以包括服务提供者标识SP-ID，用以指示签约凭证对应的服务提供者；此外，还可以包括网络接入和选择信息，如网络选择策略(支持的PLMN ID或者PLMN ID+NPN ID，优先级)，接入信息(如允许使用的CAG列表，只能通过CAG/NPN小区接入网络的指示)，特殊用户标识(用于指示网络进行外部认证或用于网络查询内部签约确定进行外部认证)或者指示终端设备构造特殊用户标识的指示信息。
由上述的实施例描述可知，通过受限定时器限制终端设备与第三方配置服务器进行第三方签约数据配置的时长，如果超出允许的时间后，终端设备仍然驻留在网络中，则网络强制终端设备去注册，防止终端设备长时间恶意驻留或者接入其他业务，此方案实现简单，容易部署实现。
参考图3，本申请实施例提供的另一种通信方法示意图，网络侧允许终端设备建立受限的第二会话，限制终端设备的业务(例如，终端设备通过第二会话只能与网络允许的第三方配置服务器交互)。具体方法，包括以下步骤：
301、终端设备进行注册，可以使用现有的通用注册，也可以使用图2中步骤201-209所示的注册。
302、终端设备向AMF发送NAS消息，NAS消息中包括会话建立请求，用于请求建立第二会话。
可选的，NAS消息中还包括受限DNN。
可选的，会话建立请求中还包括SP-ID。可选的，终端设备可以携带第三方配置服务器的标识SP-ID，指示网络将要通信的第三方配置服务器；可在第205，206，207，208等步骤使用；
303、AMF接收NAS消息，具体过程参考步骤211。
304、AMF向SMF发送N11消息，N11消息中包括上述的会话建立请求。
可选的，N11消息中还包括：受限DNN，SUPI。
可选的，会话建立请求还包括SP-ID；
305、可选的，SMF从UDM获取第三方配置服务器的AS信息，
具体的，SMF向UDM发送Nudm_SDM_Get请求，Nudm_SDM_Get请求中包括SUPI，UDM根据SUPI获取共享签约中的签约配置AS信息。
可选的，SMF向UDM发送的Nudm_SDM_Get请求还可以进一步包括SP-ID；则UDM根据SUPI以及SP-ID获取某个特定SP的第三方配置服务器的AS信息；
具体的，UDM向SMF反馈第三方签约配置AS信息，发送Nudm_SDM_Get响应，Nudm_SDM_Get响应中包括第三方配置服务器的AS信息；
306、可选的，SMF从DN-AAA获取第三方配置服务器的AS信息；
具体的，SMF执行PDU会话二次认证从DN-AAA获取第三方配置服务器的AS信息
可选的，在步骤406中SMF/终端设备发送SP-ID给DN-AAA，从DN-AAA获取特定SP的第三方配置服务器的AS信息；
307、可选的，SMF与PCF交互，从PCF获取第三方配置服务器的AS信息；
其中，PCF可以在任意时刻(例如，在流程开始之前)，动态地从NEF/AF获取签约配置AS信息；
可选的，SMF可以发送SP-ID给PCF，从PCF获取特定SP的第三方配置服务器的AS信息。
308、SMF根据本地配置的第三方配置服务器的AS信息，步骤305的用户签约数据中第三方配置服务器的AS信息，步骤306步的二次认证数据中的第三方配置服务器的AS信息，步骤307的策略数据中的第三方配置服务器的AS信息中一种或多种，确定受限DNN的第三方配置服务器的AS信息，如端口，目标地址，QoS，IP地址，时长等；设置会话的规则，如QoS Rule和PDR/FAR等，限制第二会话的业务信息；
可选的，SMF可以根据受限DNN选择特定UPF；
309、SMF继续执行会话建立流程，完成第二会话的建立，该第二会话为受限会话；
具体的，SMF还可以根据第308步中设置的会话的规则，按照现有流程，设置UPF中的PDR/FAR路由规则，和终端设备上的QoS规则。
310、通过第二会话，终端设备和第三方配置服务器交互接收来自第三方配置服务器的第三方签约数据；
311、在接收完第三方签约数据之后，终端设备发起会话释放流程以及去注册流程。该步骤与步骤214a类似。
312、终端设备使用第三方签约数据重新请求注册到网络。具体的描述可以参考步骤215。
由上述的实施例描述可知，通过建立受限会话，完成第三方签约数据的配置，防止终端设备接入其他业务，此方案实现简单，容易部署实现。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对移动管理网元、终端、数据管理网元、认证服务功能网元或外部实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中，上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图4示出了上述实施例中所涉及的通信装置的一种可能的逻辑结构示意图。该通信装置包括：处理模块401和通信模块402。处理模块401用于对通信装置的动作进行控制管理，例如，处理模块401用于执行在通信装置进行信息/数据处理的步骤。通信模块402用于支持通信装置进行信息/数据发送或者接收的步骤。
在一种可能的实施例中，通信模块可以进一步分为发送模块和接收模块。
在一种可能的实施例中，通信装置还可以包括存储模块403，用于存储通信装置可的程序代码和数据。
(一)一种示例，该通信装置为接入管理网元，例如AMF，或者为应用于接入管理网元中的芯片。在这种情况下，通信模块402，用于支持该通信装置执行上述图2和图3实施例中由接入管理网元执行的处理步骤。通信模块402用于支持该通信装置执行上述图2和图3实施例中的步骤中由接入管理网元执行的收发信息/数据的步骤。在一种可能的实现方式中，具体如下：
处理模块，用于获得配置类型指示信息，根据配置类型指示信息确定执行受限注册；启动受限注册定时器；
受限注册定时器到期后，处理模块，用于通过通信模块发起去注册流程将终端设备从 网络中去注册。
可选的，处理模块用于：从注册请求中获得配置类型指示信息；或者，从来自接入网网元的N2消息中获得配置类型指示信息，其中N2消息包括注册请求；或者，通过通信模块向数据管理网元请求终端设备的用户签约数据，接收数据管理网元返回的配置类型指示信息。
可选的，处理模块，用于获取受限策略，并根据受限策略中的受限注册定时器信息确定受限注册定时器；其中，处理模块通过以下一种或多种方式获取受限策略：通过通信模块从数据管理网元获取受限策略，获取本地配置的受限策略，或者通过通信模块从PCF获取受限策略。
可选的，处理模块用于：通过通信模块接收来自终端设备的NAS消息，NAS消息包括会话建立请求，用于请求建立第一会话。
可选的，NAS消息还包括终端设备请求接入的DNN信息，且受限策略包括允许的DNN信息，处理模块用于：终端设备请求接入的DNN信息是否满足允许的DNN信息，如果满足，则执行第一会话的建立流程。
可选的，受限策略包括SMF选择信息，处理模块用于：根据SMF选择信息选择SMF为第一会话提供服务。
可选的，受限策略包括漫游策略，处理模块用于：根据漫游策略确定第一会话支持的漫游模式为Local breakout模式或者Home routed模式，根据支持的漫游模式选择SMF为第一会话提供服务。
可选的，受限策略包括允许的会话个数处理模块用于：确定终端设备建立的会话个数等于或超过允许的会话个数，通过通信模块拒绝NAS消息。
(二)一种示例，该通信装置为终端设备，例如UE，或者为应用于接入管理网元中的芯片。在这种情况下，通信模块402，用于支持该通信装置执行上述图2和图3实施例中由终端设备执行的处理步骤。通信模块402用于支持该通信装置执行上述图2和图3实施例中的步骤中由终端设备执行的收发信息/数据的步骤。在一种可能的实现方式中，具体如下：
通信模块，用于向网络发送注册请求以注册到网络中；向网络发送会话建立请求以建立第一会话；用于通过第一会话接收来自第三方配置服务器的第三方签约数据；
处理模块在通信模块接收完第三方签约数据之后，通过通信模块发起会话释放流程以及去注册流程；通过通信模块使用第三方签约数据重新注册到网络。
可选的，注册请求中携带配置类型指示，配置类型指示用于指示该注册为受限注册。
可选的，通信模块用于通过RRC接入消息向网络发送注册请求，RRC接入消息携带配置类型指示，配置类型指示用于指示该注册为受限注册。
可选的，通信模块用于终端设备通过NAS消息向网络发送会话建立请求，NAS消息中包括终端设备请求接入的DNN，其中终端设备请求接入的DNN为受限DNN。
(三)一种示例，该通信装置为数据管理网元，例如UDM，或者为应用于数据管理网元中的芯片。在这种情况下，通信模块402，用于支持该通信装置执行上述图2和图3实施例中由数据管理网元执行的处理步骤。通信模块402用于支持该通信装置执行上述图2和图3实施例中的步骤中由数据管理网元执行的收发信息/数据的步骤。在一种可能的实 现方式中，具体如下：
通信模块，用于接收接入管理网元发送的获取用户签约数据的请求，请求中携带用户标识；
处理模块，用于确定用户标识对应的用户签约数据为配置签约数据；通过通信模块向接入管理网元发送配置类型指示，配置类型指示用于指示该注册为受限注册。
可选的，用户标识对应的用户签约数据中包括指示信息，指示信息指示用户签约数据为配置签约数据。
可选的，处理模块，用于数据管理网元获取受限策略，并通过通信模块向接入管理网元发送受限策略，受限策略包括受限注册定时器信息，受限注册定时器信息用于确定受限定时器。
可选的，如果用户签约数据为共享签约数据，处理模块，还用于获取终端设备的设备标识，根据终端设备的设备标识以及共享签约数据中的使用记录判断是否允许终端设备使用共享签约数据，其中，使用记录中包括已经注册过的终端设备的使用历史记录；如果不允许，通过通信模块通知接入管理网元拒绝终端设备。
其中，处理模块401可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块402可以是收发器、收发电路或通信接口等。存储模块403可以是存储器。
当处理模块401为处理器51或处理器55，通信模块402为通信接口53时，存储模块403为存储器42时，本申请所涉及的通信装置可以为图5所示的通信设备。
如图5所示，图5示出了本申请实施例中的一种通信设备的硬件结构示意图。接入管理网元、数据管理网元、终端设备的结构可以参考图5所示的结构。该通信设备包括处理器51，通信线路54以及至少一个通信接口(图5中仅是示例性的以包括通信接口53为例进行说明)。
可选的，该通信设备还可以包括存储器52。
处理器51可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路54可包括一通路，在上述组件之间传送信息。
通信接口53，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器52可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrical ly erasable programmable read-only memory，EEPROM)、只读光盘(compact  disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路54与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器52用于存储执行本申请方案的计算机执行指令，并由处理器51来控制执行。处理器51用于执行存储器52中存储的计算机执行指令，从而实现本申请下述实施例提供的一种通信方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器51可以包括一个或多个CPU，例如图5中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备可以包括多个处理器，例如图5中的处理器51和处理器55。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在本申请实施例中，一种通信方法的执行主体的具体结构，本申请实施例并未特别限定，只要可以通过运行记录有本申请实施例的一种通信方法的代码的程序，以根据本申请实施例的一种通信方法进行通信即可，本申请对此不进行限定。
需要指出的是，本申请各实施例之间可以相互借鉴或参考，例如，相同或相似的步骤，方法实施例和装置实施例之间，均可以相互参考，不予限制。
图6是本申请实施例提供的芯片600的结构示意图。芯片60包括一个或两个以上(包括两个)处理器601和通信接口603。
可选的，该芯片60还包括存储器604，存储器604可以包括只读存储器和随机存取存储器，并向处理器601提供操作指令和数据。存储器604的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory，NVRAM)。
在一些实施方式中，存储器604存储了如下的元素，执行模块或者数据结构，或者他们的子集，或者他们的扩展集。
在本申请实施例中，通过调用存储器604存储的操作指令(该操作指令可存储在操作系统中)，执行相应的操作。
一种可能的实现方式中为：接入管理网元、数据管理网元、终端设备所用的芯片的结构类似，不同的装置可以使用不同的芯片以实现各自的功能。
处理器601控制接入管理网元、数据管理网元、终端设备中任一个的处理操作，处理器601还可以称为中央处理单元(central processing unit，CPU)。
存储器604可以包括只读存储器和随机存取存储器，并向处理器601提供指令和数据。存储器604的一部分还可以包括NVRAM。例如应用中存储器604、通信接口603以及存储器604通过总线系统602耦合在一起，其中总线系统602除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图6中将各种总线 都标为总线系统602。
上述本申请实施例揭示的方法可以应用于处理器601中，或者由处理器601实现。处理器601可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器601中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器601可以是通用处理器、数字信号处理器(digital signal processing，DSP)、ASIC、现成可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器604，处理器601读取存储器604中的信息，结合其硬件完成上述方法的步骤。
一种可能的实现方式中，通信接口630用于执行图2和图3所示的实施例中相应网元的接收和发送的步骤。处理器601用于执行图2和图3所示的实施例中相应网元的处理的步骤。
以上通信单元可以是该装置的一种通信接口，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元是该芯片用于从其它芯片或装置接收信号或发送信号的通信接口，例如芯片的管脚。
图7示出了本申请实施例中所涉及的终端设备的一种可能的设计结构的简化示意图。所述终端700包括发射器701，接收器702和处理器703。其中，处理器703也可以为控制器，图7中表示为“控制器/处理器703”。可选的，所述终端700还可以包括调制解调处理器705，其中，调制解调处理器705可以包括编码器706、调制器707、解码器708和解调器709。
在一个示例中，发射器701调节(例如，模拟转换、滤波、放大和上变频等)输出采样并生成上行链路信号，该上行链路信号经由天线发射给上述实施例中所述的DNS、P-CSCF。在下行链路上，天线接收下行链路信号。接收器702调节(例如，滤波、放大、下变频以及数字化等)从天线接收的信号并提供输入采样。在调制解调处理器705中，编码器706接收要在上行链路上发送的业务数据和信令消息，并对业务数据和信令消息进行处理(例如，格式化、编码和交织)。调制器707进一步处理(例如，符号映射和调制)编码后的业务数据和信令消息并提供输出采样。解调器709处理(例如，解调)该输入采样并提供符号估计。解码器708处理(例如，解交织和解码)该符号估计并提供发送给终端700的已解码的数据和信令消息。编码器706、调制器707、解调器709和解码器708可以由合成的调制解调处理器705来实现。这些单元根据无线接入网采用的无线接入技术(例如，LTE及其他演进系统的接入技术)来进行处理。需要说明的是，当终端700不包括调制解调处理器705时，调制解调处理器705的上述功能也可以由处理器703完成。
处理器703对终端设备700的动作进行控制管理，用于执行上述本申请实施例中由终端设备700进行的处理过程。例如，终端设备703还用于执行图3和图4所示方法中涉及 终端设备的处理过程和/或本申请所描述的技术方案的其他过程。
进一步的，终端设备700还可以包括存储器704，存储器704用于存储终端设备700的程序代码和数据。
本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图2和图3中接入管理网元的功能。
本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图2和图3中终端设备的功能。
本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图2和图3中数据管理网元的功能。
本申请实施例提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图图2和图3中接入管理网元的功能。
本申请实施例提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图2和图3中终端设备的功能。
本申请实施例提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图图2和图3中数据管理网元的功能。
本申请实施例提供一种芯片，该芯片应用于网管网元中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图2和图3中接入管理网元的功能。
本申请实施例提供一种芯片，该芯片应用于Donor节点中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图2和图3中终端设备的功能。
本申请实施例提供一种芯片，该芯片应用于IAB节点中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图2和图3中数据管理网元的功能。
本申请实施例提供一种通信系统，该通信系统包括：接入管理网元和数据管理网元。其中，接入管理网元用于执行图图2和图3中的任一个由接入管理网元执行的步骤，数据管理网元用于执行图图2和图3中的任一个由数据管理网元执行的步骤。
本申请实施例还提供了一种计算机可读存储介质。上述方法实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，则功能可以作为一个或多个指令或代码存储在计算机可读介质上或者在计算机可读介质上传输。计算机可读介质可以包括计算机存储介质和通信介质，还可以包括任何可以将计算机程序从一个地方传送到另一个地方的介质。存储介质可以是可由计算机访问的任何可用介质。
作为一种可选的设计，计算机可读介质可以包括RAM，ROM，EEPROM，CD-ROM或其它光盘存储器，磁盘存储器或其它磁存储设备，或可用于承载的任何其它介质或以指令或数据结构的形式存储所需的程序代码，并且可由计算机访问。而且，任何连接被适当地称为计算机可读介质。例如，如果使用同轴电缆，光纤电缆，双绞线，数字用户线(DSL)或无线技术(如红外，无线电和微波)从网站，服务器或其它远程源传输软件，则同轴电缆，光纤电缆，双绞线，DSL或诸如红外，无线电和微波之类的无线技术包括在介质的定义中。如本文所使用的磁盘和光盘包括光盘(CD)，激光盘，光盘，数字通用光盘(DVD)，软盘 和蓝光盘，其中磁盘通常以磁性方式再现数据，而光盘利用激光光学地再现数据。上述的组合也应包括在计算机可读介质的范围内。
本申请实施例还提供了一种计算机程序产品。上述方法实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，可以全部或者部分得通过计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行上述计算机程序指令时，全部或部分地产生按照上述方法实施例中描述的流程或功能。上述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选的，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选的，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中，ASIC可以设置于终端设备中。可选的，处理器和存储媒介也可以设置于终端设备中的不同的部件中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的 精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (50)

  1. 一种通信方法，其特征在于，包括：
    接入管理网元接收来自终端设备的注册请求；
    所述接入管理网元获得配置类型指示信息，根据所述配置类型指示信息确定执行受限注册；
    所述接入管理网元启动受限注册定时器；
    所述受限注册定时器到期后，所述接入管理网元发起去注册流程将所述终端设备从网络中去注册。
  2. 如权利要求1所述的方法，其特征在于，所述接入管理网元获得所述配置类型指示信息包括：
    所述接入管理网元从所述注册请求中获得所述配置类型指示信息；或者
    所述接入管理网元从来自接入网网元的N2消息中获得所述配置类型指示信息，其中所述N2消息包括所述注册请求；或者
    所述接入管理网元向数据管理网元请求所述终端设备的用户签约数据，接收数据管理网元返回的所述配置类型指示信息。
  3. 如权利要求1或2所述的方法，其特征在于，所述接入管理网元启动所述受限注册定时器之前，所述方法包括：所述接入管理网元获取受限策略，并根据所述受限策略中的受限注册定时器信息确定受限注册定时器；
    其中，所述接入管理网元通过以下一种或多种方式获取所述受限策略：从所述数据管理网元获取所述受限策略，获取本地配置的所述受限策略，或者从PCF获取所述受限策略。
  4. 如权利要求1-3任一所述的方法，其特征在于，所述方法还包括:
    所述接入管理网元根据所述受限注册定时器的时长确定周期性注册定时器或者移动可达定时器的时长，其中，所述周期性注册定时器或者所述移动可达定时器的时长小于或者等于所述受限注册定时器的时长。
  5. 如权利要求1-3任一所述的方法，其特征在于，所述方法还包括:
    所述接入管理网元根据周期性注册定时器或者移动可达定时器的时长确定所述受限注册定时器的时长，其中，所述周期性注册定时器或者所述移动可达定时器的时长小于或者等于所述受限注册定时器的时长。
  6. 如权利要求1-5任一所述的方法，其特征在于，所述方法还包括：所述接入管理网元接收来自所述终端设备的NAS消息，所述NAS消息包括会话建立请求，用于请求建立第一会话。
  7. 如权利要求6所述的方法，其特征在于，所述NAS消息还包括终端设备请求接入的DNN信息，且所述受限策略包括允许的DNN信息，所述方法还包括：所述接入管理网元判断所述终端设备请求接入的DNN信息是否满足所述允许的DNN信息，如果满足，则执行所述第一会话的建立流程。
  8. 如权利要求6或7一所述的方法，其特征在于，所述受限策略包括SMF选择信息，所述方法还包括：所述接入管理网元根据所述SMF选择信息选择SMF为所述第一会话提供服务。
  9. 如权利要求6-8任一所述的方法，其特征在于，所述受限策略包括漫游策略，所述方法还包括：所述接入管理网元根据所述漫游策略确定所述第一会话支持的漫游模式为Local breakout模式或者Home routed模式，根据所述支持的漫游模式选择SMF为所述第一会话提供服务。
  10. 如权利要求6-9任一所述的方法，其特征在于，所述受限策略包括允许的会话个数，所述方法还包括：
    所述接入管理网元确定所述终端设备建立的会话个数等于或超过所述允许的会话个数，接入管理网元拒绝所述NAS消息。
  11. 一种通信方法，其特征在于，包括：
    向网络发送注册请求以注册到网络中；
    向所述网络发送会话建立请求以建立第一会话；
    通过所述第一会话接收来自第三方配置服务器的第三方签约数据；
    在接收完所述第三方签约数据之后，发起会话释放流程以及去注册流程；
    使用所述第三方签约数据重新注册到网络。
  12. 如权利要求11所述的方法，其特征在于，所述注册请求中携带配置类型指示，所述配置类型指示用于指示该注册为受限注册。
  13. 如权利要求11所述的方法，其特征在于，向所述网络发送所述注册请求包括：
    通过无线资源控制RRC接入消息向网络发送注册请求，所述RRC接入消息携带配置类型指示，所述配置类型指示用于指示该注册为受限注册。
  14. 如权利要求11-13任一所述的方法，其特征在于，向所述网络发送的会话建立请求包括：通过NAS消息向所述网络发送所述会话建立请求，所述NAS消息中包括所述请求接入的DNN，其中所述请求接入的DNN为受限DNN。
  15. 如权利要求11-14任一所述的方法，其特征在于，所述方法包括：所述会话建立请求消息包括业务提供者标识SP-ID。
  16. 一种通信方法，其特征在于，包括：
    数据管理网元接收接入管理网元发送的获取用户签约数据的请求，所述请求中携带用户标识；
    所述数据管理网元确定所述用户标识对应的用户签约数据为配置签约数据；
    所述数据管理网元向所述接入管理网元发送配置类型指示，所述配置类型指示用于指示该注册为受限注册。
  17. 如权利要求16所述的方法，其特征在于，所述用户标识对应的用户签约数据中包括指示信息，所述指示信息指示所述用户签约数据为配置签约数据。
  18. 如权利要求16或17所述的方法，其特征在于，所述方法包括：
    所述数据管理网元获取受限策略，并向所述接入管理网元发送所述受限策略，所述受限策略包括受限注册定时器信息，所述受限注册定时器信息用于确定受限定时器。
  19. 如权利要求16-18任一所述的方法，其特征在于，如果所述用户签约数据为共享签约数据，则所述方法包括：
    所述数据管理网元获取终端设备的设备标识，
    根据所述终端设备的设备标识以及共享签约数据中的使用记录判断是否允许所述终 端设备使用所述共享签约数据，其中，所述使用记录中包括已经注册过的终端设备的使用历史记录；
    如果不允许，通知所述接入管理网元拒绝所述终端设备。
  20. 一种接入管理网元，其特征在于，包括：处理模块和通信模块；
    所述处理模块，用于获得配置类型指示信息，根据所述配置类型指示信息确定执行受限注册；启动受限注册定时器；
    所述受限注册定时器到期后，所述处理模块，用于通过通信模块发起去注册流程将所述终端设备从网络中去注册。
  21. 如权利要求20所述的接入管理网元，其特征在于，处理模块用于：
    从所述注册请求中获得所述配置类型指示信息；或者
    从来自接入网网元的N2消息中获得所述配置类型指示信息，其中所述N2消息包括所述注册请求；或者
    通过通信模块向数据管理网元请求所述终端设备的用户签约数据，接收数据管理网元返回的所述配置类型指示信息。
  22. 如权利要求20或21所述的接入管理网元，其特征在于，所述处理模块，用于获取受限策略，并根据所述受限策略中的受限注册定时器信息确定受限注册定时器；
    其中，所述处理模块通过以下一种或多种方式获取所述受限策略：通过通信模块从所述数据管理网元获取所述受限策略，获取本地配置的所述受限策略，或者通过通信模块从PCF获取所述受限策略。
  23. 如权利要求20-22任一所述的接入管理网元，其特征在于，
    所述处理模块用于：根据所述受限注册定时器的时长确定周期性注册定时器或者移动可达定时器的时长，其中，所述周期性注册定时器或者所述移动可达定时器的时长小于或者等于所述受限注册定时器的时长。
  24. 如权利要求20-22任一所述的接入管理网元，其特征在于，
    所述处理模块用于：根据周期性注册定时器或者移动可达定时器的时长确定所述受限注册定时器的时长，其中，所述周期性注册定时器或者所述移动可达定时器的时长小于或者等于所述受限注册定时器的时长。
  25. 如权利要求20-24任一所述的接入管理网元，其特征在于，
    所述处理模块用于：通过通信模块接收来自所述终端设备的NAS消息，所述NAS消息包括会话建立请求，用于请求建立第一会话。
  26. 如权利要求25所述的方法，其特征在于，所述NAS消息还包括终端设备请求接入的DNN信息，且所述受限策略包括允许的DNN信息，所述处理模块用于：所述终端设备请求接入的DNN信息是否满足所述允许的DNN信息，如果满足，则执行所述第一会话的建立流程。
  27. 如权利要求25或26所述的接入管理网元，其特征在于，
    所述受限策略包括SMF选择信息，所述处理模块用于：根据所述SMF选择信息选择SMF为所述第一会话提供服务。
  28. 如权利要求25-27任一所述的接入管理网元，其特征在于，
    所述受限策略包括漫游策略，所述处理模块用于：根据所述漫游策略确定所述第一会 话支持的漫游模式为Local breakout模式或者Home routed模式，根据所述支持的漫游模式选择SMF为所述第一会话提供服务。
  29. 如权利要求25-28任一所述的接入管理网元，其特征在于，
    所述受限策略包括允许的会话个数所述处理模块用于：确定所述终端设备建立的会话个数等于或超过所述允许的会话个数，通过通信模块拒绝所述NAS消息。
  30. 一种装置，其特征在于，包括：处理模块和通信模块；
    所述通信模块，用于向网络发送注册请求以注册到网络中；
    所述通信模块，用于向所述网络发送会话建立请求以建立第一会话；
    所述通信模块，用于通过所述第一会话接收来自第三方配置服务器的第三方签约数据；
    所述处理模块在所述通信模块接收完所述第三方签约数据之后，通过所述通信模块发起会话释放流程以及去注册流程；
    通过所述通信模块使用所述第三方签约数据重新注册到网络。
  31. 如权利要求30所述的装置，其特征在于，所述注册请求中携带配置类型指示，所述配置类型指示用于指示该注册为受限注册。
  32. 如权利要求30所述的装置，其特征在于，所述通信模块用于通过RRC接入消息向网络发送注册请求，所述RRC接入消息携带配置类型指示，所述配置类型指示用于指示该注册为受限注册。
  33. 如权利要求30-32任一所述的装置，其特征在于，所述通信模块用于通过NAS消息向所述网络发送所述会话建立请求，所述NAS消息中包括请求接入的DNN，其中所述请求接入的DNN为受限DNN。
  34. 如权利要求30-33任一所述的装置，其特征在于，所述的装置为终端设备。
  35. 一种数据管理网元，其特征在于，包括：处理模块和通信模块；
    所述通信模块，用于接收接入管理网元发送的获取用户签约数据的请求，所述请求中携带用户标识；
    所述处理模块，用于确定所述用户标识对应的用户签约数据为配置签约数据；通过所述通信模块向所述接入管理网元发送配置类型指示，所述配置类型指示用于指示该注册为受限注册。
  36. 如权利要求35所述的数据管理网元，其特征在于，所述用户标识对应的用户签约数据中包括指示信息，所述指示信息指示所述用户签约数据为配置签约数据。
  37. 如权利要求35或36所述的数据管理网元，其特征在于，所述处理模块，用于所述数据管理网元获取受限策略，并通过通信模块向所述接入管理网元发送所述受限策略，所述受限策略包括受限注册定时器信息，所述受限注册定时器信息用于确定受限定时器。
  38. 如权利要求35-37任一所述的数据管理网元，其特征在于，如果所述用户签约数据为共享签约数据，所述处理模块，还用于获取终端设备的设备标识，根据所述终端设备的设备标识以及共享签约数据中的使用记录判断是否允许所述终端设备使用所述共享签约数据，其中，所述使用记录中包括已经注册过的终端设备的使用历史记录；
    如果不允许，通过所述通信模块通知所述接入管理网元拒绝所述终端设备。
  39. 一种装置，其特征在于，包括：处理器和存储器，所述存储器用于存储指令，当所述装置运行时，所述处理器执行所述存储器存储的所述指令，以使所述装置执行如权利 要求1-10中任一项所述的方法。
  40. 一种装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取所述存储器中的指令并根据所述指令执行如权利要求11-15中任一项所述的方法。
  41. 如权要要求所述40的装置，其特征在于，所述装置为终端设备。
  42. 一种装置，其特征在于，包括处理器和存储器，所述存储器用于存储指令，当所述装置运行时，所述处理器执行所述存储器存储的所述指令，以使所述装置执行如权利要求16-19中任一项所述的方法。
  43. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行如权利要求11-15中任一项所述的方法。
  44. 一种处理器，其特征在于，用于执行如权利要求11-15中任一项所述的方法。
  45. 一种装置，用于执行如权利要求1-10中任一项所述方法。
  46. 一种装置，用于执行如权利要求11-15中任一项所述方法。
  47. 一种装置，用于执行如权利要求16-19中任一项所述方法。
  48. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1-19中任一项所述的方法。
  49. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-19中任一项所述的方法。
  50. 一种通信系统，其特征在于，包括如权利要求20-29中任一项所述的装置，和，如权利要求35-38中任一项所述的装置。
PCT/CN2020/119660 2019-09-30 2020-09-30 一种通信方法及装置 WO2021063413A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20872702.4A EP4030818A4 (en) 2019-09-30 2020-09-30 METHOD AND COMMUNICATION DEVICE
US17/707,438 US20220225212A1 (en) 2019-09-30 2022-03-29 Communication Method And Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910945824.9 2019-09-30
CN201910945824.9A CN112584486B (zh) 2019-09-30 2019-09-30 一种通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/707,438 Continuation US20220225212A1 (en) 2019-09-30 2022-03-29 Communication Method And Apparatus

Publications (1)

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

Family

ID=75117082

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/119660 WO2021063413A1 (zh) 2019-09-30 2020-09-30 一种通信方法及装置

Country Status (4)

Country Link
US (1) US20220225212A1 (zh)
EP (1) EP4030818A4 (zh)
CN (1) CN112584486B (zh)
WO (1) WO2021063413A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023012255A1 (en) * 2021-08-06 2023-02-09 Nokia Technologies Oy Authentication between user equipment and communication network for onboarding process

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115175162A (zh) * 2021-04-06 2022-10-11 华为技术有限公司 通信方法及装置
CN113518459B (zh) * 2021-07-14 2023-07-04 中国联合网络通信集团有限公司 资源调度处理方法、装置及电子设备
CN115706964A (zh) * 2021-08-06 2023-02-17 华为技术有限公司 去注册的方法和通信装置
CN113727329B (zh) * 2021-08-16 2023-05-02 中国联合网络通信集团有限公司 一种通信方法及装置
CN113825225B (zh) * 2021-09-10 2024-02-02 阿里巴巴达摩院(杭州)科技有限公司 专网的漫游注册方法、amf网元、设备及系统
CN114143824A (zh) * 2021-12-07 2022-03-04 西安广和通无线软件有限公司 一种无线通讯模块选网方法及相关装置
CN114978747B (zh) * 2022-06-10 2024-02-06 中国电信股份有限公司 注册认证方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018230941A1 (ko) * 2017-06-14 2018-12-20 삼성전자 주식회사 단말의 망 접속 방법 및 이동성 지원과 데이터 전달 방법 및 장치
KR20190058371A (ko) * 2017-11-21 2019-05-29 한국전자통신연구원 신뢰할 수 없는 비-3gpp 액세스에서의 등록해제 방법 및 장치
CN109964509A (zh) * 2016-11-18 2019-07-02 Lg 电子株式会社 在无线通信系统中选择网络节点的方法及其设备

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8875265B2 (en) * 2012-05-14 2014-10-28 Qualcomm Incorporated Systems and methods for remote credentials management
WO2016086409A1 (zh) * 2014-12-05 2016-06-09 华为技术有限公司 一种接入方法、装置和系统
CN108702724B (zh) * 2016-11-27 2021-06-15 Lg 电子株式会社 无线通信系统中的注销方法及其装置
US20200008052A1 (en) * 2017-01-26 2020-01-02 Telefonaktiebolaget Lm Ericsson (Publ) Attachment of a wireless device to a mobile network operator
US10313997B2 (en) * 2017-02-06 2019-06-04 Industrial Technology Research Institute User equipment registration method for network slice selection and network controller and network communication system using the same
EP3471470B1 (en) * 2017-06-15 2021-03-31 LG Electronics Inc. -1- Method for responding to request and network device
CN109104394B (zh) * 2017-06-20 2022-01-21 华为技术有限公司 会话处理方法和设备
US10986602B2 (en) * 2018-02-09 2021-04-20 Intel Corporation Technologies to authorize user equipment use of local area data network features and control the size of local area data network information in access and mobility management function

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109964509A (zh) * 2016-11-18 2019-07-02 Lg 电子株式会社 在无线通信系统中选择网络节点的方法及其设备
WO2018230941A1 (ko) * 2017-06-14 2018-12-20 삼성전자 주식회사 단말의 망 접속 방법 및 이동성 지원과 데이터 전달 방법 및 장치
KR20190058371A (ko) * 2017-11-21 2019-05-29 한국전자통신연구원 신뢰할 수 없는 비-3gpp 액세스에서의 등록해제 방법 및 장치

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Harmonized solution for support of Non-Public Networks", 3GPP DRAFT; S2-1903385-NPN-23502-HARMONIZED, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Xi’an, China; 20190408 - 20190412, 2 April 2019 (2019-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051719548 *
SAMSUNG, SK TELECOM: "Update on solution #4 for access to non-public networks", 3GPP DRAFT; S2-1811025(WAS1372)(WAS0585)_KI_PRIVATENW_ACCESS_SOLUTION UPDATE#4, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Dongguan, China; 20181015 - 20181019, 18 October 2018 (2018-10-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051539915 *
See also references of EP4030818A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023012255A1 (en) * 2021-08-06 2023-02-09 Nokia Technologies Oy Authentication between user equipment and communication network for onboarding process

Also Published As

Publication number Publication date
CN112584486A (zh) 2021-03-30
EP4030818A1 (en) 2022-07-20
US20220225212A1 (en) 2022-07-14
CN112584486B (zh) 2022-08-09
EP4030818A4 (en) 2023-04-12

Similar Documents

Publication Publication Date Title
WO2021063413A1 (zh) 一种通信方法及装置
US20190253885A1 (en) Security management in communication systems between security edge protection proxy elements
WO2020224622A1 (zh) 一种信息配置方法及装置
WO2021012736A1 (zh) 一种会话管理网元的选择方法、装置及系统
US8909223B2 (en) Multicast optimization and aggregation in an enterprise controller
WO2021232919A1 (zh) 一种网络的接入方法、装置及系统
JP2024029170A (ja) 通信システムにおける統合サブスクリプション識別子管理
US20220110023A1 (en) Method, Apparatus, and System for Managing Background Data Transfer Policy
CN113994633B (zh) 通信系统中的网络功能集合的授权
US20200053126A1 (en) User plane security management in a communication system
WO2020103517A1 (zh) 终端的能力信息的获取方法、装置及系统
US20230164523A1 (en) Communication Method, Device, and System
WO2020249861A1 (en) Communication security between user equipment and third-party application using communication network-based key
JP2021513825A (ja) Ｓｓｃモードを決定するための方法および装置
WO2019174582A1 (zh) 一种消息传输方法和装置
CN110418395B (zh) 能力开放方法、相关装置、系统及介质
WO2020208295A1 (en) Establishing secure communication paths to multipath connection server with initial connection over private network
CN114423074A (zh) 一种通信方法及装置
WO2020183058A1 (en) Communication network-anchored cryptographic key sharing with third-party application
WO2024082880A1 (zh) 一种通信方法及装置
WO2023246649A1 (zh) 通信方法、通信装置及通信系统
WO2024098937A1 (zh) 通信方法、通信装置、及存储介质
WO2021132087A1 (ja) Ａｍｆノード及びその方法
US20230247433A1 (en) Rogue network function detection and isolation in a communication network
WO2024032290A1 (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: 20872702

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020872702

Country of ref document: EP

Effective date: 20220411