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

一种通信方法及装置 Download PDF

Info

Publication number
WO2023213181A1
WO2023213181A1 PCT/CN2023/088506 CN2023088506W WO2023213181A1 WO 2023213181 A1 WO2023213181 A1 WO 2023213181A1 CN 2023088506 W CN2023088506 W CN 2023088506W WO 2023213181 A1 WO2023213181 A1 WO 2023213181A1
Authority
WO
WIPO (PCT)
Prior art keywords
access
information
mobility management
plmn
terminal device
Prior art date
Application number
PCT/CN2023/088506
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 华为技术有限公司
Publication of WO2023213181A1 publication Critical patent/WO2023213181A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • H04W48/04Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information

Definitions

  • the present application relates to the field of communication technology, and in particular, to a communication method and device.
  • terminal equipment is currently supported to communicate with the core network through various types of access.
  • terminal equipment can be accessed through the third generation partnership project (3rd generation partnership project, 3GPP) wireless access technology and Access and core network communication for non-3GPP access technologies.
  • 3GPP third generation partnership project
  • the communications of the multiple accesses of the terminal device may share some parameters. For example, multiple accesses of terminal devices share the non-access stratum (NAS) integrity protection algorithm, or the NAS encryption algorithm, and the globally unique temporary user equipment identity (globally unique temporary UE identity, GUTI), etc.
  • NAS non-access stratum
  • GUTI globally unique temporary user equipment identity
  • the terminal device Since multiple accesses of the terminal device share some parameters, if one access of the terminal device operates on these parameters, such as deleting or modifying them, it will affect the communication of other accesses. For example, if one access terminal device deletes the NAS security context information, the uplink signaling of other access devices cannot be integrity protected and encrypted, and the downlink signaling cannot be received normally due to failure of integrity check. For another example, one access of the terminal device deletes the GUTI, causing some messages of other accesses to be unable to carry the GUTI information. As a result, the PLMN cannot recognize the identity of the terminal device, and the terminal device cannot receive paging from the PLMN.
  • the present application provides a communication method and device to solve the problem of the terminal equipment being unable to communicate normally on other accesses due to the operation of public parameters by some accesses of the terminal equipment.
  • this application provides a communication method.
  • the execution subject of the method may be a terminal device, or may be a chip or circuit or other components used to implement the functions of the terminal device.
  • the method includes: when the terminal device switches the first access of the terminal device from the first PLMN to the second PLMN, if the status of the second access of the terminal device is in the first PLMN is registered on the first PLMN or has been registered on the first PLMN, and determines not to delete the first mobility management parameter of the first access. If the status of the second access of the terminal device is not registered on the first PLMN, it is determined to delete the first mobility management parameter of the first access.
  • the first access and the second access belong to different access types.
  • Whether the terminal device needs to use the first mobility management parameter for communication on the second access can be determined by whether the second access is registered on the first PLMN (that is, the PLMN where the first access is registered). In the embodiment of this application, through When the second access of the terminal device is not registered with the first PLMN, deleting the first mobility management parameter of the first access can reduce the terminal equipment's communication speed without affecting the communication of the second access.
  • the cost of device maintenance information can also prevent the terminal device from using invalid parameters (ie, first mobility management parameters) for communication on the first access, thereby improving the communication performance of the terminal device on the first access.
  • the first mobility management parameter is not deleted when the second access of the terminal device is registered to the first PLMN or is registering on the first PLMN, normal communication of the terminal device on the second access can be ensured.
  • the first access and the second access share the first mobility management parameter.
  • the method before the first access of the terminal device is switched from the first PLMN to the second PLMN, the method further includes: the terminal device determines that the first access has been registered with the first PLMN.
  • the method further includes: if the second access is switched from the first PLMN to the third PLMN, the terminal device determines to delete the first mobility management parameter.
  • the communication of the terminal device on the second access does not use the first mobility management parameter. Therefore, when the second access is handed over from the first PLMN to other PLMN, it will be timely. Deleting the first mobility management parameter can not only reduce the cost of maintaining parameters for the terminal device, but also prevent the terminal device from using invalid parameters (i.e., the first mobility management parameter) on the first access and/or the second access. communicate.
  • the first mobility management parameter includes at least one of the following: a key set identifier or a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • the NAS security context information includes a security encryption algorithm, and the security encryption algorithm is a null encryption algorithm.
  • the above method deletes the first mobility management parameter when the security encryption algorithm is an empty encryption algorithm in the NAS security context information identified by the key set identifier. , which is beneficial to the communication security of terminal equipment.
  • this application provides a communication method.
  • the execution subject of the method may be a terminal device, or may be a chip or circuit or other components used to implement the functions of the terminal device.
  • the method includes: the terminal device obtains the first information through the first access of the terminal device, and determines whether to delete the first access based on the first information and the information of the second access of the terminal device.
  • the first information indicates the reason why the core network device rejects the request of the terminal device, and the first access and the second access belong to different access types.
  • the first mobility can not be deleted when the second access requires the first mobility management parameter.
  • mobility management parameters so that the terminal device can communicate using the first mobility management parameters on the second access, avoiding the occurrence of deletion of the first mobility management parameters of the first access in inappropriate scenarios (for example, on the second access When the access requires the first mobility management parameter), the problem that the second access cannot communicate normally is reduced, and the impact on the communication on the second access is reduced.
  • the terminal device determines whether to delete the first mobility management parameter of the first access, flexibility in processing the first mobility management parameter can be provided, and the accuracy is relatively high.
  • the first access and the second access share the first mobility management parameter.
  • the first information is not applicable to the second access; the terminal device determines whether to delete the first mobility management parameter according to the first information and the information of the second access of the terminal device, including: the terminal device determines whether to delete the first mobility management parameter according to the second access information.
  • the first information and the registration information of the second access determine whether to delete the first mobility management parameter.
  • Whether the terminal device needs to use the first mobility management parameter for communication on the second access can be determined through the registration information of the second access. Therefore, it is possible to avoid deleting the first mobility management parameter when the terminal device uses the first mobility management parameter for communication on the second access, thereby ensuring that the terminal device communicates normally on the second access.
  • the terminal device determines whether to delete the first mobility management parameter based on the first information and the registration information of the second access, including: the terminal device determines to delete when the registration information of the second access meets one of the following conditions: First mobility management parameter: the second access is not registered to the PLMN, or the PLMN registered for the second access is different from the PLMN registered for the first access.
  • the second access is not registered on the PLMN registered with the first access, it can be determined that the terminal device does not need to use the first mobility management parameter for communication on the second access.
  • the terminal device does not need to use the first mobility management parameter for communication on the second access.
  • it can be achieved without affecting the communication of the terminal device on the second access. This reduces the cost of maintaining information for the terminal device, and also prevents the terminal device from using invalid parameters (i.e., first mobility management parameters) for communication on the first access, thereby improving the communication of the terminal device on the first access. performance.
  • the terminal device determines whether to delete the first mobility management parameter based on the first information and the registration information of the second access, including: the terminal device determines not to delete the first mobility management parameter when the registration information of the second access meets the following conditions.
  • First mobility management parameter the PLMN registered for the second access is the same as the PLMN registered for the first access.
  • the terminal device needs to use the first mobility management parameter for communication on the second access.
  • the above method can ensure that the terminal device communicates normally on the second access by not deleting the first mobility management parameter when the terminal device needs to use the first mobility management parameter for communication on the second access.
  • the first information is applicable to the second access; the terminal device determines whether to delete the first mobility management parameter according to the first information and the information of the second access of the terminal device, including: the terminal device determines whether to delete the first mobility management parameter according to the first information, the registration information of the second access and the service information on the second access determine whether to delete the first mobility management parameter, and the service information on the second access is information on whether there is an ongoing emergency service on the second access. .
  • the degradation of communication quality caused by deleting the first mobility management parameter when there is an emergency service on the second access can be reduced, thereby ensuring the normal operation of emergency services on the second access and improving user experience.
  • the emergency service is a service corresponding to a protocol data unit (PDU) session carrying a first identifier, and the first identifier is used to identify that the service performed on the PDU session is an emergency service.
  • PDU protocol data unit
  • the terminal device processes the first mobility management parameter based on the first information, the registration information of the second access, and the service information on the second access, including: the registration information of the terminal device on the second access And the first mobility management parameter is determined to be deleted when the service information on the second access meets one of the following conditions: the second access is not registered with the PLMN; or the PLMN registered by the second access is different from the PLMN registered by the first access. ; Or, the PLMN registered for the second access is the same as the PLMN registered for the first access, and there is no ongoing emergency service on the second access.
  • Invalid parameters ie, first mobility management parameters
  • first mobility management parameters are used for communication on the first access, thereby improving the communication performance of the terminal device on the first access.
  • the terminal device processes the first mobility management parameter based on the first information, the registration information of the second access, and the service information on the second access, including: the registration information of the terminal device on the second access And it is determined not to delete the first mobility management parameter when the service information on the second access meets the following conditions: the PLMN registered by the second access is the same as the one registered by the second access.
  • the PLMN registered with the first access is the same, and there is an ongoing emergency service on the second access.
  • the above can ensure that emergency services on the second access are normally performed, thereby improving user experience.
  • the terminal device determines to delete the first mobility management parameter after the emergency service ends.
  • the cost of maintaining information of the terminal device can be reduced, and the terminal device can also be prevented from using invalid parameters (i.e., the first mobility management parameters) for communication on the first access, thereby improving the performance of the terminal device on the first access. communication performance.
  • the method further includes: the terminal device deletes the second mobility management parameter, and the second mobility management parameter includes at least one of the following: on the second access The last accessed tracking area identifier, or the second accessed tracking area identifier list.
  • the method further includes: the terminal device stops the ongoing service on the second access. Communication resources can be saved through the above design.
  • the method also includes: the terminal device starts a first timer for the second access, and the first timer is used to trigger the terminal device to release the N1 NAS signaling connection; or , release the N1 NAS signaling connection.
  • the terminal device starts a first timer for the second access, and the first timer is used to trigger the terminal device to release the N1 NAS signaling connection; or , release the N1 NAS signaling connection.
  • the method further includes: if there is an ongoing mobility management process on the second access, the terminal device stops the mobility management process. Communication resources can be saved through the above design.
  • the first mobility management parameter includes at least one of the following: a key set identifier or a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • this application provides a communication method.
  • the execution subject of the method may be a core network device, or may be a chip or circuit or other component used to implement the functions of the core network device.
  • the method includes: the core network device sends first information to the terminal device through the first access of the terminal device, and the first information indicates the reason why the core network device rejects the request of the terminal device; the core network device according to the first access of the terminal device.
  • Information and information about the second access of the terminal device determine whether to delete the first mobility management parameter of the first access; wherein the first access and the second access belong to different access types.
  • the first mobility can not be deleted when the second access requires the first mobility management parameter.
  • mobility management parameters so that the terminal device can communicate using the first mobility management parameters on the second access, and avoid the situation where normal communication on the second access cannot be performed due to deletion of the first mobility management parameters of the first access. problem, reducing the impact on communications on the secondary access.
  • the first access and the second access share the first mobility management parameter.
  • the first information is not applicable to the second access; the core network device determines whether to delete the first mobility management parameter based on the first information and the second access information, including: the core network device determines whether to delete the first mobility management parameter based on the first access information. information and the registration information of the second access to determine whether to delete the first mobility management parameter.
  • Whether the core network device needs to use the first mobility management parameter for communication on the second access can be determined through the registration information of the second access. Therefore, it is possible to avoid deleting the first mobility management parameter when the terminal device uses the first mobility management parameter for communication on the second access, thereby ensuring that the terminal device communicates normally on the second access.
  • the core network device determines whether to delete the first mobility management parameter based on the first information and the registration information of the second access, including: the core network device determines whether to delete the first mobility management parameter when the registration information of the second access meets one of the following conditions: Sure Delete the first mobility management parameter: the second access is not registered with the PLMN.
  • the second access is not registered on the PLMN registered with the first access, it can be determined that the terminal device does not need to use the first mobility management parameter for communication on the second access.
  • the terminal device does not need to use the first mobility management parameter for communication on the second access.
  • the core network device determines whether to delete the first mobility management parameter based on the first information and the registration information of the second access, including: the core network device determines when the registration information of the second access meets the following conditions: The first mobility management parameter is not deleted: the PLMN registered for the second access is the same as the PLMN registered for the first access.
  • the terminal device needs to use the first mobility management parameter for communication on the second access.
  • the above method can ensure that the terminal device communicates normally on the second access by not deleting the first mobility management parameter when the terminal device needs to use the first mobility management parameter for communication on the second access.
  • the first information is applicable to the second access; the core network device determines whether to delete the first mobility management parameter based on the first information and the information of the second access, including: the core network device determines whether to delete the first mobility management parameter based on the first information , the registration information of the second access and the service information on the second access determine whether to delete the first mobility management parameter, and the service information on the second access is information on whether there is an ongoing emergency service on the second access.
  • the core network device processes the first mobility management parameter based on the first information, the registration information of the second access, and the service information on the second access, including: the core network device processes the first mobility management parameter on the second access.
  • the first mobility management parameter is determined to be deleted when the registration information and the service information on the second access meet one of the following conditions: the second access is not registered with the PLMN; or the PLMN registered by the second access is different from the PLMN registered by the first access.
  • the PLMN is the same, and there is no ongoing emergency service on the second access.
  • the cost of maintaining information for core network equipment can be reduced without affecting the communication of the terminal equipment on the second access or the ongoing emergency services on the second access.
  • the core network device processes the first mobility management parameter based on the first information, the registration information of the second access, and the service information on the second access, including: the core network device processes the first mobility management parameter on the second access. It is determined not to delete the first mobility management parameter when the registration information and the service information on the second access meet the following conditions: the PLMN registered for the second access is the same as the PLMN registered for the first access, and there is an ongoing connection on the second access. Urgent business.
  • the above can ensure that emergency services on the second access are normally performed, thereby improving user experience.
  • the core network device determines to delete the first mobility management parameter after the emergency service ends.
  • the method further includes: the core network device deletes the second mobility management parameter, and the second mobility management parameter includes at least one of the following: on the second access The last accessed tracking area identifier, or the second accessed tracking area identifier list.
  • the method further includes: the core network device stops the ongoing service on the second access. Communication resources can be saved through the above design.
  • the method also includes: the core network device releases the N1 NAS signaling connection.
  • the core network device releases the N1 NAS signaling connection.
  • the method further includes: if there is a While the mobility management process is in progress, the core network equipment stops the mobility management process. Communication resources can be saved through the above design.
  • the first mobility management parameter includes at least one of the following: a key set identifier or a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • the present application provides a communication method.
  • the execution subject of the method may be a terminal device, or may be a chip or circuit or other components used to implement the functions of the terminal device.
  • the method includes: the terminal device receives first indication information through the first access of the terminal device, and the first indication information indicates whether to delete the first mobility management parameter of the first access; according to the first indication The information determines whether to delete the first mobility management parameter of the first access, and the first access and the second access belong to different access types.
  • the network device instructs the terminal device whether to delete the first mobility management parameter, which can reduce the complexity of the terminal device.
  • the first access and the second access share the first mobility management parameter.
  • the terminal device determines whether to delete the first mobility management parameter based on the first indication information, including: the terminal device determines whether to delete the first mobility management parameter based on the first indication information and the second access information.
  • the first mobility management can not be deleted when the second access requires the first mobility management parameters. parameters, so that the terminal device can communicate using the first mobility management parameters on the second access, and avoid the problem of being unable to communicate normally on the second access due to deletion of the first mobility management parameters of the first access, Reduce impact on communications on the secondary access.
  • the terminal device determines whether to delete the first mobility management parameter based on the first indication information and the second access information, including: the terminal device determines whether to delete the first mobility management parameter based on the first indication information and the second access registration information. Delete the first mobility management parameter.
  • Whether the terminal device needs to use the first mobility management parameter for communication on the second access can be determined through the registration information of the second access. Therefore, it is possible to avoid deleting the first mobility management parameter when the terminal device uses the first mobility management parameter for communication on the second access, thereby ensuring that the terminal device communicates normally on the second access.
  • the terminal device determines whether to delete the first mobility management parameter based on the first indication information and the registration information of the second access, including: if the first indication information indicates to delete the first mobility management parameter, the terminal device The first mobility management parameter is determined to be deleted when the registration information of the second access meets one of the following conditions: the second access is not registered with a PLMN, or the PLMN registered by the second access is different from the PLMN registered by the first access.
  • the second access is not registered on the PLMN registered with the first access, it can be determined that the terminal device does not need to use the first mobility management parameter for communication on the second access.
  • the terminal device does not need to use the first mobility management parameter for communication on the second access.
  • it can be achieved without affecting the communication of the terminal device on the second access. This reduces the cost of maintaining information for the terminal device, and also prevents the terminal device from using invalid parameters (i.e., first mobility management parameters) for communication on the first access, thereby improving the communication of the terminal device on the first access. performance.
  • the terminal device determines whether to delete the first mobility management parameter based on the first indication information and the registration information of the second access, including: if the first indication information indicates to delete the first mobility management parameter, and the The PLMN registered for the second access is the same as the PLMN registered for the first access.
  • the terminal device determines whether to delete the first mobility management parameter based on the service information on the second access.
  • the service information on the second access is the second access. Is there an emergency going on? business information.
  • the terminal device determines whether to delete the first mobility management parameter based on the service information on the second access, including: if there is an ongoing emergency service on the second access, the terminal device determines not to delete the first mobility management parameter. mobility management parameters; or, if there is no ongoing emergency service on the second access, the terminal device determines to delete the first mobility management parameters.
  • the method further includes: the terminal device determines to delete the first mobility management parameter after the emergency service ends.
  • the cost of maintaining information of the terminal device can be reduced, and the terminal device can also be prevented from using invalid parameters (i.e., the first mobility management parameters) for communication on the first access, thereby improving the performance of the terminal device on the first access. communication performance.
  • the method further includes: the terminal device deletes the second mobility management parameter, and the second mobility management parameter includes at least one of the following: on the second access The last accessed tracking area identifier, or the second accessed tracking area identifier list.
  • the method further includes: the terminal device stops the ongoing service on the second access. Communication resources can be saved through the above design.
  • the method also includes: the terminal device starts a first timer for the second access, where the first timer is used to trigger the terminal device to release the N1 NAS signaling connection. ; Or, release the N1 NAS signaling connection.
  • the terminal device starts a first timer for the second access, where the first timer is used to trigger the terminal device to release the N1 NAS signaling connection. ; Or, release the N1 NAS signaling connection.
  • the method further includes: if there is an ongoing mobility management process on the second access, the terminal device stops the mobility management process. Communication resources can be saved through the above design.
  • the first mobility management parameter includes at least one of the following: a key set identifier or a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • the present application provides a communication method.
  • the execution subject of the method may be a core network device, a chip or a circuit, or other components used to implement the functions of the core network device.
  • the method includes: the core network device determines the first indication information, and sends the first indication information to the terminal device through the first access of the terminal device; the first indication information indicates whether to delete the first accessed The first mobility management parameter indicates that the first access and the second access belong to different access types.
  • the network device instructs the terminal device whether to delete the first mobility management parameter, which can reduce the complexity of the terminal device.
  • the first access and the second access share the first mobility management parameter.
  • the core network device determines the first indication information, including: the core network device determines the first indication information based on the second indication information and the second access information, and the second indication information instructs the core network device to reject the terminal device. The reason for the request.
  • the first mobility can not be deleted when the second access requires the first mobility management parameter.
  • mobility management parameters so that the terminal device can communicate using the first mobility management parameters on the second access, and avoid the situation where normal communication on the second access cannot be performed due to deletion of the first mobility management parameters of the first access. problem, degrading the communication on the second access Influence.
  • the second indication information is not applicable to the second access; the core network device determines the first indication information based on the second indication information and the second access information, including: the core network device determines the first indication information based on the second indication information And the registration information of the second access determines the first indication information.
  • Whether the core network device needs to use the first mobility management parameter for communication on the second access can be determined through the registration information of the second access. Therefore, it is possible to avoid deleting the first mobility management parameter when the terminal device uses the first mobility management parameter for communication on the second access, thereby ensuring that the terminal device communicates normally on the second access.
  • the core network device determines the first indication information based on the second indication information and the registration information of the second access, including: the core network device determines the first indication information when the registration information of the second access meets one of the following conditions: The information indicates deletion of the first mobility management parameter: the second access is not registered with the PLMN; or, the core network device indicates not to delete the first mobility management parameter when the registration information of the second access meets the following conditions: The second access has been registered to or is being registered to the PLMN.
  • the second access is not registered on the PLMN registered with the first access, it can be determined that the terminal device does not need to use the first mobility management parameter for communication on the second access.
  • the terminal device does not need to use the first mobility management parameter for communication on the second access.
  • the terminal device needs to use the first mobility management parameter for communication on the second access.
  • the above method can ensure that the terminal device communicates normally on the second access by not deleting the first mobility management parameter when the terminal device needs to use the first mobility management parameter for communication on the second access.
  • the second indication information is applicable to the second access; the core network device determines the first indication information based on the second indication information and the second access information, including: the core network device determines the first indication information based on the second indication information, The registration information of the second access and the service information on the second access determine the first indication information, and the service information on the second access is information on whether emergency services are being performed on the second access.
  • the core network device determines the first indication information based on the second indication information, the registration information of the second access, and the service information on the second access, including: the registration information of the core network device on the second access
  • the first indication information indicates deletion of the first mobility management parameter when the information and the service information on the second access meet one of the following conditions: the second access is not registered with the PLMN; or the second access has been registered with or is registering with the PLMN. PLMN, there is no ongoing emergency service on the second access.
  • the cost of maintaining information for core network equipment can be reduced without affecting the communication of the terminal equipment on the second access or the ongoing emergency services on the second access.
  • the core network device determines the first indication information based on the second indication information, the registration information of the second access, and the service information on the second access, including: the registration information of the core network device on the second access
  • the first indication information indicates not to delete the first mobility management parameter when the information and the service information on the second access meet the following conditions: the second access has been registered or is registering with the PLMN, and there is an ongoing emergency on the second access. business.
  • the above can ensure that emergency services on the second access are normally performed, thereby improving user experience.
  • the first mobility management parameter includes at least one of the following: a key set identifier and a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • the present application also provides a communication device, which has the ability to implement the above-mentioned first or second aspect. Any method provided by the first or fourth aspect.
  • the communication device can be implemented by hardware, or can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a processor, the processor is configured to support the communication device to perform the corresponding functions of the terminal device in the method shown above.
  • the communications device may also include memory, which storage may be coupled to the processor, which holds program instructions and data necessary for the communications device.
  • the communication device further includes an interface circuit, the interface circuit is used to support communication between the communication device and other devices.
  • the communication device includes corresponding functional modules, respectively used to implement the steps in the above method.
  • Functions can be implemented by hardware, or by hardware executing corresponding software.
  • Hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the communication device includes a processing module and a communication module. These modules can perform corresponding functions in the above method examples. For details, see the description in the method provided by the first aspect, the second aspect, or the fourth aspect. , will not be described in detail here.
  • the present application also provides a communication device, which has the ability to implement any of the methods provided in the third aspect or the fifth aspect.
  • the communication device can be implemented by hardware, or can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a processor, the processor is configured to support the communication device to perform corresponding functions of the network device in the method shown above.
  • the communications device may also include memory, which storage may be coupled to the processor, which holds program instructions and data necessary for the communications device.
  • the communication device further includes an interface circuit, the interface circuit is used to support communication between the communication device and other devices.
  • the communication device includes corresponding functional modules, respectively used to implement the steps in the above method.
  • Functions can be implemented by hardware, or by hardware executing corresponding software.
  • Hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the communication device includes a processing module and a communication module. These modules can perform the corresponding functions in the above method examples. For details, please refer to the description in the method provided in the third aspect or the fifth aspect, which is not mentioned here. To elaborate.
  • a communication device including a processor and an interface circuit.
  • the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or to send signals from the processor.
  • the processor is used to implement the method in the foregoing first aspect, second aspect, fourth aspect and any possible design through logic circuits or executing code instructions.
  • a communication device including a processor and an interface circuit.
  • the interface circuit is configured to receive signals from other communication devices other than the communication device and transmit them to the processor or to send signals from the processor.
  • the processor is used to implement the method in the aforementioned third aspect or fifth aspect and any possible design through logic circuits or executing code instructions.
  • a computer-readable storage medium In a tenth aspect, a computer-readable storage medium is provided. Computer programs or instructions are stored in the computer-readable storage medium. When the computer program or instructions are executed by a processor, the above-described first to fifth aspects are implemented. method in any aspect and in any possible design.
  • An eleventh aspect provides a computer program product storing instructions. When the instructions are executed by a processor, any one of the foregoing first to fifth aspects and the method in any possible design are implemented.
  • a twelfth aspect provides a chip system, which includes a processor and may also include a memory for implementing any one of the foregoing first to fifth aspects and any possible design method.
  • the chip system can be composed of Chip composition can also include chips and other discrete devices.
  • a thirteenth aspect provides a communication system, which includes the device (such as terminal equipment) described in the first aspect, and may also include core network equipment.
  • a fourteenth aspect provides a communication system, which includes the device (such as terminal equipment) described in the second aspect and the device (such as core network equipment) described in the third aspect.
  • a fifteenth aspect provides a communication system, which includes the device (such as terminal equipment) described in the fourth aspect and the device (such as core network equipment) described in the fifth aspect.
  • Figure 1 is a schematic diagram of a 5G network architecture based on a service-based architecture according to an embodiment of the present application
  • Figure 2 is a schematic diagram of an untrusted non-3GPP access network architecture according to an embodiment of the present application
  • Figure 3 is a schematic diagram of a trusted non-3GPP access network architecture according to an embodiment of the present application.
  • Figure 4 is a schematic flow chart of a communication method according to an embodiment of the present application.
  • Figure 5 is a schematic flow chart of a communication method according to an embodiment of the present application.
  • Figure 6 is a schematic flow chart of a communication method according to an embodiment of the present application.
  • Figure 7 is a schematic flow chart of a communication method according to an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 1 it is a schematic diagram of the 5G network architecture based on service-oriented architecture.
  • the 5G network architecture shown in Figure 1 can include three parts, namely the terminal equipment part, the data network (DN) and the operator network part. The following is a brief introduction to the functions of some of the network elements.
  • the operator's network may include one or more of the following network elements: authentication server function (AUSF) network element, network exposure function (NEF) network element, policy control function (policy control) function (PCF) network element, unified data management (UDM) network element, unified data repository (UDR), network repository function (NRF) network element, access and mobility management function (access and mobility management function, AMF) network element, session management function (SMF) network element, access network and user plane function (UPF) network element, etc.
  • AUSF authentication server function
  • NEF network exposure function
  • PCF policy control function
  • UDM unified data management
  • UDR unified data repository
  • NRF network repository function
  • SMF session management function
  • UPF user plane function
  • the part other than the wireless access network part may be called the core network part.
  • the operator network also includes an application function (Application Function, AF) network element.
  • the AF network element may not belong to the operator's network but to a third party.
  • Terminal device is a device with wireless transceiver functions that can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons, satellites, etc.).
  • the terminal device can be a mobile phone (mobile phone), tablet computer (pad), wireless Computers with wire transceiver functions, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self driving), remote Wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, and smart home wireless terminals, UE, etc.
  • the above-mentioned terminal device can establish a connection with the operator network through an interface (such as N1, etc.) provided by the operator network, and use data and/or voice services provided by the operator network.
  • the terminal device can also access the DN through the operator network and use the operator services deployed on the DN and/or services provided by third parties.
  • the above-mentioned third party can be a service provider other than the operator's network and terminal equipment, and can provide data and/or voice services for the terminal equipment.
  • the specific manifestations of the above-mentioned third parties can be determined according to the actual application scenarios and are not limited here.
  • the core network part includes user plane functions and control plane functions.
  • User plane functions include UPF network elements. As an interface with the data network, the UPF network element completes user plane data (such as packet packets) forwarding, quality of service (QoS) control, session/flow level-based billing statistics, bandwidth limitation and other functions.
  • user plane data such as packet packets
  • QoS quality of service
  • session/flow level-based billing statistics such as bandwidth limitation and other functions.
  • the control plane function mainly performs user registration and authentication, mobility management, and delivers data packet forwarding strategies and QoS control strategies to the user plane functions.
  • the control plane functions can be further refined to include other network elements besides UPF network elements, such as AMF network elements and SMF network elements.
  • the AMF network element mainly performs the registration process when users access, as well as location management, access authentication/authorization and other functions during user movement. In addition, it is also responsible for transmitting user policies between UE and PCF.
  • the SMF network element mainly establishes corresponding session connections when users initiate services and provides users with specific services, such as delivering data packet forwarding policies, QoS policies and other functions to UPF based on the NG4 interface between SMF and UPF.
  • the AUSF network element is mainly responsible for authenticating users, determining the legitimacy of user equipment, and determining whether users or equipment are allowed to access the network.
  • the UDM network element is mainly responsible for storing contract data of user equipment, user access authorization and other functions.
  • UDR is mainly responsible for the access function of contract data, policy data, application data and other types of data.
  • PCF network element is mainly responsible for delivering service-related policies to AMF or SMF.
  • NEF network elements are mainly used to support the opening of capabilities and events.
  • the AF network element mainly transmits the requirements of the application side to the network side to the PCF, allowing the PCF to generate corresponding policies.
  • AF can be a third-party functional entity or an application service deployed by an operator, such as the Internet Protocol (Internet Protocol, IP) Multimedia Subsystem (IP Multimedia Subsystem, IMS) voice call service.
  • IP Internet Protocol
  • IMS IP Multimedia Subsystem
  • NRF network elements can be used to provide network element discovery functions and provide network element information corresponding to network element types based on requests from other network elements.
  • NRF also provides network element management services, such as network element registration, update, de-registration, network element status subscription and push, etc.
  • DN is a network located outside the operator's network.
  • the operator's network can access multiple DNs.
  • a variety of services can be deployed on the DN, which can provide data and/or voice services to terminal devices.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is the internal office network of a company.
  • the mobile phones or computers of employees of the company can be used as terminal devices.
  • the employees' mobile phones or computers can access information and data resources on the company's internal office network.
  • Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • the meaning of these interface serial numbers can be found in the meaning defined in the 3rd generation partnership project (3GPP) standard protocol, which is not limited here.
  • the access network is a subnetwork of the operator's network and an implementation system between service nodes and terminal equipment in the operator's network.
  • a terminal device To access the operator's network, a terminal device must first pass through the access network, and then connect to the service node of the operator's network through the access network.
  • the access network may include a 3GPP access network and/or a non-3GPP access network, that is, the terminal device may use a 3GPP access network (or 3GPP access technology) and/or a non-3GPP access network (or N3GPP access technology). ) access the core network.
  • Non-3GPP access network refers to access networks other than 3GPP, such as wireless local area networks (WLAN), wireless fidelity (Wi-Fi) network, and worldwide interoperability for microwave access , WiMAX), fixed network, etc.
  • the non-3GPP access network may include a trusted non-3GPP access network, an untrusted non-3GPP access network, a wired network, etc.
  • the untrusted non-3GPP access network may include, for example, untrusted WLAN, untrusted Wi-Fi network, untrusted WiMAX, etc.
  • a trusted non-3GPP access network may include, for example, a trusted WLAN, a trusted Wi-Fi network, a trusted WiMAX, etc.
  • a wired network may include, for example, a fixed network, etc.
  • the access of a terminal device to a 3GPP access network may be called 3GPP access, and the access of a terminal device to a non-3GPP access network may be called non-3GPP access.
  • the access equipment of the 3GPP access network may be equipment that provides wireless communication functions for terminal equipment.
  • the access equipment of the 3GPP access network may also be called access network equipment.
  • the access equipment of the 3GPP access network includes but is not limited to: next-generation base station (g nodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), Node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.
  • the access equipment of the untrusted non-3GPP access network can be called non-3GPP interworking function (N3IWF) equipment or next generation packet data gateway (ngPDG).
  • N3IWF network element is similar to the evolved packet data gateway (ePDG) in long term evolution (LTE). It is used in 5G when terminal equipment accesses the core network through the non-3GPP access network. Establish an Internet protocol security (IPsec) tunnel with the terminal device. In the future 5G definition, the name of N3IWF may change.
  • IPsec Internet protocol security
  • This application only uses non-3GPP network access gateway as an example of N3IWF device.
  • N3IWF devices may include routers, etc.
  • Access devices in the trusted non-3GPP access network may include trusted non-3GPP access points (TNAP) and/or trusted non-3GPP access gateways (trusted non -3GPP gateway function, TNGF).
  • TNAP is used to communicate with terminal equipment
  • TNGF is used to communicate with core network equipment.
  • TNAP can include, but is not limited to, WLAN access points (access points, APs), fixed access network equipment (fixed access network, FANs), switches, routers, etc.
  • the terminal device accesses the core network through the 3GPP access network and the untrusted non-3GPP access network, as shown in Figure 2.
  • the interface between UPF and 3GPP access network element can be called N3 interface
  • the interface between UPF and N3IWF device can be called N3 interface
  • the interface between 3GPP access network element and AMF can be called It is the N2 interface
  • the interface between the N3IWF device and the AMF can be called the N2 interface.
  • the other interfaces are shown in Figure 2 and will not be explained one by one here.
  • the terminal device accesses the core network through the 3GPP access network and the trusted non-3GPP access network, as shown in Figure 3.
  • the interface between UPF and the 3GPP access network element may be called the N3 interface
  • the interface between the UPF and the TNGF network element may be called the N3 interface.
  • the interface between the 3GPP access network element and the AMF can be called the N2 interface
  • the interface between the TNGF network element and the AMF can be called the N2 interface
  • the interface between the TNGF network element unified TNAP can be called Ta
  • the other interfaces are as shown in the figure 3, and will not be explained one by one here.
  • FIGS 2 and 3 are only schematic architectural diagrams of the untrusted non-3GPP access network and the trusted non-3GPP access network, and do not limit the access network through which the terminal device accesses the core network. type and quantity.
  • the terminal equipment can access the core network through two or more access networks.
  • the access network through which the terminal device accesses the core network may be, but is not limited to, one or more of the following access network types: 3GPP access network, untrusted non-3GPP access network, or trusted
  • the non-3GPP access network can also be other access network types that will appear in future communication development.
  • the network types included in the untrusted non-3GPP access network and the trusted non-3GPP access network can be found in the previous article about the untrusted non-3GPP access network and the trusted non-3GPP access network. The introduction of the network will not be repeated here.
  • the access of the terminal equipment in the 3GPP access network can be called 3GPP access
  • the access of the terminal equipment in the non-3GPP access network can be called non-3GPP access.
  • 3GPP access and non-3GPP access are only exemplary names.
  • 3GPP access can also be described as 3GPP access link, 3GPP transmission channel, 3GPP transmission path, 3GPP transmission link, and 3GPP communication link. wait.
  • the communication link is based on 3GPP access technology, it can be understood as 3GPP access as described in this application.
  • Non-3GPP access can also be described as non-3GPP access link, non-3GPP transmission channel, non-3GPP transmission path, non-3GPP transmission link, etc. As long as the communication link is based on non-3GPP access technology, it can be understood as non-3GPP access as described in this application.
  • the first access mentioned in the following of this application may also be called a first access link, a first transmission channel, a first transmission path, a first transmission link, a first communication link, etc.
  • the second access mentioned below may also be called a second access link, a second transmission channel, a second transmission path, a second transmission link, a second communication link, etc.
  • the above network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the above network elements or functions can be divided into one or more services.
  • instances of the above functions, or instances of services included in the above functions, or service instances that exist independently of network functions can be called service instances.
  • the above network element a may be abbreviated as a.
  • the AF network element may be abbreviated as AF
  • the NEF network element may be abbreviated as NEF
  • the AMF network element may be abbreviated as AMF, and so on.
  • FIGS. 1 to 3 are only examples of applicable network architectures, and an actual applied network architecture may include more or fewer network elements than those in FIGS. 1 to 3 .
  • the names of each network element used in the above embodiments of the present application may maintain the same functions in future communication systems, but the names will change.
  • Mobility management parameters may include, but are not limited to, key set identifiers (ngKSI or eKSI), Or parameters such as globally unique temporary UE identity (GUTI), or the tracking area identifier (tracking zrea identity, TAI) of the last accessed tracking area of the last visit.
  • ngKSI or eKSI key set identifiers
  • GUI globally unique temporary UE identity
  • TAI tracking zrea identity
  • the key set identifier is used to identify NAS security context information.
  • the NAS security context information may include but is not limited to: NAS integrity protection algorithm, or NAS encryption algorithm, AMF key (KAMF) in the service network, user equipment (user equipment, UE) security capability information and other information.
  • NAS integrity protection algorithm or NAS encryption algorithm
  • AMF key AMF key
  • UE user equipment
  • the NAS integrity protection algorithm which can also be called 5G integrity protection algorithm, integrity protection algorithm, etc., is used to verify the integrity of NAS messages.
  • NAS encryption algorithm which can also be called 5G encryption algorithm, secure encryption algorithm, etc., is used to encrypt NAS messages.
  • GUTI It is a temporary identifier assigned to the UE by the core network.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects are in an “or” relationship.
  • “At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • At least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, and timing of multiple objects. , priority or importance, etc.
  • first access and the second access are just to distinguish different accesses, but do not indicate the difference in priority or importance of the two accesses.
  • the terminal device can communicate with the core network through multiple accesses.
  • the terminal device can communicate with the core network through 3GPP access and non-3GPP access.
  • the communication of the multiple accesses of the terminal device may share some parameters, that is, the terminal device and the core network device maintain a set of parameters. For example, in order to achieve password separation and replay protection, multiple accesses to terminal devices share NAS security context information and GUTI.
  • the terminal device Since multiple accesses of the terminal device share some parameters, if one access of the terminal device operates on these parameters, it will affect the communication of other accesses. For example, the terminal device receives a rejection message through access A, and the rejection message carries a cause value. The terminal device may delete the key set identifier and/or GUTI of access A based on the cause value.
  • the reason value carried in the rejection message is #3 or #6, and the reason value indicates an illegal terminal (Illegal UE).
  • the terminal device can perform at least one of the following processes: update the 5GS status to 5U3 ROAMING NOT ALLOWED; delete the GUTI, TAI, TAI list and password of the last visited tracking area.
  • One or more of the key set identifiers in the case of PLMN, consider the universal subscriber identity module (USIM) as invalid for 5GS services until the universal integrated circuit card (universal subscriber identity module) containing the USIM is turned off or deleted. integrated circuit card (UICC) or timer T3245 expires.
  • USB universal subscriber identity module
  • UICC integrated circuit card
  • the reason value carried in the rejection message is #7: the reason value indicates that 5GS services are not allowed (5GS services not allowed).
  • the terminal device can have at least one of the following processing: update the 5GS status to 5U3 roaming not allowed; delete the GUTI, TAI of the last visited tracking area, TAI list and key set identification. One or more; in case of PLMN, treat USIM as invalid for 5GS services until Close or delete the UICC containing USIM or timer T3245 expires.
  • the reason value carried in the rejection message is #11: the reason value indicates that PLMN is not allowed (PLMN not allowed).
  • the terminal device can have at least one of the following processing: update the 5GS status to 5U3 roaming not allowed; delete the GUTI, TAI of the last visited tracking area, TAI list and key set identification. One or more items.
  • the reason value carried in the rejection message is #72: the reason value indicates that non-3GPP access to 5G Core Network (5GCN) is not allowed (non-3GPP access to 5GCN not allowed).
  • the terminal device can have at least one of the following processing: if accessing the core network through non-3GPP, update the 5GS status to 5U3 roaming not allowed; delete the GUTI and the last visited tracking area One or more of the TAI, TAI list, and key set identifier.
  • the reason value carried in the rejection message is #12: the reason value indicates that the tracking area is not allowed (Tracking area not allowed).
  • the terminal device can have at least one of the following processing: update the 5GS status to 5U3 roaming not allowed; delete the GUTI, TAI of the last visited tracking area, TAI list and key set identification. One or more items; resets the registration attempt counter.
  • the reason value carried in the rejection message is #78: the reason value indicates that the PLMN is not allowed to operate at the current terminal equipment location (PLMN is not allowed to operate at the present UE location).
  • the terminal device can have at least one of the following processing: update the 5GS status to 5U3 roaming not allowed; delete the GUTI, TAI of the last visited tracking area, TAI list and key set identification. One or more items.
  • the terminal device Since the terminal device maintains a set of NAS security context information and a GUTI for access A and access B, if the key set identifier of access A is deleted, the NAS security context information of access A and access B will be deleted. As a result, the uplink signaling accessed by B cannot be integrity protected and encrypted, and the downlink signaling cannot be received normally due to failed integrity check. If the GUTI of access A is deleted, some messages of access B will not be able to carry GUTI information. As a result, the PLMN will not be able to identify the identity of the terminal equipment, and the terminal equipment will not be able to receive paging from the PLMN.
  • embodiments of the present application provide a communication method and device to solve the problem of the terminal device being unable to communicate normally on other accesses due to the operation of public parameters by some accesses of the terminal device.
  • the method and the device are based on the same concept. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated points will not be repeated.
  • the communication method provided by this application can be applied to various communication systems, for example, it can be the Internet of Things (IoT), narrowband Internet of things (NB-IoT), long term evolution (long term evolution) , LTE), it can also be the fifth generation (5G) communication system, it can also be a hybrid architecture of LTE and 5G, it can also be a 5G new radio (NR) system, and 6G or new communications emerging in future communication development. system etc.
  • the communication system described in this application can also be a machine to machine (machine to machine, M2M) network, a non-terrestrial network (non-terrestrial network, NTN) network or other networks.
  • "if" can also be described as “in the case of" or "if” or “when" and so on.
  • the status of the second access of the terminal device is being registered on the first PLMN or has been registered on the first PLMN
  • it can also be described as "If the status of the second access of the terminal device is being registered on the first PLMN” Betting on PLMN registered or registered on the first PLMN", or "when the status of the second access of the terminal device is registering on the first PLMN or registered on the first PLMN” or “when the terminal device's second access status is registering on the first PLMN or registered on the first PLMN”
  • the status of the second access is "registering on the first PLMN or already registered on the first PLMN” and so on.
  • switching from... to! can also be described as “switching from (or from)... to!, or “reselecting from (or from)... to! or “from (or chosen from)... to! or “from (or from)... to! or “from (or from)... to! or “from (or from)... to ......”wait.
  • the first access of the terminal equipment is switched from the first PLMN to the second PLMN
  • the first access of the terminal equipment is switched from (or by) the first PLMN to the second PLMN
  • the first access of the terminal device is reselected from (or by) the first PLMN to the second PLMN
  • the first access of the terminal equipment changes from (or from) the first PLMN to the second PLMN
  • the first access of the terminal equipment changes from (or from) the first PLMN to the second PLMN
  • the first access of the terminal equipment changes from (or from) the first PLMN to the second PLMN
  • the terminal equipment The first access is changed from (or by) the first PLMN to the second PLMN” and so on.
  • the following description takes a terminal device accessing the core network through the first access and the second access as an example.
  • the first access and the second access belong to different access types, or can also be described as having different access technologies.
  • the first access is a 3GPP access
  • the second access is a trusted non-3GPP access or an untrusted non-3GPP access.
  • the first access is a trusted non-3GPP access or an untrusted non-3GPP access
  • the second access is a 3GPP access.
  • the first access is a trusted non-3GPP access
  • the second access is an untrusted non-3GPP access
  • the first access is an untrusted non-3GPP access
  • the second access is a trusted non-3GPP access.
  • the embodiments of the present application do not limit the terminal device to only have two accesses.
  • the terminal device can also access through the first access, the second access, and other accesses (such as the third access, The fourth access, etc.) access the core network.
  • the other accesses, the first access, and the second access all belong to different access types, that is, the corresponding (or applied) access technologies are different.
  • the terminal device can communicate with the core network device through the access device of the access network.
  • terminal equipment can communicate with core network equipment through the access network equipment.
  • terminal equipment can communicate with core network equipment through N3IWF equipment.
  • the embodiment of the present application can be applied to a scenario where the first mobility management parameter of the first access of the terminal device needs to be deleted. Wherein, if the PLMN registered for the first access and the PLMN registered for the second access are the same, the first access and the second access share the first mobility management parameter.
  • the first mobility management parameter may include at least one of the following: key set identification, or GUTI.
  • the first mobility management parameters may also include other parameters common to the first access and the second access, which will not be listed here.
  • Scenario 1 The first access of the terminal device is switched from the first PLMN to the second PLMN.
  • the second PLMN is not the first access registered PLMN (RPLMN)
  • the second The PLMN is also not the equivalent PLMN (EPLMN) of the first access.
  • the terminal device obtains the first information through the first access, and the first information indicates the reason why the core network device rejects the request of the terminal device.
  • the terminal device may determine that the first mobility management parameter of the first access needs to be deleted according to the first information.
  • the terminal device may receive a registration rejection message through the first access, and the registration rejection message may carry a cause value.
  • the terminal device may receive a service rejection message through the first access, where the service rejection message carries a cause value.
  • the terminal device may receive a deregistration request message through the first access, where the deregistration request message carries the cause value.
  • the cause value can be understood as the above-mentioned first information.
  • the terminal device may determine that the first mobility management parameter of the first access needs to be deleted.
  • Scenario 3 The scenario where the first mobility management parameter of the first access needs to be deleted may also be: the terminal device receives the first message through the first access. In this example, the terminal device may determine that the first mobility management parameter of the first access needs to be deleted after receiving the first message. The first message does not carry the first information.
  • the first message may be an authentication rejection message received by the terminal device through the first access or other messages.
  • the terminal device After the terminal device receives the authentication rejection message through the first access, if the authentication rejection message has successfully passed the NAS integrity check, it can determine the first access point of the first access. Mobility management parameters need to be deleted.
  • S401 The terminal device determines that the first access is switched from the first PLMN to the second PLMN.
  • the first access has been registered with the first PLMN.
  • the terminal device may determine that the first access is switched from the first PLMN to the second PLMN in the following manner: the first access of the terminal device is switched from the first cell to the second cell, where, The PLMN corresponding to the first cell is the first PLMN.
  • the terminal device receives system information broadcast by the second cell through the first access, and the system information may carry PLMN information to which the second cell belongs.
  • the terminal device may determine that the first access is switched from the first PLMN to the second PLMN according to the PLMN information carried in the system information and the locally saved PLMN information of the first access.
  • the terminal device may determine that the first access is switched from the first PLMN to the second PLMN in the following manner: the terminal device determines that the connection with the first access device is interrupted, and the terminal device determines that the connection with the first access device is interrupted.
  • the PLMN corresponding to an access device is the first PLMN.
  • the terminal device sends a request message to the second access device.
  • the request message is used to request to establish a communication connection with the second access device.
  • the PLMN corresponding to the second access device is the second PLMN.
  • the terminal device receives a response message from the second access device, where the response message is used to instruct the terminal device to access the second access device.
  • the terminal device determines that the first access is switched from the first PLMN to the second PLMN according to the PLMN corresponding to the second access device.
  • first access device and the second access device please refer to the relevant description of the access device of the non-3GPP access network in the previous network architecture introduction.
  • the second access deregisters from the first PLMN (or deregisters or leaves the first PLMN, etc.), it may be determined to delete the first mobility management parameter of the first access.
  • an implementation scenario in which the second access is deregistered from the first PLMN is that the second access is switched from the first PLMN to the third PLMN.
  • the third PLMN is different from the first PLMN, and the third PLMN and the second PLMN may be the same or different.
  • the first mobility management parameter includes a key set identifier
  • the NAS security context information identified by the key set identifier includes a security encryption algorithm.
  • the security encryption algorithm may be an empty encryption algorithm, for example , 5G-EA0 algorithm or other algorithms that will appear in future communication development.
  • the terminal device may determine that the security encryption algorithm is a null encryption algorithm.
  • the first mobility management parameter is beneficial to the communication security of the terminal device.
  • the terminal device may perform corresponding actions after determining not to delete the first mobility management parameter.
  • the first mobility management parameter is not deleted, or the first mobility management parameter is retained, or the first mobility management parameter is not processed, and so on.
  • the terminal device may perform corresponding actions after determining to delete the first mobility management parameter.
  • the first mobility management parameter is deleted.
  • deleting the key set identifier can be achieved in at least one of the following ways:
  • KAMF key "one or more of the KAMF key, K'AMF, NAS encryption key and NAS integrity key is invalid” can also be described as the NAS security context information related to the key set identifier is invalid or no longer valid. .
  • deleting the GUTI can be achieved in the following manner: setting the GUTI to invalid.
  • Whether the terminal device needs to use the first mobility management parameter for communication on the second access can be determined by whether the second access is registered on the first PLMN (that is, the PLMN where the first access is registered).
  • the first mobility management parameter of the first access can be deleted without affecting the operation of the terminal device on the second access.
  • the cost of maintaining information of the terminal device can be reduced, and the terminal device can also be prevented from using invalid parameters (i.e., the first mobility management parameters) for communication on the first access, thereby improving the performance of the terminal device on the first access. communication performance.
  • the first mobility management parameter is not deleted when the second access of the terminal device is registered to the first PLMN or is registering on the first PLMN, normal communication of the terminal device on the second access can be ensured.
  • the core network device sends the first information to the terminal device through the first access.
  • the terminal device obtains the first information through the first access.
  • the first information may be carried in a registration rejection message, a service rejection message, or a de-registration message. It should be understood that these are just some examples and do not limit the specific messages carrying the first information.
  • the core network device may be the core network device accessed by the first access.
  • the terminal device determines whether to delete the first mobility management parameter of the first access based on the first information and the information of the second access.
  • the information of the second access may include at least one of the following: registration information of the second access, or service information of the second access, or the information of the second access may also include other information, which will not be discussed here. Specific limitations.
  • the registration information may represent the PLMN registration status of the second access, and the service information on the second access is information on whether emergency services are ongoing on the second access.
  • the terminal device may determine based on the first information that the first mobility management parameter of the first access needs to be deleted. The terminal device determines whether to delete the first mobility management parameter of the first access according to the information of the second access.
  • the terminal device determines that the first mobility management parameter of the first access needs to be deleted based on the first information.
  • the first information may be applicable to the first access, but not to the second access.
  • the first information may also be applicable to both the first access and the second access. Whether the first information is applicable to the first access and the second access will be described below in combination with specific cause values.
  • the reason value indicates an illegal terminal, that is, the terminal device is not allowed. Therefore, neither the first access nor the second access of the terminal device is allowed, that is, the first information is applicable to both the first access and the second access.
  • the reason value indicates that the 5GS service is not allowed, that is, the 5GS service of the terminal device is not allowed. Therefore, neither the first access nor the second access of the terminal device is allowed, that is, the first information is applicable to both the first access and the second access.
  • the reason value indicates that the PLMN is not allowed, that is, the first accessed PLMN is not allowed. If the PLMN registered (or registered) for the second access is the same as the PLMN registered for the first access, the first information is also applicable to the second access. If the PLMN registered (or registered) for the second access is different from the PLMN registered for the first access, the first information is not applicable to the second access.
  • the reason value indicates that non-3GPP access is not allowed for 5GCN.
  • the terminal device receives the cause value #72 through the first access. It can be seen that the first access is a non-3GPP access, and the first information is applicable to the first access. If the second access is a 3GPP access, the first information is not applicable to the second access.
  • the reason value indicates that the tracking area is not allowed, and the reason value is applicable to 3GPP access.
  • the terminal device receives the cause value #12 through the first access. It can be seen that the first information is applicable to the first access, that is, the first access is a 3GPP access. If the second access is a non-3GPP access, the first information is not applicable to the second access.
  • the reason value indicates that the PLMN is not allowed to operate under the current End device location operation. This reason value applies to 3GPP access.
  • the terminal device receives the cause value #78 through the first access. It can be seen that the first information is applicable to the first access, that is, the first access is a 3GPP access. Therefore, if the second access is a non-3GPP access, the first information is not applicable to the second access.
  • the terminal device determines whether to delete the first mobility management parameter of the first access based on the information of the second access.
  • the implementation method is explained.
  • the terminal device may determine whether to delete the first mobility management parameter of the first access according to the registration information of the second access.
  • the terminal device may determine to delete the first mobility management parameters of the first access when the registration information of the second access meets one of the following conditions: the second access is not registered with the PLMN, or the second access is registered with the PLMN.
  • the PLMN is different from the PLMN registered with the first access.
  • the terminal device may determine not to delete the first mobility management parameter of the first access when the registration information of the second access satisfies the following conditions: the PLMN registered for the second access is the same as the PLMN registered for the first access.
  • the PLMN registered for the second access is different from the PLMN registered for the first access. It can be understood that the PLMN registered for the second access is the same as the PLMN currently registered for the first access, and the PLMN registered for the second access is not the third access registered PLMN.
  • the first accessed RPLMN, the second PLMN is not the first accessed EPLMN.
  • the PLMN registered by the second access mentioned below is the same as the PLMN registered by the first access. It can be understood that the PLMN registered by the second access is the same as the PLMN currently registered by the first access, or the PLMN registered by the second access.
  • the registered PLMN is the first accessed RPLMN, or the second PLMN is the first accessed EPLMN.
  • the terminal device can determine whether to delete the first mobility management of the first access based on the registration information of the second access and the service information on the second access. parameter.
  • the terminal device may determine to delete the first mobility management parameters of the first access when the registration information of the second access meets one of the following conditions: the second access is not registered with the PLMN; or, the second access is registered The PLMN is different from the PLMN registered for the first access.
  • the terminal device may determine to delete the first mobility management parameters of the first access when the registration information of the second access and the service information on the second access meet one of the following conditions: the PLMN registered by the second access is not the same as the first mobility management parameter of the first access.
  • the registered PLMN is the same, and there is no ongoing emergency service on the second access.
  • the terminal device may determine not to delete the first mobility management parameters of the first access when the registration information of the second access and the service information on the second access meet the following conditions: the PLMN registered by the second access is the same as the first mobility management parameter of the first access.
  • the registered PLMN is the same, and emergency services are in progress on the second access.
  • the terminal device may determine to delete the first mobility management parameter of the first access after the emergency service on the second access ends.
  • the above describes the implementation manner in which the terminal device determines whether to delete the first mobility management parameter of the first access based on the information of the second access.
  • the behavior of the core network device after sending the first information may also determine whether to delete the first mobility management parameter of the first access based on the first information and the information of the second access.
  • the core network device determines whether to delete the first mobility management parameter of the first access based on the first information and the second access information, and the terminal device determines whether to delete the first mobility management parameter based on the first information and the second access information.
  • the implementation of deleting the first mobility management parameter of the first access is similar. The difference is that the terminal device can determine to delete the first mobility management parameters of the first access when the registration information of the second access meets one of the following conditions: the second access is not registered with the PLMN; or, the second access is registered with the PLMN.
  • the PLMN is different from the PLMN registered with the first access.
  • the core network device determines to delete the first mobility management parameter of the first access when the registration information of the second access meets one of the following conditions: the second access is not registered with the PLMN. For details, reference may be made to the implementation of the terminal device determining whether to delete the first mobility management parameter of the first access based on the first information and the information of the second access.
  • the terminal equipment and/or core network equipment can also implement one or more of the following four solutions:
  • Solution 1 If it is determined to delete the first mobility management parameter of the first access, the second mobility management parameter and/or the third mobility management parameter may be deleted.
  • the second mobility management parameter includes at least one of the following: the TAI of the last visited tracking area on the second access, or the TAI list of the second access (TAI list).
  • the third mobility management parameter includes at least one of the following: the TAI of the last visited tracking area on the first access, or the TAI list of the first access.
  • TAI of the last accessed tracking area on the second access can also be described as the TAI of the last accessed tracking area corresponding to the second access, or the terminal device on the second access corresponding to the TAI of the last accessed tracking area.
  • TAI of the last visited tracking area on the first access can also be described as the TAI of the last visited tracking area corresponding to the first access, or the terminal device is in the access network corresponding to the first access.
  • the second mobility management parameter and the third mobility management parameter may also include other parameters, which are not specifically limited here.
  • Option 2 If it is determined to delete the first mobility management parameter, ongoing services on the second access can be stopped.
  • stop in the embodiment of this application can also describe termination, cancellation, suspension, interruption, etc.
  • the terminal device can start the first timer of the second access or release the N1 NAS signaling connection of the second access.
  • the core network equipment can release the N1 NAS signaling connection of the second access.
  • the first timer is used to trigger the terminal device to release the N1 NAS signaling connection of the second access.
  • the first timer is used to allow the core network device to release the N1 NAS signaling connection of the second access.
  • the terminal device may release the second accessed N1 NAS signaling connection when the first timer expires.
  • the terminal device can stop the first timer.
  • Option 4 If it is determined to delete the first mobility management parameter, if there is an ongoing mobility management process on the second access, the mobility management process can be stopped.
  • the mobility management process may include one or more of the following processes: common procedures (5GMM common procedures), specific procedures (5GMM specific procedures:), connection management procedures (5GMM connection management procedures), etc.
  • common procedures 5GMM common procedures
  • specific procedures 5GMM specific procedures:
  • connection management procedures 5GMM connection management procedures
  • the public process may include but is not limited to: identity authentication process, authentication process, security mode control process, UE configuration update process, uplink transmission process, downlink transmission process, or slice authentication process, etc.
  • Specific processes may include, but are not limited to: registration process, de-registration process, etc.
  • connection management process may include, but is not limited to, a service request process, a paging process, etc.
  • the mobile management process may also include other processes, which will not be listed here.
  • the terminal device determines to delete the first mobility management parameter, which may be determined by the terminal device based on the information of the second access, or may be determined by the emergency on the second access. Determined after the business closes.
  • the terminal device may perform corresponding actions after determining not to delete the first mobility management parameter.
  • the first mobility management parameter is not deleted, or the first mobility management parameter is retained, or the first mobility management parameter is not processed, and so on.
  • the terminal device may perform corresponding actions after determining to delete the first mobility management parameter.
  • the first mobility management parameter is deleted.
  • the first mobility can not be deleted when the second access requires the first mobility management parameter.
  • mobility management parameters so that the terminal device can communicate using the first mobility management parameters on the second access, and avoid the situation where normal communication on the second access cannot be performed due to deletion of the first mobility management parameters of the first access. problem, reducing the impact on communications on the secondary access.
  • the terminal device determines whether to delete the first mobility management parameter, which has higher flexibility and better accuracy.
  • the core network device sends the first message to the terminal device through the first access.
  • the terminal device receives the first message through the first access.
  • S602 The terminal device determines whether to delete the first mobility management parameter of the first access according to the first message and the information of the second access.
  • the terminal device may determine according to the first message that the first mobility management parameter of the first access needs to be deleted. The terminal device determines whether to delete the first mobility management parameter of the first access according to the information of the second access.
  • the terminal device determines whether to delete the first mobility management parameter of the first access based on the information of the second access. Refer to the method described in Figure 5 for the terminal device to determine whether to delete the first access based on the information of the second access. The implementation method of the entered first mobility management parameter will not be described again here.
  • the behavior of the core network device after sending the first information may also determine whether to delete the first mobility management parameter of the first access based on the first information and the information of the second access.
  • the core network device determines whether to delete the first mobility management parameter of the first access based on the first information and the second access information. Refer to the method described in Figure 5. The core network device determines whether to delete the first mobility management parameter of the first access based on the first information and the second access information. The access information determines whether to delete the first mobility management parameter of the first access in an implementation manner, which will not be described again here.
  • the terminal equipment and/or the core network equipment can also perform one or more of the following four solutions: delete the second mobility management parameter and/or the third mobility management parameter; or stop the second mobility management parameter. Ongoing services on the access; or, start the first timer of the second access or release the N1 NAS signaling connection; or, stop the ongoing mobility management process on the second access.
  • the terminal device may perform corresponding actions after determining not to delete the first mobility management parameter.
  • the first mobility management parameter is not deleted, or the first mobility management parameter is retained, or the first mobility management parameter is not processed, and so on.
  • the terminal device may perform corresponding actions after determining to delete the first mobility management parameter.
  • the first mobility management parameter is deleted.
  • the first mobility can not be deleted when the second access requires the first mobility management parameter.
  • mobility management parameters so that the terminal device can communicate using the first mobility management parameters on the second access, and avoid the situation where normal communication on the second access cannot be performed due to deletion of the first mobility management parameters of the first access. problem, reducing the impact on communications on the secondary access.
  • the terminal device determines whether to delete the first mobility management parameter, which has higher flexibility and better accuracy.
  • the above describes the method for the terminal device to determine whether to delete the first mobility management parameter.
  • the method for the core network device to instruct the terminal device whether to delete the first mobility management parameter will be described below in conjunction with the above situations two and three.
  • FIG 7 it is a schematic flow chart of a communication method provided by an embodiment of the present application.
  • the core network device determines the first instruction information.
  • the terminal device can access the core network device through the first access point.
  • the core network device may determine whether to delete the first mobility management parameter of the first access based on the second indication information and the information of the second access.
  • the second indication information instructs the core network device to reject the terminal. The reason for the device's request.
  • the second indication information may be the first information in case 2 mentioned above.
  • the core network device determines whether to delete the first mobility management parameter of the first access based on the second instruction information and the second access information. Refer to the method described in Figure 5 for the core network device to determine whether to delete the first mobility management parameter of the first access based on the first information and the second access information. The information of the second access determines whether to delete the first mobility management parameter of the first access.
  • the core network device may determine whether to delete the first mobility management parameter of the first access based on the first message and the information of the second access.
  • the first message please refer to the relevant descriptions of the three situations mentioned above.
  • the core network device determines whether to delete the first mobility management parameter of the first access according to the first message and the second access information. Refer to the method described in Figure 6. The core network device determines whether to delete the first mobility management parameter of the first access according to the first message and the second access information. The access information determines whether to delete the implementation of the first mobility management parameter of the first access.
  • the core network device sends the first instruction information to the terminal device through the first access.
  • the terminal device receives the first indication information through the first access.
  • the first indication information indicates whether to delete the first mobility management parameter of the first access.
  • the first indication information may indicate whether to delete the first mobility management parameter of the first access in an explicit indication manner.
  • the first indication information indicates whether to delete the first mobility management parameter of the first access through different values of one or more bits.
  • the first indication information may use the first values of the one or more bits to indicate whether to delete the first mobility management parameter of the first access.
  • the first indication information may indicate deletion of the first mobility management parameter of the first access in an implicit indication manner. For example, if the first indication information carries a specific field, it indicates not to delete the first mobility management parameter of the first access; if it does not carry the specific field, it indicates that the first mobility management parameter of the first access is deleted.
  • the first indication information may indicate not to delete the first mobility management parameter of the first access in an implicit indication manner. For example, if the first indication information carries a specific field, it indicates that the first mobility management parameter of the first access is deleted. If it does not carry a specific field, it indicates that the first mobility management parameter of the first access is not deleted.
  • S703 The terminal device determines whether to delete the first mobility management parameter of the first access according to the first indication information.
  • the terminal device may determine whether to delete the first mobility management parameter of the first access based on the first indication information and the information of the second access.
  • the terminal device may determine whether to delete the first mobility management parameter of the first access based on the first indication information and the registration information of the second access.
  • the first instruction information indicates to delete the first mobility management parameter of the first access
  • the determination is made based on the service information on the second access.
  • Whether to delete the first mobility management parameter of the first access, and the service information on the second access is information on whether emergency services are ongoing on the second access.
  • the terminal device can also perform one or more of the following four solutions: delete the second mobility management parameter and/or the third mobility management parameter; or stop the ongoing processing on the second access. service; or, start the first timer of the second access or release the N1 NAS signaling connection; or, stop the ongoing mobility management process on the second access.
  • the terminal device may perform corresponding actions after determining not to delete the first mobility management parameter.
  • the first mobility management parameter is not deleted, or the first mobility management parameter is retained, or the first mobility management parameter is not processed, and so on.
  • the terminal device may perform corresponding actions after determining to delete the first mobility management parameter.
  • the first mobility management parameter is deleted.
  • the network device instructs the terminal device whether to delete the first mobility management parameter of the first access, which can reduce the complexity of the terminal device.
  • the first mobility management parameter may not be deleted when the second access requires the first mobility management parameter, So that the terminal equipment The first mobility management parameter can be used for communication on the second access, thereby avoiding the problem that normal communication on the second access cannot be caused by deleting the first mobility management parameter of the first access, and reducing the impact on the second access. impact on communication.
  • the embodiment of the present application provides a communication device.
  • the structure of the communication device can be shown in Figure 8 and includes a processing module 801.
  • the device may also include a communication module 802.
  • the communication device can be used to implement the method executed by the terminal device in the embodiment of Figure 4.
  • the device can be the terminal device itself, or it can be a chip or chipset in the terminal device or a chip for Execute part of the related method functionality.
  • the processing module 801 is used to determine that the first access of the terminal device is switched from the first PLMN to the second PLMN; and, if the status of the second access of the terminal device is on the first PLMN Register or have been registered on the first PLMN, and determine not to delete the first mobility management parameter of the first access; and if the status of the second access is not registered on the first PLMN, Determine to delete the first mobility management parameter; wherein the first access and the second access belong to different access types.
  • the processing module 801 is further configured to: before the terminal device determines that the first access is switched from the first PLMN to the second PLMN, determine that the first access has been switched. Register to the first PLMN.
  • the processing module 801 may also be configured to: after determining not to delete the first mobility management parameter, if the second access is handed over from the first PLMN to a third PLMN, determine to delete the first mobility management parameter. Mobility management parameters.
  • the first mobility management parameter includes at least one of the following: a key set identifier or a globally unique temporary user equipment identifier, where the key set identifier is used to identify NAS security context information.
  • the NAS security context information includes a security encryption algorithm, and the security encryption algorithm is a null encryption algorithm.
  • the communication device may be used to implement the method executed by the terminal device in the embodiment of FIG. 5 .
  • the device may be the terminal device itself, or may be a chip or chipset in the terminal device or a chip for Execute part of the related method functionality.
  • the communication module 802 is used to obtain the first information through the first access of the terminal device.
  • the processing module 801 is configured to determine whether to delete the first mobility management parameter of the first access according to the first information and the information of the second access of the terminal device.
  • the first information indicates the reason why the core network device rejects the request of the terminal device, and the first access and the second access belong to different access types.
  • the processing module 801 is specifically configured to: when determining whether to delete the first mobility management parameter based on the first information and the information of the second access of the terminal device: The first information and the registration information of the second access determine whether to delete the first mobility management parameter.
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the first information and the registration information of the second access, is specifically configured to: determine to delete the first mobility when the registration information of the second access satisfies one of the following conditions: Property management parameters: The second access is not registered with the PLMN, or the PLMN registered by the second access is different from the PLMN registered by the first access.
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the first information and the registration information of the second access, is specifically used to: determine not to delete the first mobility when the registration information of the second access satisfies the following conditions.
  • Property management parameters The PLMN registered for the second access is the same as the PLMN registered for the first access.
  • the first information is applicable to the second access;
  • the processing module 801 is specifically configured to: when determining whether to delete the first mobility management parameter according to the first information and the information of the second access of the terminal device:
  • the first information, the registration information of the second access and the service information on the second access determine whether to delete the first mobility management parameter.
  • the service information on the second access is whether there is an emergency service on the second access. information.
  • the processing module 801 performs processing according to the first information, the registration information of the second access, and the service information on the second access.
  • processing the first mobility management parameter it is specifically used to: determine to delete the first mobility management parameter when the registration information of the second access and the service information on the second access meet one of the following conditions: the second access is not registered. to the PLMN; or, the PLMN registered for the second access is different from the PLMN registered for the first access; or, the PLMN registered for the second access is the same as the PLMN registered for the first access, and there is no ongoing communication on the second access. Urgent business.
  • the processing module 801 when processing the first mobility management parameters according to the first information, the registration information of the second access, and the service information on the second access, is specifically used to: process the registration information of the second access and the second access information. It is determined not to delete the first mobility management parameter when the service information on the access meets the following conditions: the PLMN registered on the second access is the same as the PLMN registered on the first access, and there is an ongoing emergency service on the second access.
  • processing module 801 is also configured to determine to delete the first mobility management parameter after the emergency service ends.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, delete the second mobility management parameter.
  • the second mobility management parameter includes at least one of the following: the last mobility management parameter on the second access The accessed tracking area identifier, or the second accessed tracking area identifier list.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, stop the ongoing service on the second access.
  • the processing module 801 is also used to: if it is determined to delete the first mobility management parameter, start the first timer for the second access.
  • the first timer is used to trigger the terminal device to release the N1 NAS signaling connection; or, Release the N1 NAS signaling connection.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter and there is an ongoing mobility management process on the second access, stop the mobility management process.
  • the first mobility management parameter includes at least one of the following: a key set identifier or a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • the communication device can also be used to implement the method executed by the core network device in the embodiment of FIG. 5.
  • the device may be the core network equipment itself, or may be a chip or chipset in the core network equipment, or a part of the chip used to perform related method functions.
  • the communication module 802 is configured to send first information to the terminal device through the first access of the terminal device, where the first information indicates the reason why the core network device rejects the request of the terminal device.
  • the processing module 801 is configured to determine whether to delete the first mobility management parameter of the first access according to the first information and the information of the second access of the terminal device; wherein the first access and the second access belong to different accesses. Input type.
  • the first information is not applicable to the second access; the processing module 801, when determining whether to delete the first mobility management parameter according to the first information and the information of the second access, is specifically used to: according to the first information and the registration information of the second access determines whether to delete the first mobility management parameter.
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the first information and the registration information of the second access, may be specifically configured to: determine to delete the first mobility management parameter when the registration information of the second access satisfies one of the following conditions: Mobility management parameters: The second access is not registered with the PLMN.
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the first information and the registration information of the second access, may be specifically used to determine not to delete the first mobility when the registration information of the second access satisfies the following conditions:
  • Property management parameters The PLMN registered for the second access is the same as the PLMN registered for the first access.
  • the first information is applicable to the second access;
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the first information and the information of the second access, may be specifically configured to: based on the first information , the registration information of the second access and the service information on the second access determine whether to delete the first mobility management parameter, the service on the second access
  • the information is whether there is information about ongoing emergency services on the second access.
  • the processing module 801 when processing the first mobility management parameter according to the first information, the registration information of the second access, and the service information on the second access, may be specifically used to: process the registration information of the second access and the service information on the second access.
  • the first mobility management parameter is determined to be deleted when the service information on the second access meets one of the following conditions: the second access is not registered with the PLMN; or the PLMN registered by the second access is the same as the PLMN registered by the first access. There is no ongoing emergency service on the second access.
  • the processing module 801 when processing the first mobility management parameter according to the first information, the registration information of the second access, and the service information on the second access, may be specifically used to: process the registration information of the second access and the service information on the second access. It is determined not to delete the first mobility management parameter when the service information on the second access meets the following conditions: the PLMN registered on the second access is the same as the PLMN registered on the first access, and there is an ongoing emergency service on the second access.
  • processing module 801 is also configured to determine to delete the first mobility management parameter after the emergency service ends.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, delete the second mobility management parameter.
  • the second mobility management parameter includes at least one of the following: the last mobility management parameter on the second access The accessed tracking area identifier, or the second accessed tracking area identifier list.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, stop the ongoing service on the second access.
  • the processing module 801 is also used to: if it is determined to delete the first mobility management parameter, release the N1 NAS signaling connection.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, and if there is an ongoing mobility management process on the second access, stop the mobility management process.
  • the first mobility management parameter includes at least one of the following: a key set identifier or a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • the communication device may be used to implement the method executed by the terminal device in the embodiment of FIG. 7 .
  • the device may be the terminal device itself, or may be a chip or chipset in the terminal device or a chip for Execute part of the related method functionality.
  • the communication module 802 is used to receive the first indication information through the first access of the terminal device, and the first indication information indicates whether to delete the first mobility management parameter of the first access; the processing module 801 is used to according to the first access An indication information determines whether to delete the first mobility management parameter of the first access, and the first access and the second access belong to different access types.
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the first indication information, may be specifically configured to: determine whether to delete the first mobility management parameter based on the first indication information and the second access information.
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the first indication information and the information of the second access, may be specifically configured to: determine whether to delete the first mobility management parameter based on the first indication information and the registration information of the second access. - Mobility management parameters.
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the first indication information and the registration information of the second access, may be specifically configured to: if the first indication information indicates deletion of the first mobility management parameter, in the The first mobility management parameter is determined to be deleted when the registration information of the second access meets one of the following conditions: the second access is not registered with the PLMN, or the PLMN registered by the second access is different from the PLMN registered by the first access.
  • the processing module 801 when determining whether to delete the first mobility management parameter according to the first indication information and the registration information of the second access, may be specifically used: if the first indication information indicates to delete the first mobility management parameter, and the The PLMN registered for the second access is the same as the PLMN registered for the first access. Determine whether to delete it based on the service information on the second access.
  • the service information on the second access is information on whether emergency services are ongoing on the second access.
  • the processing module 801 when determining whether to delete the first mobility management parameter based on the service information on the second access, may be specifically used to: determine not to delete the first mobility management parameter if there is an ongoing emergency service on the second access. parameter; or, if there is no ongoing emergency service on the second access, determine to delete the first mobility management parameter.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, determine to delete the first mobility management parameter after the emergency service ends.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, delete the second mobility management parameter.
  • the second mobility management parameter includes at least one of the following: the last mobility management parameter on the second access The accessed tracking area identifier, or the second accessed tracking area identifier list.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, stop the ongoing service on the second access.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, start a first timer for the second access, where the first timer is used to trigger the terminal device to release the N1 NAS signaling connection; Or, release the N1NAS signaling connection.
  • the processing module 801 is also configured to: if it is determined to delete the first mobility management parameter, and if there is an ongoing mobility management process on the second access, stop the mobility management process.
  • the first mobility management parameter includes at least one of the following: a key set identifier or a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • the communication device can also be used to implement the method executed by the core network device in the embodiment of FIG. 7.
  • the device may be the core network equipment itself, or may be a chip or chipset in the core network equipment, or a part of the chip used to perform related method functions.
  • the processing module 801 is used to determine the first indication information.
  • the communication module 802 is configured to send first indication information to the terminal device through the first access of the terminal device; the first indication information indicates whether to delete the first mobility management parameter of the first access, the first access and the second access. Access belongs to different access types.
  • the processing module 801 may be specifically configured to: determine the first indication information according to the second indication information and the second access information, and the second indication information indicates the reason why the core network device rejects the request of the terminal device.
  • the second indication information is not applicable to the second access; the processing module 801 may be specifically configured to determine the first indication information according to the second indication information and the registration information of the second access.
  • the processing module 801 may be specifically configured to: the first indication information indicates deletion of the first mobility management parameter when the registration information of the second access satisfies one of the following conditions: the second access is not registered with the PLMN; or the core network device is in The first indication information indicates not to delete the first mobility management parameter when the registration information of the second access meets the following conditions: the second access has been registered or is registering with the PLMN.
  • the second indication information is applicable to the second access; the processing module 801 may be specifically configured to: determine the first indication information according to the second indication information, the registration information of the second access, and the service information on the second access, and the second indication information.
  • the service information on the access is information on whether emergency services are being performed on the second access.
  • the processing module 801 may be specifically configured to: when the registration information of the second access and the service information on the second access meet one of the following conditions, the first instruction information instructs to delete the first mobility management parameter: the second access is not registered. to the PLMN; or, the second access has been registered to or is being registered to the PLMN, and there is no ongoing emergency service on the second access.
  • the processing module 801 can be specifically used to: when the registration information of the second access and the service information on the second access are satisfied.
  • the first indication information indicates not to delete the first mobility management parameter when the following conditions are met: the second access has been registered or is being registered to the PLMN, and there is an ongoing emergency service on the second access.
  • the first mobility management parameter includes at least one of the following: a key set identifier and a globally unique temporary user equipment identifier.
  • the key set identifier is used to identify the NAS security context information.
  • the communication device can also be used to implement the method executed by the communication device (such as a terminal device or a core network device) in the embodiment of Figure 6.
  • the device can be the communication device itself, or it can be a chip or chipset in the communication device or The part of the chip used to perform related method functions.
  • each functional module in each embodiment of the present application may be integrated into one processing unit. In the device, it can exist physically alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or software function modules. It can be understood that for the functions or implementation of each module in the embodiments of this application, further reference can be made to the relevant descriptions of the method embodiments.
  • the communication device may be as shown in Figure 9.
  • the device may be a communication device or a chip in the communication device.
  • the communication device may be a terminal device in the above embodiment or may be a terminal device in the above embodiment.
  • the device includes a processor 901 and a communication interface 902, and may also include a memory 903.
  • the processing module 801 may be a processor 901.
  • the communication module 802 may be a communication interface 902.
  • the processor 901 may be a CPU, a digital processing unit, or the like.
  • the communication interface 902 may be a transceiver, an interface circuit such as a transceiver circuit, or a transceiver chip, or the like.
  • the device also includes: a memory 903 for storing programs executed by the processor 901.
  • the memory 903 can be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory (volatile memory), such as a random access memory (random access memory). -access memory, RAM).
  • Memory 903 is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the processor 901 is used to execute the program code stored in the memory 903, and is specifically used to execute the actions of the above-mentioned processing module 801, which will not be described again in this application.
  • the communication interface 902 is specifically used to perform the above-mentioned actions of the communication module 802, which will not be described again in this application.
  • the embodiment of the present application does not limit the specific connection medium between the communication interface 902, the processor 901 and the memory 903.
  • the memory 903, the processor 901 and the communication interface 902 are connected through a bus 904 in Figure 9.
  • the bus is represented by a thick line in Figure 9.
  • the connection methods between other components are only schematically explained. , is not limited.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • Embodiments of the present application also provide a computer-readable storage medium for storing computer software instructions required to execute the above-mentioned processor, which includes programs required to execute the above-mentioned processor.
  • Embodiments of the present application also provide a communication system, including a communication device for realizing the functions of the terminal equipment in the embodiment of FIG. 4 and a communication device for realizing the functions of the network equipment in the embodiment of FIG. 4 .
  • Embodiments of the present application also provide a communication system, including a communication device for realizing the functions of the terminal equipment in the embodiment of FIG. 5 and a communication device for realizing the functions of the network equipment in the embodiment of FIG. 5 .
  • Embodiments of the present application also provide a communication system, including a communication device for realizing the functions of the terminal equipment in the embodiment of FIG. 6 and a communication device for realizing the functions of the network equipment in the embodiment of FIG. 6 .
  • An embodiment of the present application also provides a communication system, including a communication system for realizing the functions of the terminal device in the embodiment of Figure 7 A communication device and a communication device used to implement the functions of the network equipment in the embodiment of FIG. 7 .
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种通信方法及装置,用于解决终端设备的部分接入对公共参数的操作导致终端设备在其他接入上无法正常通信的问题。该方法包括:终端设备在该终端设备的第一接入从第一PLMN切换到第二PLMN的情况下,若该终端设备的第二接入的状态为正在第一PLMN上进行注册或已注册在第一PLMN上,确定不删除第一接入的第一移动性管理参数。若该终端设备的第二接入的状态为未注册在第一PLMN上,确定删除第一接入的第一移动性管理参数。其中,第一接入和第二接入属于不同的接入类型。通过在删除第一移动性管理参数时考虑第二接入的注册情况,可以降低对第二接入上的通信的影响。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年05月05日提交中国专利局、申请号为202210479701.2、申请名称为“一种通信方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,尤其涉及一种通信方法及装置。
背景技术
随着通信的发展,目前支持终端设备通过多种类型的接入与核心网通信,例如,终端设备可以通过第三代合作伙伴计划(3rd generation partnership project,3GPP)无线接入技术的接入以及非3GPP接入技术的接入与核心网通信。
当终端设备的多个接入注册到同一个公共陆地移动网络(public land mobile network,PLMN)时,终端设备的多个接入的通信可能共用一些参数。例如,终端设备的多个接入共用非接入层(non access stratum,NAS)完整性保护算法、或者NAS加密算法、以及全球唯一临时用户设备标识(globally unique temporary UE identity,GUTI)等。
由于终端设备的多个接入共用一些参数,若终端设备的一个接入对这些参数进行操作如删除、修改等,会对其他接入的通信产生影响。例如,终端设备的一个接入对NAS安全上下文信息进行删除,将导致其他的接入的上行信令无法进行完整性保护和加密,下行信令因完整性检查失败而无法正常接收等。又例如,终端设备的一个接入对GUTI进行删除,导致其他的接入的一些消息中无法携带GUTI信息,从而导致PLMN无法识别终端设备的身份、终端设备也无法接收PLMN的寻呼等。
因此,如何避免终端设备的部分接入对公共参数的操作对其他接入产生影响是一个亟待解决的问题。
发明内容
本申请提供一种通信方法及装置,用于解决终端设备的部分接入对公共参数的操作导致终端设备在其他接入上无法正常通信的问题。
第一方面,本申请提供一种通信方法,该方法的执行主体可以是终端设备,也可以是芯片或电路或用于实现终端设备的功能的其他部件。以终端设备为例,该方法包括:终端设备在该终端设备的第一接入从第一PLMN切换到第二PLMN的情况下,若该终端设备的第二接入的状态为正在第一PLMN上进行注册或已注册在第一PLMN上,确定不删除第一接入的第一移动性管理参数。若该终端设备的第二接入的状态为未注册在第一PLMN上,确定删除第一接入的第一移动性管理参数。其中,第一接入和第二接入属于不同的接入类型。
通过第二接入是否在第一PLMN(即第一接入注册的PLMN)上进行注册,可以确定终端设备在第二接入上的通信是否需要使用第一移动性管理参数。本申请实施例中通过在 终端设备的第二接入未注册在第一PLMN的情况下,删除第一接入的第一移动性管理参数,可以在不影响终端设备在第二接入上的通信的前提下,降低终端设备维护信息的成本,还可以避免终端设备在第一接入上使用无效的参数(即第一移动性管理参数)进行通信,从而可以提升终端设备在第一接入上的通信性能。
在终端设备的第二接入注册到第一PLMN或者正在第一PLMN上进行注册的情况下不删除第一移动性管理参数,可以保证终端设备在第二接入上正常通信。
一种可能的设计中,若第一接入注册的PLMN和第二接入注册的PLMN相同,第一接入和第二接入共用第一移动性管理参数。
一种可能的设计中,在终端设备的第一接入从第一PLMN切换到第二PLMN之前,方法还包括:终端设备确定第一接入已注册到第一PLMN。
一种可能的设计中,在确定不删除第一移动性管理参数之后,方法还包括:若第二接入从第一PLMN切换到第三PLMN,终端设备确定删除第一移动性管理参数。
当第二接入从第一PLMN切换到其他PLMN后,终端设备在第二接入上的通信不使用第一移动性管理参数,因此当第二接入从第一PLMN切换到其他PLMN后及时删除第一移动性管理参数,一方面可以降低终端设备维护参数的成本,还可以避免终端设备在第一接入和/或第二接入上使用无效的参数(即第一移动性管理参数)进行通信。
一种可能的设计中,第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
一种可能的设计中,NAS安全上下文信息包括安全加密算法,安全加密算法为空加密算法。
由于安全加密算法为空加密算法时NAS安全上下文信息的安全性较低,上述方式通过在密钥集标识所标识的NAS安全上下文信息中安全加密算法为空加密算法时删除第一移动性管理参数,有利于终端设备的通信安全。
第二方面,本申请提供一种通信方法,该方法的执行主体可以是终端设备,也可以是芯片或电路或用于实现终端设备的功能的其他部件。以终端设备为例,该方法包括:终端设备通过该终端设备的第一接入获取第一信息,并根据第一信息以及该终端设备的第二接入的信息确定是否删除第一接入的第一移动性管理参数。其中,第一信息指示核心网设备拒绝该终端设备的请求的原因,第一接入和第二接入属于不同的接入类型。
本申请实施例中,在删除第一接入的第一移动性管理参数时通过考虑第二接入的信息,可以在第二接入需要第一移动性管理参数的情况下不删除第一移动性管理参数,从而使得终端设备在第二接入上可以使用第一移动性管理参数进行通信,避免出现因在不合适场景下删除第一接入的第一移动性管理参数(例如在第二接入需要第一移动性管理参数的情况下)导致第二接入上无法正常通信的问题,降低对第二接入上的通信的影响。
并且,通过终端设备判断是否删除第一接入的第一移动性管理参数,可以提供处理第一移动性管理参数的灵活性的,准确性也比较好。
一种可能的设计中,若第一接入注册的PLMN和第二接入注册的PLMN相同,第一接入和第二接入共用第一移动性管理参数。
一种可能的设计中,第一信息不适用于第二接入;终端设备根据第一信息以及终端设备的第二接入的信息确定是否删除第一移动性管理参数,包括:终端设备根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数。
通过第二接入的注册信息可以确定终端设备在第二接入上的通信是否需要使用第一移动性管理参数。从而可以避免在终端设备在第二接入上使用第一移动性管理参数进行通信的情况下将第一移动性管理参数删除,进而可以保证终端设备在第二接入上正常通信。
一种可能的设计中,终端设备根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数,包括:终端设备在第二接入的注册信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN、或者第二接入注册的PLMN与第一接入注册的PLMN不同。
若第二接入没有在第一接入注册的PLMN上进行注册,可以确定终端设备在第二接入上的通信不需要使用第一移动性管理参数。上述方式通过在终端设备在第二接入上的通信不需要使用第一移动性管理参数的情况下删除第一移动性管理参数,可以在不影响终端设备在第二接入上的通信的前提下,降低终端设备维护信息的成本,还可以避免终端设备在第一接入上使用无效的参数(即第一移动性管理参数)进行通信,从而可以提升终端设备在第一接入上的通信性能。
一种可能的设计中,终端设备根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数,包括:终端设备在第二接入的注册信息满足如下条件时确定不删除第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同。
若第二接入在第一接入注册的PLMN上进行注册,可以确定终端设备在第二接入上的通信需要使用第一移动性管理参数。上述方式通过终端设备在第二接入上的通信需要使用第一移动性管理参数的情况下不删除第一移动性管理参数,可以保证终端设备在第二接入上正常通信。
一种可能的设计中,第一信息适用于第二接入;终端设备根据第一信息以及终端设备的第二接入的信息确定是否删除第一移动性管理参数,包括:终端设备根据第一信息、第二接入的注册信息以及第二接入上的业务信息确定是否删除第一移动性管理参数,第二接入上的业务信息为第二接入上是否存在正在进行紧急业务的信息。
通过上述设计,可以降低在第二接入上有紧急业务时删除第一移动性管理参数而导致的通信质量下降,从而可以保证第二接入上正常进行的紧急业务正常进行,提升用户体验。
一种可能的设计中,紧急业务为携带第一标识的协议数据单元(protocol data unit,PDU)会话对应的业务,该第一标识用于标识该PDU会话上进行的业务为紧急业务。
一种可能的设计中,终端设备根据第一信息、第二接入的注册信息以及第二接入上的业务信息处理第一移动性管理参数,包括:终端设备在第二接入的注册信息以及第二接入上的业务信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN;或者,第二接入注册的PLMN与第一接入注册的PLMN不同;或者,第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上没有正在进行的紧急业务。
通过上述设计,可以在不影响终端设备在第二接入上的通信或者不影响第二接入上正在进行的紧急业务的前提下,降低终端设备维护信息的成本,还可以避免终端设备在第一接入上使用无效的参数(即第一移动性管理参数)进行通信,从而可以提升终端设备在第一接入上的通信性能。
一种可能的设计中,终端设备根据第一信息、第二接入的注册信息以及第二接入上的业务信息处理第一移动性管理参数,包括:终端设备在第二接入的注册信息以及第二接入上的业务信息满足如下条件时确定不删除第一移动性管理参数:第二接入注册的PLMN与 第一接入注册的PLMN相同,第二接入上存在正在进行的紧急业务。
通过上述可以保证第二接入上的紧急业务正常进行,从而可以提升用户体验。
一种可能的设计中,终端设备在紧急业务结束之后确定删除第一移动性管理参数。通过上述设计,可以降低终端设备维护信息的成本,还可以避免终端设备在第一接入上使用无效的参数(即第一移动性管理参数)进行通信,从而可以提升终端设备在第一接入上的通信性能。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:终端设备删除第二移动性管理参数,第二移动性管理参数包括如下至少一项:在第二接入上的最后访问的跟踪区标识、或者第二接入的跟踪区标识列表。通过上述设计,可以降低终端设备维护信息的成本。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:终端设备停止第二接入上正在进行的业务。通过上述设计可以节省通信资源。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:终端设备启动第二接入的第一定时器,第一定时器用于触发终端设备释放N1 NAS信令连接;或者,释放N1 NAS信令连接。通过上述设计可以节省N1 NAS信令连接资源。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:若第二接入上存在正在进行移动管理流程,终端设备停止移动管理流程。通过上述设计可以节省通信资源。
一种可能的设计中,第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
第三方面,本申请提供一种通信方法,该方法的执行主体可以是核心网设备,也可以是芯片或电路或用于实现核心网设备的功能的其他部件。以核心网设备为例,该方法包括:核心网设备通过终端设备的第一接入向终端设备发送第一信息,第一信息指示核心网设备拒绝终端设备的请求的原因;核心网设备根据第一信息以及终端设备的第二接入的信息确定是否删除第一接入的第一移动性管理参数;其中,第一接入和第二接入属于不同的接入类型。
本申请实施例中,在删除第一接入的第一移动性管理参数时通过考虑第二接入的信息,可以在第二接入需要第一移动性管理参数的情况下不删除第一移动性管理参数,从而使得终端设备在第二接入上可以使用第一移动性管理参数进行通信,避免出现因删除第一接入的第一移动性管理参数导致第二接入上无法正常通信的问题,降低对第二接入上的通信的影响。
一种可能的设计中,若第一接入注册的PLMN和第二接入注册的PLMN相同,第一接入和第二接入共用第一移动性管理参数。
一种可能的设计中,第一信息不适用于第二接入;核心网设备根据第一信息以及第二接入的信息确定是否删除第一移动性管理参数,包括:核心网设备根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数。
通过第二接入的注册信息可以确定核心网设备在第二接入上的通信是否需要使用第一移动性管理参数。从而可以避免在终端设备在第二接入上使用第一移动性管理参数进行通信的情况下将第一移动性管理参数删除,进而可以保证终端设备在第二接入上正常通信。
一种可能的设计中,核心网设备根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数,包括:核心网设备在第二接入的注册信息满足如下条件之一时确定 删除第一移动性管理参数:第二接入未注册到PLMN。
若第二接入没有在第一接入注册的PLMN上进行注册,可以确定终端设备在第二接入上的通信不需要使用第一移动性管理参数。上述方式通过在终端设备在第二接入上的通信不需要使用第一移动性管理参数的情况下删除第一移动性管理参数,可以在不影响终端设备在第二接入上的通信的前提下,降低核心网设备维护信息的成本。
一种可能的设计中,核心网设备根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数,包括:核心网设备在第二接入的注册信息满足如下条件时确定不删除第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同。
若第二接入在第一接入注册的PLMN上进行注册,可以确定终端设备在第二接入上的通信需要使用第一移动性管理参数。上述方式通过在终端设备在第二接入上的通信需要使用第一移动性管理参数的情况下不删除第一移动性管理参数,可以保证终端设备在第二接入上正常通信。
一种可能的设计中,第一信息适用于第二接入;核心网设备根据第一信息以及第二接入的信息确定是否删除第一移动性管理参数,包括:核心网设备根据第一信息、第二接入的注册信息以及第二接入上的业务信息确定是否删除第一移动性管理参数,第二接入上的业务信息为第二接入上是否存在正在进行紧急业务的信息。
通过上述设计,可以降低对第二接入上的业务的影响,提升用户体验。
一种可能的设计中,核心网设备根据第一信息、第二接入的注册信息以及第二接入上的业务信息处理第一移动性管理参数,包括:核心网设备在第二接入的注册信息以及第二接入上的业务信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN;或者,第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上没有正在进行的紧急业务。
通过上述设计,可以在不影响终端设备在第二接入上的通信或者不影响第二接入上正在进行的紧急业务的前提下,降低核心网设备维护信息的成本。
一种可能的设计中,核心网设备根据第一信息、第二接入的注册信息以及第二接入上的业务信息处理第一移动性管理参数,包括:核心网设备在第二接入的注册信息以及第二接入上的业务信息满足如下条件时确定不删除第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上存在正在进行紧急业务。
通过上述可以保证第二接入上的紧急业务正常进行,从而可以提升用户体验。
一种可能的设计中,核心网设备在紧急业务结束之后确定删除第一移动性管理参数。通过上述设计,可以降低核心网设备维护信息的成本。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:核心网设备删除第二移动性管理参数,第二移动性管理参数包括如下至少一项:在第二接入上的最后访问的跟踪区标识、或者第二接入的跟踪区标识列表。通过上述设计,可以降低核心网设备维护信息的成本。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:核心网设备停止第二接入上正在进行的业务。通过上述设计可以节省通信资源。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:核心网设备释放N1 NAS信令连接。通过上述设计可以节省N1 NAS信令连接资源。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:若第二接入上存 在正在进行移动管理流程,核心网设备停止移动管理流程。通过上述设计可以节省通信资源。
一种可能的设计中,第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
第四方面,本申请提供一种通信方法,该方法的执行主体可以是终端设备,也可以是芯片或电路或用于实现终端设备的功能的其他部件。以终端设备为例,该方法包括:终端设备通过该终端设备的第一接入接收第一指示信息,第一指示信息指示是否删除第一接入的第一移动性管理参数;根据第一指示信息确定是否删除第一接入的第一移动性管理参数,第一接入和第二接入属于不同的接入类型。
本申请实施例中通过网络设备指示终端设备是否删除第一移动性管理参数,可以降低终端设备的复杂度。
一种可能的设计中,若第一接入注册的PLMN和第二接入注册的PLMN相同,第一接入和第二接入共用第一移动性管理参数。
一种可能的设计中,终端设备根据第一指示信息确定是否删除第一移动性管理参数,包括:终端设备根据第一指示信息以及第二接入的信息确定是否删除第一移动性管理参数。
上述方式中,在删除第一接入的第一移动性管理参数时通过考虑第二接入的信息,可以在第二接入需要第一移动性管理参数的情况下不删除第一移动性管理参数,从而使得终端设备在第二接入上可以使用第一移动性管理参数进行通信,避免出现因删除第一接入的第一移动性管理参数导致第二接入上无法正常通信的问题,降低对第二接入上的通信的影响。
一种可能的设计中,终端设备根据第一指示信息以及第二接入的信息确定是否删除第一移动性管理参数,包括:终端设备根据第一指示信息以及第二接入的注册信息确定是否删除第一移动性管理参数。
通过第二接入的注册信息可以确定终端设备在第二接入上的通信是否需要使用第一移动性管理参数。从而可以避免在终端设备在第二接入上使用第一移动性管理参数进行通信的情况下将第一移动性管理参数删除,进而可以保证终端设备在第二接入上正常通信。
一种可能的设计中,终端设备根据第一指示信息以及第二接入的注册信息确定是否删除第一移动性管理参数,包括:若第一指示信息指示删除第一移动性管理参数,终端设备在第二接入的注册信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN、或者第二接入注册的PLMN与第一接入注册的PLMN不同。
若第二接入没有在第一接入注册的PLMN上进行注册,可以确定终端设备在第二接入上的通信不需要使用第一移动性管理参数。上述方式通过在终端设备在第二接入上的通信不需要使用第一移动性管理参数的情况下删除第一移动性管理参数,可以在不影响终端设备在第二接入上的通信的前提下,降低终端设备维护信息的成本,还可以避免终端设备在第一接入上使用无效的参数(即第一移动性管理参数)进行通信,从而可以提升终端设备在第一接入上的通信性能。
一种可能的设计中,终端设备根据第一指示信息以及第二接入的注册信息确定是否删除第一移动性管理参数,包括:若第一指示信息指示删除第一移动性管理参数,且第二接入注册的PLMN与第一接入注册的PLMN相同,终端设备根据第二接入上的业务信息确定是否删除第一移动性管理参数,第二接入上的业务信息为第二接入上是否正在进行紧急 业务的信息。
通过上述设计,可以降低对第二接入上的业务的影响,提升用户体验。
一种可能的设计中,终端设备根据第二接入上的业务信息确定是否删除第一移动性管理参数,包括:若第二接入上存在正在进行紧急业务,终端设备确定不删除第一移动性管理参数;或者,若第二接入上没有正在进行的紧急业务,终端设备确定删除第一移动性管理参数。
通过上述设计,可以保证第二接入上正常进行的紧急业务正常进行,提升用户体验。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:终端设备在紧急业务结束后确定删除第一移动性管理参数。通过上述设计,可以降低终端设备维护信息的成本,还可以避免终端设备在第一接入上使用无效的参数(即第一移动性管理参数)进行通信,从而可以提升终端设备在第一接入上的通信性能。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:终端设备删除第二移动性管理参数,第二移动性管理参数包括如下至少一项:在第二接入上的最后访问的跟踪区标识、或者第二接入的跟踪区标识列表。通过上述设计,可以降低终端设备维护信息的成本。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:终端设备停止第二接入上正在进行的业务。通过上述设计可以节省通信资源。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:终端设备启动第二接入的第一定时器,其中,第一定时器用于触发终端设备释放N1 NAS信令连接;或者,释放N1 NAS信令连接。通过上述设计可以节省N1 NAS信令连接资源。
一种可能的设计中,若确定删除第一移动性管理参数,方法还包括:若第二接入上存在正在进行移动管理流程,终端设备停止移动管理流程。通过上述设计可以节省通信资源。
一种可能的设计中,第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
第五方面,本申请提供一种通信方法,该方法的执行主体可以是核心网设备,也可以是芯片或电路或用于实现核心网设备的功能的其他部件。以核心网设备为例,该方法包括:核心网设备确定第一指示信息,并通过终端设备的第一接入向终端设备发送第一指示信息;第一指示信息指示是否删除第一接入的第一移动性管理参数,第一接入和第二接入属于不同的接入类型。
本申请实施例中通过网络设备指示终端设备是否删除第一移动性管理参数,可以降低终端设备的复杂度。
一种可能的设计中,若第一接入注册的PLMN和第二接入注册的PLMN相同,第一接入和第二接入共用第一移动性管理参数。
一种可能的设计中,核心网设备确定第一指示信息,包括:核心网设备根据第二指示信息以及第二接入的信息确定第一指示信息,第二指示信息指示核心网设备拒绝终端设备的请求的原因。
本申请实施例中,在删除第一接入的第一移动性管理参数时通过考虑第二接入的信息,可以在第二接入需要第一移动性管理参数的情况下不删除第一移动性管理参数,从而使得终端设备在第二接入上可以使用第一移动性管理参数进行通信,避免出现因删除第一接入的第一移动性管理参数导致第二接入上无法正常通信的问题,降低对第二接入上的通信的 影响。
一种可能的设计中,第二指示信息不适用于第二接入;核心网设备根据第二指示信息以及第二接入的信息确定第一指示信息,包括:核心网设备根据第二指示信息以及第二接入的注册信息确定第一指示信息。
通过第二接入的注册信息可以确定核心网设备在第二接入上的通信是否需要使用第一移动性管理参数。从而可以避免在终端设备在第二接入上使用第一移动性管理参数进行通信的情况下将第一移动性管理参数删除,进而可以保证终端设备在第二接入上正常通信。
一种可能的设计中,核心网设备根据第二指示信息以及第二接入的注册信息确定第一指示信息,包括:核心网设备在第二接入的注册信息满足如下条件之一时第一指示信息指示删除第一移动性管理参数:第二接入未注册到PLMN;或者,核心网设备在第二接入的注册信息满足如下条件时第一指示信息指示不删除第一移动性管理参数:第二接入已注册到或者正在注册到PLMN。
若第二接入没有在第一接入注册的PLMN上进行注册,可以确定终端设备在第二接入上的通信不需要使用第一移动性管理参数。上述方式通过在终端设备在第二接入上的通信不需要使用第一移动性管理参数的情况下删除第一移动性管理参数,可以在不影响终端设备在第二接入上的通信的前提下,降低核心网设备维护信息的成本。
若第二接入在第一接入注册的PLMN上进行注册,可以确定终端设备在第二接入上的通信需要使用第一移动性管理参数。上述方式通过在终端设备在第二接入上的通信需要使用第一移动性管理参数的情况下不删除第一移动性管理参数,可以保证终端设备在第二接入上正常通信。
一种可能的设计中,第二指示信息适用于第二接入;核心网设备根据第二指示信息以及第二接入的信息确定第一指示信息,包括:核心网设备根据第二指示信息、第二接入的注册信息以及第二接入上的业务信息确定第一指示信息,第二接入上的业务信息为第二接入上是否正在进行紧急业务的信息。
通过上述设计,可以降低对第二接入上的业务的影响,提升用户体验。
一种可能的设计中,核心网设备根据第二指示信息、第二接入的注册信息以及第二接入上的业务信息确定第一指示信息,包括:核心网设备在第二接入的注册信息以及第二接入上的业务信息满足如下条件之一时第一指示信息指示删除第一移动性管理参数:第二接入未注册到PLMN;或者,第二接入已注册到或者正在注册到PLMN,第二接入上没有正在进行的紧急业务。
通过上述设计,可以在不影响终端设备在第二接入上的通信或者不影响第二接入上正在进行的紧急业务的前提下,降低核心网设备维护信息的成本。
一种可能的设计中,核心网设备根据第二指示信息、第二接入的注册信息以及第二接入上的业务信息确定第一指示信息,包括:核心网设备在第二接入的注册信息以及第二接入上的业务信息满足如下条件时第一指示信息指示不删除第一移动性管理参数:第二接入已注册到或者正在注册到PLMN,第二接入上存在正在进行紧急业务。
通过上述可以保证第二接入上的紧急业务正常进行,从而可以提升用户体验。
一种可能的设计中,第一移动性管理参数包括如下至少一项:密钥集标识、全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
第六方面,本申请还提供一种通信装置,该通信装置具有实现上述第一方面或第二方 面或第四方面提供的任一方法。该通信装置可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的设计中,该通信装置包括:处理器,该处理器被配置为支持该通信装置执行以上所示方法中终端设备的相应功能。该通信装置还可以包括存储器,该存储可以与处理器耦合,其保存该通信装置必要的程序指令和数据。可选地,该通信装置还包括接口电路,该接口电路用于支持该通信装置与其他设备之间的通信。
在一种可能的设计中,该通信装置包括相应的功能模块,分别用于实现以上方法中的步骤。功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中,通信装置的结构中包括处理模块和通信模块,这些模块可以执行上述方法示例中相应功能,具体参见第一方面或第二方面或第四方面提供的方法中的描述,此处不做赘述。
第七方面,本申请还提供一种通信装置,该通信装置具有实现上述第三方面或第五方面提供的任一方法。该通信装置可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的设计中,该通信装置包括:处理器,该处理器被配置为支持该通信装置执行以上所示方法中网络设备的相应功能。该通信装置还可以包括存储器,该存储可以与处理器耦合,其保存该通信装置必要的程序指令和数据。可选地,该通信装置还包括接口电路,该接口电路用于支持该通信装置与其他设备之间的通信。
在一种可能的设计中,该通信装置包括相应的功能模块,分别用于实现以上方法中的步骤。功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中,通信装置的结构中包括处理模块和通信模块,这些模块可以执行上述方法示例中相应功能,具体参见第三方面或第五方面提供的方法中的描述,此处不做赘述。
第八方面,提供了一种通信装置,包括处理器和接口电路,接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置,该处理器通过逻辑电路或执行代码指令用于实现前述第一方面或第二方面或第四方面以及任意可能的设计中的方法。
第九方面,提供了一种通信装置,包括处理器和接口电路,接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置,该处理器通过逻辑电路或执行代码指令用于实现前述第三方面或第五方面以及任意可能的设计中的方法。
第十方面,提供了一种计算机可读存储介质,该计算机可读存储介质中存储有计算机程序或指令,当该计算机程序或指令被处理器执行时,实现前述第一方面至第五方面中任一方面以及任意可能的设计中的方法。
第十一方面,提供了一种存储有指令的计算机程序产品,当该指令被处理器运行时,实现前述第一方面至第五方面中任一方面以及任意可能的设计中的方法。
第十二方面,提供一种芯片系统,该芯片系统包括处理器,还可以包括存储器,用于实现前述第一方面至第五方面中任一方面以及任意可能的设计的方法。该芯片系统可以由 芯片构成,也可以包含芯片和其他分立器件。
第十三方面,提供一种通信系统,所述系统包括第一方面所述的装置(如终端设备),还可以包括核心网设备。
第十四方面,提供一种通信系统,所述系统包括第二方面所述的装置(如终端设备)和第三方面所述的装置(如核心网设备)。
第十五方面,提供一种通信系统,所述系统包括第四方面所述的装置(如终端设备)和第五方面所述的装置(如核心网设备)。
附图说明
图1为本申请实施例的一种基于服务化架构的5G网络架构示意图;
图2为本申请实施例的一种非可信的non-3GPP接入网架构示意图;
图3为本申请实施例的一种可信的non-3GPP接入网架构示意图;
图4为本申请实施例的一种通信方法的流程示意图;
图5为本申请实施例的一种通信方法的流程示意图;
图6为本申请实施例的一种通信方法的流程示意图;
图7为本申请实施例的一种通信方法的流程示意图;
图8为本申请实施例的一种通信装置的结构示意图;
图9为本申请实施例的一种通信装置的结构示意图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施例作进一步地详细描述。
下面介绍本申请所提供的方法应用的网络系统的架构。
如图1所示,为基于服务化架构的5G网络架构示意图。图1所示的5G网络架构中可包括三部分,分别是终端设备部分、数据网络(data network,DN)和运营商网络部分。下面对其中的部分网元的功能进行简单介绍说明。
其中,运营商网络可包括以下网元中的一个或多个:鉴权服务器功能(authentication server function,AUSF)网元、网络开放功能(network exposure function,NEF)网元、策略控制功能(policy control function,PCF)网元、统一数据管理(unified data management,UDM)网元、统一数据库(unified data repository,UDR)、网络存储功能(network repository function,NRF)网元、接入与移动性管理功能(access and mobility management function,AMF)网元、会话管理功能(session management function,SMF)网元、接入网以及用户面功能(user plane function,UPF)网元等。上述运营商网络中,除无线接入网部分之外的部分可以称为核心网部分。在一种可能的实现方法中,运营商网络中还包括应用功能(Application Function,AF)网元。或者,AF网元也可能不属于运营商网络,而是属于第三方。
终端设备(terminal device),是一种具有无线收发功能的设备,可以部署在陆地上,包括室内或室外、手持或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。终端设备可以是手机(mobile phone)、平板电脑(pad)、带无 线收发功能的电脑、虚拟现实(virtual reality,VR)终端、增强现实(augmented reality,AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、UE等。
上述终端设备可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接,使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问DN,使用DN上部署的运营商业务,和/或第三方提供的业务。其中,上述第三方可为运营商网络和终端设备之外的服务方,可为终端设备提供数据和/或语音等服务。其中,上述第三方的具体表现形式,具体可根据实际应用场景确定,在此不做限制。
核心网部分包括用户面功能和控制面功能。
用户面功能包括UPF网元。UPF网元作为和数据网络的接口,完成用户面数据(如分组数据包)转发、服务质量(quality of service,QoS)控制、基于会话/流级的计费统计,带宽限制等功能。
控制面功能主要进行用户注册认证、移动性管理、向用户面功能下发数据包转发策略、QoS控制策略等。控制面功能可以进一步细化包括除UPF网元之外的其它网元,如AMF网元和SMF网元等。
其中,AMF网元,主要进行用户接入时的注册流程,以及用户移动过程中的位置管理、接入鉴权/授权等功能。此外,还负责在UE与PCF间传递用户策略。
SMF网元,主要进行用户发起业务时建立相应的会话连接,为用户提供具体服务,如基于SMF与UPF之间的NG4接口向UPF下发数据包转发策略、QoS策略等功能。
AUSF网元,主要负责对用户进行鉴权,确定用户设备的合法性,以确定是否允许用户或设备接入网络。
UDM网元,主要负责存储用户设备的签约数据、用户接入授权等功能。
UDR,主要负责签约数据、策略数据、应用数据等类型数据的存取功能。
PCF网元,主要负责向AMF或SMF下发业务相关的策略。
NEF网元,主要用于支持能力和事件的开放。
AF网元,主要向PCF传递应用侧对网络侧的需求,使得PCF生成对应的策略。AF可以是第三方功能实体,也可以是运营商部署的应用服务,如网络协议(internet protocol,IP)多媒体子系统(IP Multimedia Subsystem,IMS)语音呼叫业务。
NRF网元,可用于提供网元发现功能,基于其他网元的请求,提供网元类型对应的网元信息。NRF还提供网元管理服务,如网元注册、更新、去注册以及网元状态订阅和推送等。
DN,是位于运营商网络之外的网络,运营商网络可以接入多个DN,DN上可部署多种业务,可为终端设备提供数据和/或语音等服务。例如,DN是某智能工厂的私有网络,智能工厂安装在车间的传感器可为终端设备,DN中部署了传感器的控制服务器,控制服务器可为传感器提供服务。传感器可与控制服务器通信,获取控制服务器的指令,根据指令将采集的传感器数据传送给控制服务器等。又例如,DN是某公司的内部办公网络,该公司员工的手机或者电脑可为终端设备,员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1中Nausf、Nnef、Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4,以及N6为接口序列号。这些接口序列号的含义可参见第三代合作伙伴计划(3rd generation partnership project,3GPP)标准协议中定义的含义,在此不做限制。
接入网是运营商网络的子网络,是运营商网络中业务节点与终端设备之间的实施系统。终端设备要接入运营商网络,首先是经过接入网,进而可通过接入网与运营商网络的业务节点连接。
接入网可以包括3GPP接入网和/或non-3GPP接入网,即终端设备可以通过3GPP接入网(或3GPP接入技术)和/或non-3GPP接入网(或N3GPP接入技术)接入核心网。non-3GPP接入网是指3GPP以外的接入网,如无线局域网(wireless local area networks,WLAN)、无线保真(wirelessfidelity,Wi-Fi)网络、全球微波互联接入(worldwide interoperability for microwave access,WiMAX)、固定网络等。其中,non-3GPP接入网可以包括可信的non-3GPP接入网、非可信的non-3GPP接入网和有线网络等。非可信的non-3GPP接入网例如可以包括非可信的WLAN、非可信的Wi-Fi网络、非可信的WiMAX等。可信的non-3GPP接入网例如可以包括可信的WLAN、可信的Wi-Fi网络、可信的WiMAX等,有线网络例如可以包括固定网络等。
终端设备在3GPP接入网中的接入可以称为3GPP接入,终端设备在non-3GPP接入网中的接入可以称为non-3GPP接入。
3GPP接入网的接入设备可以是为终端设备提供无线通信功能的设备,3GPP接入网的接入设备也可称为接入网设备。3GPP接入网的接入设备包括但不限于:5G中的下一代基站(g nodeB,gNB)、演进型节点B(evolved node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved nodeB,或home node B,HNB)、基带单元(baseBand unit,BBU)、传输点(transmitting and receiving point,TRP)、发射点(transmitting point,TP)、移动交换中心等。
非可信的non-3GPP接入网的接入设备可以称为non-3GPP转换功能(non-3GPP interworking function,N3IWF)设备或下一代接入网关(next generation packet data gateway,ngPDG)。N3IWF网元类似于长期演进(long term evolution,LTE)中的演进的分组数据网关(evolved packet data gateway,ePDG),在5G中用于终端设备通过non-3GPP接入网接入核心网时,和终端设备建立互联网协议安全性(internet protocol security,IPsec)隧道。在未来5G定义中,N3IWF的名字可能会更改,本申请仅以非3GPP网络接入网关为N3IWF设备进行举例说明。
举例说明,N3IWF设备可以包括路由器等。
在可信的non-3GPP接入网的接入设备可以包括可信的non-3GPP接入点(trusted non-3GPP access point,TNAP)和/或可信的non-3GPP接入网关(trusted non-3GPP gateway function,TNGF)。其中,TNAP用于和终端设备进行通信,TNGF用于和核心网设备进行通信。TNAP可以但不限于包括WLAN接入点(access point,AP),固定接入网设备(fixed access network,FAN),交换机,路由器等。
一种可能的示例中,终端设备通过3GPP接入网和非可信的non-3GPP接入网接入核心网可以如图2所示。其中,作为示例,UPF与3GPP接入网元的接口可以称为N3接口,UPF与N3IWF设备的接口可以称为N3接口,3GPP接入网元与AMF之间的接口可以称 为N2接口,N3IWF设备与AMF之间的接口可以称为N2接口,其他接口如图2所示,这里不再一一说明。
另一种可能的示例中,终端设备通过3GPP接入网和可信的non-3GPP接入网接入核心网可以如图3所示。其中,作为示例,UPF与3GPP接入网元的接口可以称为N3接口,UPF与TNGF网元的接口可以称为N3接口。3GPP接入网元与AMF之间的接口可以称为N2接口,TNGF网元与AMF之间的接口可以称为N2接口,TNGF网元统一TNAP之间的接口可以称为Ta,其他接口如图3所示,这里不再一一说明。
应理解,上述图2和图3仅是非可信的non-3GPP接入网和可信的non-3GPP接入网的架构示意图,并不限定终端设备接入核心网时所通过的接入网的类型以及数量。在具体实施中,终端设备可以通过两种或者两种以上的接入网接入核心网。终端设备接入核心网时所通过的接入网可以但不限于以下接入网类型中的一种或多种:3GPP接入网、非可信的non-3GPP接入网、或者可信的non-3GPP接入网,还可以为未来通信发展中出现的其他接入网类型。其中,非可信的non-3GPP接入网以及可信的non-3GPP接入网包括的网络类型,可以参阅前文关于非可信的non-3GPP接入网以及可信的non-3GPP接入网的介绍,这里不再重复说明。
其中,终端设备在3GPP接入网中的接入可以称为3GPP接入,终端设备在non-3GPP接入网中的接入可以称为non-3GPP接入。
应理解,3GPP接入以及non-3GPP接入仅是一种示例性命名,3GPP接入还可以描述为3GPP接入链路、3GPP传输通道、3GPP传输路径、3GPP传输链路、3GPP通信链路等。只要通信链路是基于3GPP接入技术的,均可以理解为本申请所述的3GPP接入。
non-3GPP接入还可以描述为non-3GPP接入链路、non-3GPP传输通道、non-3GPP传输路径、non-3GPP传输链路等。只要通信链路是基于non-3GPP接入技术的,均可以理解为本申请所述的non-3GPP接入。
可以理解的,本申请下文中涉及的第一接入也可以称为第一接入链路、第一传输通道、第一传输路径、第一传输链路、第一通信链路等。
下文中涉及的第二接入也可以称为第二接入链路、第二传输通道、第二传输路径、第二传输链路、第二通信链路等。
可以理解的是,上述网元或者功能既可以是硬件设备中的网络元件,也可以是在专用硬件上运行的软件功能,或者是平台(例如,云平台)上实例化的虚拟化功能。上述网元或者功能可划分出一个或多个服务,进一步,还可能会出现独立于网络功能存在的服务。在本申请中,上述功能的实例、或上述功能中包括的服务的实例、或独立于网络功能存在的服务实例均可称为服务实例。
进一步地,可以将上述a网元简称为a,例如,可以将AF网元简称为AF,NEF网元简称为NEF,AMF网元简称为AMF,等等。
应当理解,图1-图3仅为适用的网络架构的示例,实际应用的网络架构可以包括比图1-图3更多或更少的网元。本申请实施例上述所使用的各个网元的名称,在未来通信系统中,可能保持功能相同,但名称会改变。
前文介绍了本申请实施例所涉及到的网络架构。以下,对本申请实施例中的部分用语进行解释说明,以便于本领域技术人员理解。
移动性管理参数:移动性管理参数可以但不限于包括密钥集标识(ngKSI或者eKSI)、 或者全球唯一临时终端标识(globally unique temporary UE identity,GUTI)、或者最后一次访问的最后访问的跟踪区的跟踪区标识(tracking zrea identity,TAI)等参数。
密钥集标识:密钥集标识用于标识NAS安全上下文信息。其中,NAS安全上下文信息可以但不限于包括:NAS完整性保护算法、或者NAS加密算法、服务网络中AMF的密钥(KAMF)、用户设备(user equipment,UE)安全能力信息等信息。
NAS完整性保护算法,也可以称为5G完整性保护算法、完整性保护算法等,用于对NAS消息进行完整性验证。
NAS加密算法,也可以称为5G加密算法、安全加密算法等,用于对NAS消息进行加密。
GUTI:是由核心网分配给UE的临时性标识。
本申请实施例中“至少一个”是指一个或者多个,“多个”是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,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可以是单个,也可以是多个。
以及,除非有相反的说明,本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分,不用于限定多个对象的大小、内容、顺序、时序、优先级或者重要程度等。例如,第一接入和第二接入,只是为了区分不同的接入,而并不是表示这两个接入的优先级或者重要程度等的不同。
下面介绍本申请实施例涉及的技术特征。
如前文图2或图3所示,终端设备可以通过多个接入与核心网通信,例如,终端设备可以通过3GPP接入以及non-3GPP接入与核心网通信。当终端设备的多个接入注册到同一个PLMN时,终端设备的多个接入的通信可能共用一些参数,也就是终端设备和核心网设备维护一套参数。例如,为了实现密码分离和重放保护,终端设备的多个接入共用NAS安全上下文信息以及GUTI。
由于终端设备的多个接入共用一些参数,若终端设备的一个接入对这些参数进行操作,会对其他接入的通信产生影响。例如,终端设备通过接入A收到拒绝消息,该拒绝消息中携带原因值。终端设备根据该原因值可能对删除接入A的密钥集标识和/或GUTI。
例如,该拒绝消息中携带的原因值为#3或者#6,该原因值指示非法终端(Illegal UE)。目前,终端设备在接收到该原因值后,可以有以下至少一项处理:将5GS更新状态为5U3漫游不允许(5U3ROAMING NOT ALLOWED);删除GUTI、最后访问的跟踪区的TAI、TAI列表和密钥集标识中的一项或多项;在PLMN的情况下,将全球用户识别卡(universal subscriber identity module,USIM)视为对5GS服务无效,直到关闭或者删除包含USIM的通用集成电路卡(universal integrated circuit card,UICC)或定时器T3245到期。
又例如,该拒绝消息中携带的原因值为#7:该原因值指示5GS服务不被允许(5GS services not allowed)。目前,终端设备在接收到该原因值后,可以有以下至少一项处理:将5GS更新状态为5U3漫游不允许;删除GUTI、最后访问的跟踪区的TAI、TAI列表和密钥集标识中的一项或多项;在PLMN的情况下,将USIM视为对5GS服务无效,直到 关闭或者删除包含USIM的UICC或定时器T3245到期。
又例如,该拒绝消息中携带的原因值为#11:该原因值指示PLMN不被允许(PLMN not allowed)。目前,终端设备在接收到该原因值后,可以有以下至少一项处理:将5GS更新状态为5U3漫游不允许;删除GUTI、最后访问的跟踪区的TAI、TAI列表和密钥集标识中的一项或多项。
又例如,该拒绝消息中携带的原因值为#72:该原因值指示non-3GPP接入对于5G核心网(5G Core Network,5GCN)不被允许(non-3GPP access to 5GCN not allowed)。目前,终端设备在接收到该原因值后,可以有以下至少一项处理:若通过non-3GPP接入接入核心网,将5GS更新状态为5U3漫游不允许;删除GUTI、最后访问的跟踪区的TAI、TAI列表和密钥集标识中的一项或多项。
又例如,该拒绝消息中携带的原因值为#12:该原因值指示跟踪区不被允许(Tracking area not allowed)。目前,终端设备在接收到该原因值后,可以有以下至少一项处理:将5GS更新状态为5U3漫游不允许;删除GUTI、最后访问的跟踪区的TAI、TAI列表和密钥集标识中的一项或多项;重置注册尝试计数器。
又例如,该拒绝消息中携带的原因值为#78:该原因值指示PLMN不允许在当前的终端设备位置运行(PLMN not allowed to operate at the present UE location)。目前,终端设备在接收到该原因值后,可以有以下至少一项处理:将5GS更新状态为5U3漫游不允许;删除GUTI、最后访问的跟踪区的TAI、TAI列表和密钥集标识中的一项或多项。
由于终端设备对于接入A和接入B维护一套NAS安全上下文信息和一个GUTI,若删除接入A的密钥集标识,将导致接入A和接入B的NAS安全上下文信息被删除,从而导致接入B的上行信令无法进行完整性保护和加密,下行信令因完整性检查失败而无法正常接收等。若删除接入A的GUTI,将导致接入B的一些消息中无法携带GUTI信息,从而导致PLMN无法识别终端设备的身份、终端设备也无法接收PLMN的寻呼等。
基于此,本申请实施例提供一种通信方法及装置,用于解决终端设备的部分接入对公共参数的操作导致终端设备在其他接入上无法正常通信的问题。其中,方法和装置是基于同一构思的,由于方法及装置解决问题的原理相似,因此装置与方法的实施可以相互参见,重复之处不再赘述。
本申请提供的通信方法可以应用于各类通信系统中,例如,可以是物联网(internet of things,IoT)、窄带物联网(narrow band internet of things,NB-IoT)、长期演进(long term evolution,LTE),也可以是第五代(5G)通信系统,还可以是LTE与5G混合架构、也可以是5G新无线(new radio,NR)系统以及6G或者未来通信发展中出现的新的通信系统等。本申请所述的通信系统还可以是机器到机器(machine to machine,M2M)网络、非地面网络(non-terrestrial network,NTN)网络或者其他网络。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题同样适用。
本申请实施例中“若……”,也可以描述为“在……情况下”或者“如果”或者“当……时”等等。例如,“若终端设备的第二接入的状态为正在第一PLMN上进行注册或已注册在第一PLMN上”,也可以描述为“如果终端设备的第二接入的状态为正在第一PLMN上进行注 册或已注册在第一PLMN上”,或者“在终端设备的第二接入的状态为正在第一PLMN上进行注册或已注册在第一PLMN上的情况下”或者“当终端设备的第二接入的状态为正在第一PLMN上进行注册或已注册在第一PLMN上时”等等。
本申请实施例中“从……切换到……”也可以描述为“从(或者由)……换到……”、或者“从(或者由)……重选到……”或者“从(或者由)……选择到……”或者“从(或者由)……变为……”或者“从(或者由)……变化为……”或者“从(或者由)……改变为……”等。
例如,下文中“终端设备的第一接入从第一PLMN切换到第二PLMN”,可以描述为“终端设备的第一接入从(或者由)第一PLMN换到第二PLMN”,或者“终端设备的第一接入从(或者由)第一PLMN重选到第二PLMN”,或者“终端设备的第一接入从(或者由)第一PLMN选择到第二PLMN”,或者“终端设备的第一接入从(或者由)第一PLMN变为第二PLMN”,或者“终端设备的第一接入从(或者由)第一PLMN变化为第二PLMN”,或者“终端设备的第一接入从(或者由)第一PLMN改变为第二PLMN”等等。
为了便于描述,下面以终端设备通过第一接入以及第二接入接入核心网为例进行描述。其中,第一接入和第二接入属于不同的接入类型,或者,也可以描述为第一接入和第二接入的接入技术不同。例如,第一接入为3GPP接入,第二接入为可信的non-3GPP接入或者非可信的non-3GPP接入。或者,第一接入为可信的non-3GPP接入或者非可信的non-3GPP接入,第二接入为3GPP接入。
又例如,第一接入为可信的non-3GPP接入,第二接入为非可信的non-3GPP接入。或者,第一接入为非可信的non-3GPP接入,第二接入为可信的non-3GPP接入。
应理解,本申请实施例并不限定终端设备仅有两种接入,在具体实施中,终端设备还可以通过第一接入、第二接入以及其他的接入(如第三接入、第四接入等)接入核心网。其中,所述其他的接入、第一接入、第二接入均属于不同的接入类型,也即对应(或者应用)的接入技术不同。
本申请实施例中,终端设备可以通过接入网的接入设备与核心网设备进行通信。例如,在3GPP接入网中,终端设备可以通过接入网设备与核心网设备进行通信。又例如,在non-3GPP接入网中,终端设备可以通过N3IWF设备与核心网设备进行通信。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。
本申请实施例可以应用于终端设备的第一接入的第一移动性管理参数需要被删除的场景中。其中,若第一接入注册的PLMN和第二接入注册的PLMN相同,第一接入和第二接入共用第一移动性管理参数。
示例性的,第一移动性管理参数可以包括如下至少一项:密钥集标识,或者GUTI。第一移动性管理参数还可以包括第一接入和第二接入共用的其他参数,这里不再一一列举。
下面介绍第一接入的第一移动性管理参数需要被删除的三种情况。应理解,本申请不限于在如下三种情况中第一接入的第一移动性管理参数需要被删除,只要在某种情况下第一接入的第一移动性管理参数需要被删除,均可以视为本申请实施例中第一接入的第一移动性管理参数需要被删除的情况。在其他场景中终端设备对第一接入的第一移动性管理参数的处理方式与本申请中终端设备在如下三种情况中对第一接入的第一移动性管理参数的处理方式类似。
情况一,终端设备的第一接入从第一PLMN切换到第二PLMN。
其中,第二PLMN不是第一接入已注册的PLMN(registered PLMN,RPLMN),第二 PLMN也不是第一接入的等效PLMN(equivalent PLMN,EPLMN)。
情况二,终端设备通过第一接入获取第一信息,第一信息指示核心网设备拒绝终端设备的请求的原因。在该示例中,终端设备可以根据该第一信息确定第一接入的第一移动性管理参数需要被删除。
一种可能的实现方式中,终端设备可以通过第一接入接收注册拒绝消息,该注册拒绝消息可以携带原因值。或者,终端设备可以通过第一接入接收业务拒绝消息,该业务拒绝消息携带原因值。或者,终端设备可以通过第一接入接收去注册请求消息,该去注册请求消息中携带原因值。在该举例说明中,原因值可以理解为上述第一信息。
示例性的,若终端设备通过第一接入接收到的原因值为前文所述的#3或者#6,或者,前文所述的#7,或者,前文所述的#11,或者,前文所述的#72,或者,前文所述的#12,或者,前文所述的#78,终端设备可以确定第一接入的第一移动性管理参数需要被删除。
应理解,这里仅是示例性的示出七种原因值,并不限定只能通过这七种原因值确定第一接入的第一移动性管理参数被删除。
情况三,第一接入的第一移动性管理参数需要被删除的场景还可以为:终端设备通过第一接入接收第一消息。在该示例中,终端设备可以在接收到该第一消息后确定第一接入的第一移动性管理参数需要被删除。该第一消息中没有携带第一信息。
在该示例中,第一消息可以是终端设备通过第一接入接收的鉴权拒绝消息或者其他消息。
以第一消息为鉴权拒绝消息为例,终端设备通过第一接入接收到鉴权拒绝消息后,若鉴权拒绝消息已通过NAS完整性检查成功,则可以确定第一接入的第一移动性管理参数需要被删除。
下面将结合上述三种情况对本申请实施例提供的通信方法进行说明。
结合上述情况一,如图4所示,为本申请实施例提供的一种通信方法的流程示意图。
S401,终端设备确定第一接入从第一PLMN切换到第二PLMN。
在S401之后,可以执行S402或者S403。
可选的,在S401之前,第一接入已注册到第一PLMN。
下面结合3GPP接入和non-3GPP接入对S401的实现方式进行说明。
若第一接入为3GPP接入,终端设备可以通过如下方式确定第一接入从第一PLMN切换到第二PLMN:终端设备的第一接入由第一小区切换到第二小区,其中,第一小区对应的PLMN为第一PLMN。终端设备通过第一接入接收第二小区广播的系统信息,该系统信息中可以携带该第二小区所属的PLMN信息。终端设备可以根据系统信息中携带的PLMN信息以及本地保存的第一接入的PLMN信息确定第一接入从第一PLMN切换到第二PLMN。
若第一接入为non-3GPP接入,终端设备可以通过如下方式确定第一接入从第一PLMN切换到第二PLMN:终端设备确定与第一接入设备之间的连接中断,该第一接入设备对应的PLMN为第一PLMN。终端设备向第二接入设备发送请求消息,该请求消息用于请求与第二接入设备建立通信连接,第二接入设备对应的PLMN为第二PLMN。终端设备接收第二接入设备的响应消息,该响应消息用于指示终端设备接入第二接入设备。终端设备根据第二接入设备对应的PLMN确定第一接入从第一PLMN切换到第二PLMN。
其中,第一接入设备、第二接入设备可以参阅前文网络架构介绍中non-3GPP接入网的接入设备的相关描述。
S402,若第二接入的状态为正在第一PLMN上进行注册或已注册在第一PLMN上,终端设备确定不删除第一接入的第一移动性管理参数。
可选的,在S402之后,若第二接入从第一PLMN中去注册(或者注销或者脱离第一PLMN等),可以确定删除第一接入的第一移动性管理参数。
示例性的,第二接入从第一PLMN中去注册的一种实现场景为第二接入从第一PLMN切换到第三PLMN。其中,第三PLMN与第一PLMN不同,第三PLMN与第二PLMN可以相同,也可以不同。
S403,若第二接入的状态为未注册在第一PLMN上,终端设备确定删除第一接入的第一移动性管理参数。
作为一种可能的实施方式,假设第一移动性管理参数包括密钥集标识,该密钥集标识所标识的NAS安全上下文信息中包括安全加密算法,该安全加密算法可以为空加密算法,例如,5G-EA0算法或者未来通信发展中出现的其他算法。
从而,终端设备在确定删除第一接入的第一移动性管理参数之前,可以确定该安全加密算法为空加密算法。
由于安全加密算法为空加密算法时NAS空口消息不加密,因此NAS空口消息的安全性较低,上述方式通过在密钥集标识所标识的NAS安全上下文信息中安全加密算法为空加密算法时删除第一移动性管理参数,有利于终端设备的通信安全。
可选的,终端设备(或者核心网设备)在确定不删除第一移动性管理参数后可以执行相应的动作。例如,不删除第一移动性管理参数,或者,保留第一移动性管理参数,或者对第一移动性管理参数不处理等等。
可选的,终端设备(或者核心网设备)在确定删除第一移动性管理参数后可以执行相应动作。例如,删除第一移动性管理参数。
以第一移动性管理参数中的密钥集标识为例,删除密钥集标识,可以通过如下至少一种方式实现:
将密钥集标识的值(the ngKSI to the value)设置为“没有可用的密钥;
确定KAMF的密钥、K'AMF、NAS加密密钥以及NAS完整性密钥中的一种或多种无效。
其中,“KAMF的密钥、K'AMF、NAS加密密钥以及NAS完整性密钥中的一种或多种无效”也可以描述为密钥集标识相关的NAS安全上下文信息无效或者不再有效。
以第一移动性管理参数中的GUTI为例,删除GUTI,可以通过如下方式实现:将GUTI设置为无效。
通过第二接入是否在第一PLMN(即第一接入注册的PLMN)上进行注册,可以确定终端设备在第二接入上的通信是否需要使用第一移动性管理参数。本申请实施例中通过在终端设备的第二接入未注册在第一PLMN的情况下,删除第一接入的第一移动性管理参数,可以在不影响终端设备在第二接入上的通信的前提下,降低终端设备维护信息的成本,还可以避免终端设备在第一接入上使用无效的参数(即第一移动性管理参数)进行通信,从而可以提升终端设备在第一接入上的通信性能。
在终端设备的第二接入注册到第一PLMN或者正在第一PLMN上进行注册的情况下不删除第一移动性管理参数,可以保证终端设备在第二接入上正常通信。
结合上述情况二,如图5所示,为本申请实施例提供的一种通信方法的流程示意图。
S501,核心网设备通过第一接入向终端设备发送第一信息。相应的,终端设备通过第一接入获取第一信息。
第一信息可以承载在注册拒绝消息、或者业务拒绝消息、或者去注册消息等消息承载,应理解,这里仅是一些举例说明,并不限定承载第一信息的具体消息。
其中,第一信息可以参阅前文情况二中的相关描述,这里不再重复赘述。
示例性的,该核心网设备可以是第一接入所接入的核心网设备。
S502,终端设备根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数。
举例说明,第二接入的信息可以包括如下至少一项:第二接入的注册信息、或者第二接入的业务信息,或者,第二接入的信息还可以包括其他信息,这里不做具体限定。
其中,注册信息可以表征第二接入的PLMN注册情况,第二接入上的业务信息为第二接入上是否存在正在进行紧急业务的信息。
一种可能的实现方式中,终端设备可以根据第一信息确定第一接入的第一移动性管理参数需要被删除。终端设备根据第二接入的信息确定是否删除第一接入的第一移动性管理参数。其中,终端设备根据第一信息确定第一接入的第一移动性管理参数需要被删除的实现方式,可以参阅前文情况二的相关描述。
一种示例性说明中,第一信息可以适用于第一接入,但是不适用于第二接入。或者,第一信息也可以对第一接入和第二接入都适用。下面结合具体原因值对第一信息是否适用于第一接入和第二接入进行说明。
例如,若第一信息为前文所述的原因值#3或者原因值#6,该原因值指示非法终端,也就是,终端设备不被允许。因此,该终端设备的第一接入和第二接入都不被允许,也就是,第一信息对第一接入和第二接入都适用。
又例如,若第一信息为前文所述的原因值#7,该原因值指示5GS服务不被允许,也就是,终端设备的5GS服务不被允许。因此,该终端设备的第一接入和第二接入都不被允许,也就是,第一信息对第一接入和第二接入都适用。
又例如,若第一信息为前文所述的原因值#11,该原因值指示PLMN不被允许,也就是,第一接入的PLMN不被允许。若第二接入已注册(或者正在注册)的PLMN与第一接入注册的PLMN相同,则第一信息也适用于第二接入。若第二接入已注册(或者正在注册)的PLMN与第一接入注册的PLMN不同,则第一信息不适用于第二接入。
又例如,若第一信息为前文所述的原因值#72,该原因值指示non-3GPP接入对于5GCN不被允许。
可以理解的,终端设备通过第一接入接收到原因值#72,可见第一接入为non-3GPP接入,第一信息是适用于第一接入的。若第二接入为3GPP接入,则第一信息不适用于第二接入。
又例如,若第一信息为前文所述的原因值#12,该原因值指示跟踪区不被允许,该原因值适用于3GPP接入。
可以理解的,终端设备通过第一接入接收到原因值#12,可见,第一信息是适用于第一接入的,也就是第一接入为3GPP接入。若第二接入为non-3GPP接入,则第一信息不适用于第二接入。
又例如,若第一信息为前文所述的原因值#78,该原因值指示PLMN不允许在当前的 终端设备位置运行。该原因值适用于3GPP接入。
可以理解的,终端设备通过第一接入接收到原因值#78,可见第一信息是适用于第一接入的,也就是第一接入为3GPP接入。因此,若第二接入为non-3GPP接入,则第一信息不适用于第二接入。
下面结合第一信息适用于第一接入,但第一信息不适用于第二接入的场景,对终端设备根据第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式进行说明。
假设第一信息不适用于第二接入,作为一种实现方式,终端设备可以根据第二接入的注册信息确定是否删除第一接入的第一移动性管理参数。
可选的,终端设备可以在第二接入的注册信息满足如下条件之一时确定删除第一接入的第一移动性管理参数:第二接入未注册到PLMN、或者第二接入注册的PLMN与第一接入注册的PLMN不同。
终端设备可以在第二接入的注册信息满足如下条件时确定不删除第一接入的第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同。
其中,第二接入注册的PLMN与第一接入注册的PLMN不同,可以理解为,第二接入注册的PLMN与第一接入当前注册的PLMN,且第二接入注册的PLMN不是第一接入的RPLMN,第二PLMN也不是第一接入的EPLMN。相应的,下文中涉及的第二接入注册的PLMN与第一接入注册的PLMN相同,可以理解为,第二接入注册的PLMN与第一接入当前注册的PLMN,或者第二接入注册的PLMN是第一接入的RPLMN,或者第二PLMN是第一接入的EPLMN。
应理解,下文中对第二接入注册的PLMN与第一接入注册的PLMN不同的理解,对第二接入注册的PLMN与第一接入注册的PLMN相同的理解,与此处的描述相同,下文不再一一说明。
假设第一信息适用于第二接入,作为一种实现方式,终端设备可以根据第二接入的注册信息以及第二接入上的业务信息确定是否删除第一接入的第一移动性管理参数。
可选的,终端设备可以在第二接入的注册信息满足如下条件之一时确定删除第一接入的第一移动性管理参数:第二接入未注册到PLMN;或者,第二接入注册的PLMN与第一接入注册的PLMN不同。
终端设备可以在第二接入的注册信息以及第二接入上的业务信息满足如下条件之一时确定删除第一接入的第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上没有正在进行的紧急业务。
终端设备可以在第二接入的注册信息以及第二接入上的业务信息满足如下条件时确定不删除第一接入的第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上存在正在进行紧急业务。
作为一种可选的方案,终端设备可以在第二接入上的紧急业务结束之后确定删除第一接入的第一移动性管理参数。
以上介绍了终端设备根据第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式。
可选的,核心网设备在发送第一信息后的行为,也可以根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数。
其中,核心网设备根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式,与终端设备根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式类似。区别在于,终端设备可以在第二接入的注册信息满足如下条件之一时确定删除第一接入的第一移动性管理参数:第二接入未注册到PLMN;或者,第二接入注册的PLMN与第一接入注册的PLMN不同。而核心网设备在第二接入的注册信息满足如下条件之一时确定删除第一接入的第一移动性管理参数:第二接入未注册到PLMN。具体可以参阅终端设备根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式。
可选的,终端设备和/或核心网设备还可以执行以下四种方案中一种或多种:
方案一,若确定删除第一接入的第一移动性管理参数,可以删除第二移动性管理参数和/或第三移动性管理参数。第二移动性管理参数包括如下至少一项:在第二接入上的最后访问的跟踪区的TAI、或者第二接入的TAI列表(TAI list)。第三移动性管理参数包括如下至少一项:在第一接入上的最后访问的跟踪区的TAI、或者第一接入的TAI list。
示例性的,“在第二接入上的最后访问的跟踪区的TAI”,也可以描述为第二接入对应的最后访问的跟踪区的TAI,或者,终端设备在第二接入对应的接入网中最后访问的跟踪区的TAI,等等。“在第一接入上的最后访问的跟踪区的TAI”,也可以描述为第一接入对应的最后访问的跟踪区的TAI,或者,终端设备在第一接入对应的接入网中最后访问的跟踪区的TAI,等等。
应理解,第二移动性管理参数、第三移动性管理参数也可以包括其他参数,这里不做具体限定。
方案二,若确定删除第一移动性管理参数,可以停止所述第二接入上正在进行的业务。
需要说明的是,本申请实施例中“停止”也可以描述终止、取消、中止、打断等。
方案三,若确定删除第一移动性管理参数,终端设备可以启动第二接入的第一定时器或者释放第二接入的N1 NAS信令连接。核心网设备可以释放第二接入的N1 NAS信令连接。
其中,第一定时器用于触发终端设备释放第二接入的N1 NAS信令连接。一种示例性说明中,第一定时器用于允许核心网设备释放第二接入的N1 NAS信令连接。
在该可选的方案中,终端设备可以在第一定时器超时时释放第二接入的N1 NAS信令连接。
可选的,在第一定时器超时之前,若核心网设备释放了第二接入的N1 NAS信令连接,终端设备可以停止第一定时器。
方案四,若确定删除第一移动性管理参数,如果第二接入上存在正在进行的移动管理流程,可以停止该移动管理流程。
示例性的,移动管理流程可以包括如下流程中一项或多项:公共流程(5GMM common procedures)、特定流程(5GMM specific procedures:)、连接管理流程(5GMM connection management procedures)等。
其中,公共流程可以但不限于包括:身份认证流程、鉴权流程、安全模式控制流程、UE配置更新流程、上行传输流程、下行传输流程、或者切片鉴权流程等。
特定流程可以但不限于包括:注册流程、或者去注册流程等。
连接管理流程可以但不限于包括:业务请求流程、或者寻呼流程等。
应理解,移动管理流程还可以包括其他流程,这里不再一一列举。
需要说明的是,上述四种可选的方案中,终端设备确定删除第一移动性管理参数,可以是终端设备根据第二接入的信息确定的,也可以是在第二接入上的紧急业务结束后确定的。
可选的,终端设备(或者核心网设备)在确定不删除第一移动性管理参数后可以执行相应的动作。例如,不删除第一移动性管理参数,或者,保留第一移动性管理参数,或者对第一移动性管理参数不处理等等。
可选的,终端设备(或者核心网设备)在确定删除第一移动性管理参数后可以执行相应动作。例如,删除第一移动性管理参数。
其中,删除第一移动性管理参数的实现方式可以参阅图4所述方法中的相关描述。
本申请实施例中,在删除第一接入的第一移动性管理参数时通过考虑第二接入的信息,可以在第二接入需要第一移动性管理参数的情况下不删除第一移动性管理参数,从而使得终端设备在第二接入上可以使用第一移动性管理参数进行通信,避免出现因删除第一接入的第一移动性管理参数导致第二接入上无法正常通信的问题,降低对第二接入上的通信的影响。
并且,通过终端设备判断是否删除第一移动性管理参数,灵活性更高,准确性也比较好。
结合上述情况三,如图6所示,为本申请实施例提供的一种通信方法的流程示意图。
S601,核心网设备通过第一接入向终端设备发送第一消息。相应的,终端设备通过第一接入接收第一消息。
其中,第一消息可以参阅前文情况三中的相关描述,这里不再重复赘述。
S602,终端设备根据第一消息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数。
一种可能的实现方式中,终端设备可以根据第一消息确定第一接入的第一移动性管理参数需要被删除。终端设备根据第二接入的信息确定是否删除第一接入的第一移动性管理参数。
其中,终端设备根据第一消息确定第一接入的第一移动性管理参数需要被删除的实现方式,可以参阅前文情况三的相关描述。
终端设备根据第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式,可以参阅图5所述方法中终端设备根据第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式,这里不再重复说明。
可选的,核心网设备在发送第一信息后的行为,也可以根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数。
核心网设备根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式,可以参阅图5所述方法中核心网设备根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式,这里不再重复说明。
可选的,终端设备和/或核心网设备还可以执行以下四种方案中一种或多种:删除第二移动性管理参数和/或第三移动性管理参数;或者,停止所述第二接入上正在进行的业务;或者,启动第二接入的第一定时器或者释放N1 NAS信令连接;或者,停止第二接入上正在进行的移动管理流程。
其中,删除第二移动性管理参数和/或第三移动性管理参数、停止所述第二接入上正在进行的业务、启动第二接入的第一定时器或者释放N1 NAS信令连接、以及停止第二接入上正在进行的移动管理流程的实现方式可以参阅图5所述方法中的相关描述。
可选的,终端设备(或者核心网设备)在确定不删除第一移动性管理参数后可以执行相应的动作。例如,不删除第一移动性管理参数,或者,保留第一移动性管理参数,或者对第一移动性管理参数不处理等等。
可选的,终端设备(或者核心网设备)在确定删除第一移动性管理参数后可以执行相应动作。例如,删除第一移动性管理参数。
其中,删除第一移动性管理参数的实现方式可以参阅图4所述方法中的相关描述。
本申请实施例中,在删除第一接入的第一移动性管理参数时通过考虑第二接入的信息,可以在第二接入需要第一移动性管理参数的情况下不删除第一移动性管理参数,从而使得终端设备在第二接入上可以使用第一移动性管理参数进行通信,避免出现因删除第一接入的第一移动性管理参数导致第二接入上无法正常通信的问题,降低对第二接入上的通信的影响。
并且,通过终端设备判断是否删除第一移动性管理参数,灵活性更高,准确性也比较好。
以上介绍由终端设备确定是否删除第一移动性管理参数的方法。下面结合上述情况二和情况三对核心网设备指示终端设备是否删除第一移动性管理参数的方法进行说明。
如图7所示,为本申请实施例提供的一种通信方法的流程示意图。
S701,核心网设备确定第一指示信息。
其中,终端设备可以通过第一接入该核心网设备。
一种可能的实现方式中,该核心网设备可以根据第二指示信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数,第二指示信息指示核心网设备拒绝终端设备的请求的原因。
其中,第二指示信息可以为前文所述情况二中的第一信息。
核心网设备根据第二指示信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式,可以参阅图5所述方法中核心网设备根据第一信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式。
另一种可能的实现方式中,该核心网设备可以根据第一消息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数。其中,第一消息可以参阅前文情况三种的相关描述。
核心网设备根据第一消息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式,可以参阅图6所述方法中核心网设备根据第一消息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数的实现方式。
S702,核心网设备通过第一接入向终端设备发送第一指示信息。相应的,终端设备通过第一接入接收第一指示信息。
第一指示信息指示是否删除第一接入的第一移动性管理参数。
其中,第一指示信息可以通过显式指示的方式指示是否删除第一接入的第一移动性管理参数。例如,第一指示信息通过一个或多个比特的不同取值指示是否删除第一接入的第一移动性管理参数,举例说明,第一指示信息可以通过该一个或多个比特的第一取值指示 删除第一接入的第一移动性管理参数,通过第二取值指示不删除第一接入的第一移动性管理参数。
或者,第一指示信息可以通过隐式指示的方式指示删除第一接入的第一移动性管理参数。例如,第一指示信息携带特定字段,则指示不删除第一接入的第一移动性管理参数,若不携带特定字段,则指示删除第一接入的第一移动性管理参数。
或者,第一指示信息可以通过隐式指示的方式指示不删除第一接入的第一移动性管理参数。例如,第一指示信息携带特定字段,则指示删除第一接入的第一移动性管理参数,若不携带特定字段,则指示不删除第一接入的第一移动性管理参数。
S703,终端设备根据第一指示信息确定是否删除第一接入的第一移动性管理参数。
一种可能的实现方式中,终端设备可以根据第一指示信息以及第二接入的信息确定是否删除第一接入的第一移动性管理参数。
一种具体的实现方式中,终端设备可以根据第一指示信息以及第二接入的注册信息确定是否删除第一接入的第一移动性管理参数。
例如,若第一指示信息指示删除第一接入的第一移动性管理参数,第二接入的注册信息满足如下条件之一时确定删除第一接入的第一移动性管理参数:第二接入未注册到PLMN、或者第二接入注册的PLMN与第一接入注册的PLMN不同。
又例如,若第一指示信息指示删除第一接入的第一移动性管理参数,且第二接入注册的PLMN与第一接入注册的PLMN相同,根据第二接入上的业务信息确定是否删除第一接入的第一移动性管理参数,第二接入上的业务信息为第二接入上是否正在进行紧急业务的信息。
举例说明,若第二接入上存在正在进行紧急业务,确定不删除第一接入的第一移动性管理参数。或者,若第二接入上没有正在进行的紧急业务,确定删除第一接入的第一移动性管理参数。
可选的,终端设备还可以执行以下四种方案中一种或多种:删除第二移动性管理参数和/或第三移动性管理参数;或者,停止所述第二接入上正在进行的业务;或者,启动第二接入的第一定时器或者释放N1 NAS信令连接;或者,停止第二接入上正在进行的移动管理流程。
其中,删除第二移动性管理参数和/或第三移动性管理参数、停止所述第二接入上正在进行的业务、启动第二接入的第一定时器或者释放N1 NAS信令连接、以及停止第二接入上正在进行的移动管理流程的实现方式可以参阅图5所述方法中的相关描述。
可选的,终端设备(或者核心网设备)在确定不删除第一移动性管理参数后可以执行相应的动作。例如,不删除第一移动性管理参数,或者,保留第一移动性管理参数,或者对第一移动性管理参数不处理等等。
可选的,终端设备(或者核心网设备)在确定删除第一移动性管理参数后可以执行相应动作。例如,删除第一移动性管理参数。
其中,删除第一移动性管理参数的实现方式可以参阅图4所述方法中的相关描述。
本申请实施例中通过网络设备指示终端设备是否删除第一接入的第一移动性管理参数,可以降低终端设备的复杂度。
并且,在删除第一接入的第一移动性管理参数时通过考虑第二接入的信息,可以在第二接入需要第一移动性管理参数的情况下不删除第一移动性管理参数,从而使得终端设备 在第二接入上可以使用第一移动性管理参数进行通信,避免出现因删除第一接入的第一移动性管理参数导致第二接入上无法正常通信的问题,降低对第二接入上的通信的影响。
基于与方法实施例的同一构思,本申请实施例提供一种通信装置,该通信装置的结构可以如图8所示,包括处理模块801。可选的,该装置还可以包括通信模块802。
在一种实施方式中,通信装置具体可以用于实现图4的实施例中终端设备执行的方法,该装置可以是终端设备本身,也可以是终端设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。其中,处理模块801,用于确定所述终端设备的第一接入从第一PLMN切换到第二PLMN;以及,若所述终端设备的第二接入的状态为正在所述第一PLMN上进行注册或已注册在所述第一PLMN上,确定不删除第一接入的第一移动性管理参数;以及,若所述第二接入的状态为未注册在所述第一PLMN上,确定删除所述第一移动性管理参数;其中,所述第一接入和所述第二接入属于不同的接入类型。
可选的,所述处理模块801,还用于:在所述终端设备的确定所述第一接入从所述第一PLMN切换到所述第二PLMN之前,确定所述第一接入已注册到所述第一PLMN。
所述处理模块801,还可以用于:在确定不删除所述第一移动性管理参数之后,若所述第二接入从所述第一PLMN切换到第三PLMN,确定删除所述第一移动性管理参数。
示例性的,所述第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,所述密钥集标识用于标识NAS安全上下文信息。
可选的,所述NAS安全上下文信息包括安全加密算法,所述安全加密算法为空加密算法。
在一种实施方式中,通信装置具体可以用于实现图5的实施例中终端设备执行的方法,该装置可以是终端设备本身,也可以是终端设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。其中,通信模块802,用于通过该终端设备的第一接入获取第一信息。处理模块801,用于根据第一信息以及该终端设备的第二接入的信息确定是否删除第一接入的第一移动性管理参数。其中,第一信息指示核心网设备拒绝该终端设备的请求的原因,第一接入和第二接入属于不同的接入类型。
可选的,第一信息不适用于第二接入;处理模块801,在根据第一信息以及终端设备的第二接入的信息确定是否删除第一移动性管理参数时,具体用于:根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数。
处理模块801,在根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数时,具体用于:在第二接入的注册信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN、或者第二接入注册的PLMN与第一接入注册的PLMN不同。
处理模块801,在根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数时,具体用于:在第二接入的注册信息满足如下条件时确定不删除第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同。
可选的,第一信息适用于第二接入;处理模块801,在根据第一信息以及终端设备的第二接入的信息确定是否删除第一移动性管理参数时,具体用于:根据第一信息、第二接入的注册信息以及第二接入上的业务信息确定是否删除第一移动性管理参数,第二接入上的业务信息为第二接入上是否存在正在进行紧急业务的信息。
处理模块801,在根据第一信息、第二接入的注册信息以及第二接入上的业务信息处 理第一移动性管理参数时,具体用于:在第二接入的注册信息以及第二接入上的业务信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN;或者,第二接入注册的PLMN与第一接入注册的PLMN不同;或者,第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上没有正在进行的紧急业务。
处理模块801,在根据第一信息、第二接入的注册信息以及第二接入上的业务信息处理第一移动性管理参数时,具体用于:在第二接入的注册信息以及第二接入上的业务信息满足如下条件时确定不删除第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上存在正在进行紧急业务。
可选的,处理模块801,还用于在紧急业务结束之后确定删除第一移动性管理参数。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,删除第二移动性管理参数,第二移动性管理参数包括如下至少一项:在第二接入上的最后访问的跟踪区标识、或者第二接入的跟踪区标识列表。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,停止第二接入上正在进行的业务。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,启动第二接入的第一定时器,第一定时器用于触发终端设备释放N1 NAS信令连接;或者,释放N1 NAS信令连接。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,且第二接入上存在正在进行移动管理流程,停止移动管理流程。
示例性的,第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
在一种实施方式中,该通信装置还可以用于实现图5的实施例中核心网设备执行的方法,具体可以参阅前文的相关描述,这里不再重复赘述。该装置可以是核心网设备本身,也可以是核心网设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。其中,通信模块802,用于通过终端设备的第一接入向终端设备发送第一信息,第一信息指示核心网设备拒绝终端设备的请求的原因。处理模块801,用于根据第一信息以及终端设备的第二接入的信息确定是否删除第一接入的第一移动性管理参数;其中,第一接入和第二接入属于不同的接入类型。
可选的,第一信息不适用于第二接入;处理模块801,在根据第一信息以及第二接入的信息确定是否删除第一移动性管理参数时,具体用于:根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数。
处理模块801,在根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数时,可以具体用于:在第二接入的注册信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN。
处理模块801,在根据第一信息以及第二接入的注册信息确定是否删除第一移动性管理参数时,可以具体用于:第二接入的注册信息满足如下条件时确定不删除第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同。
可选的,第一信息适用于第二接入;处理模块801,在根据第一信息以及第二接入的信息确定是否删除第一移动性管理参数时,可以具体用于:根据第一信息、第二接入的注册信息以及第二接入上的业务信息确定是否删除第一移动性管理参数,第二接入上的业务 信息为第二接入上是否存在正在进行紧急业务的信息。
处理模块801,在根据第一信息、第二接入的注册信息以及第二接入上的业务信息处理第一移动性管理参数时,可以具体用于:在第二接入的注册信息以及第二接入上的业务信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN;或者,第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上没有正在进行的紧急业务。
处理模块801,在根据第一信息、第二接入的注册信息以及第二接入上的业务信息处理第一移动性管理参数时,可以具体用于:在第二接入的注册信息以及第二接入上的业务信息满足如下条件时确定不删除第一移动性管理参数:第二接入注册的PLMN与第一接入注册的PLMN相同,第二接入上存在正在进行紧急业务。
可选的,处理模块801,还用于在紧急业务结束之后确定删除第一移动性管理参数。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,删除第二移动性管理参数,第二移动性管理参数包括如下至少一项:在第二接入上的最后访问的跟踪区标识、或者第二接入的跟踪区标识列表。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,停止第二接入上正在进行的业务。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,释放N1 NAS信令连接。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,若第二接入上存在正在进行移动管理流程,停止移动管理流程。
示例性的,第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
在一种实施方式中,通信装置具体可以用于实现图7的实施例中终端设备执行的方法,该装置可以是终端设备本身,也可以是终端设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。其中,通信模块802,用于通过该终端设备的第一接入接收第一指示信息,第一指示信息指示是否删除第一接入的第一移动性管理参数;处理模块801,用于根据第一指示信息确定是否删除第一接入的第一移动性管理参数,第一接入和第二接入属于不同的接入类型。
处理模块801,在根据第一指示信息确定是否删除第一移动性管理参数时,可以具体用于:根据第一指示信息以及第二接入的信息确定是否删除第一移动性管理参数。
处理模块801,在根据第一指示信息以及第二接入的信息确定是否删除第一移动性管理参数时,可以具体用于:根据第一指示信息以及第二接入的注册信息确定是否删除第一移动性管理参数。
处理模块801,在根据第一指示信息以及第二接入的注册信息确定是否删除第一移动性管理参数时,可以具体用于:若第一指示信息指示删除第一移动性管理参数,在第二接入的注册信息满足如下条件之一时确定删除第一移动性管理参数:第二接入未注册到PLMN、或者第二接入注册的PLMN与第一接入注册的PLMN不同。
处理模块801,在根据第一指示信息以及第二接入的注册信息确定是否删除第一移动性管理参数时,可以具体用于:若第一指示信息指示删除第一移动性管理参数,且第二接入注册的PLMN与第一接入注册的PLMN相同,根据第二接入上的业务信息确定是否删 除第一移动性管理参数,第二接入上的业务信息为第二接入上是否正在进行紧急业务的信息。
处理模块801,在根据第二接入上的业务信息确定是否删除第一移动性管理参数时,可以具体用于:若第二接入上存在正在进行紧急业务,确定不删除第一移动性管理参数;或者,若第二接入上没有正在进行的紧急业务,确定删除第一移动性管理参数。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,在紧急业务结束后确定删除第一移动性管理参数。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,删除第二移动性管理参数,第二移动性管理参数包括如下至少一项:在第二接入上的最后访问的跟踪区标识、或者第二接入的跟踪区标识列表。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,停止第二接入上正在进行的业务。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,启动第二接入的第一定时器,其中,第一定时器用于触发终端设备释放N1 NAS信令连接;或者,释放N1NAS信令连接。
可选的,处理模块801,还用于:若确定删除第一移动性管理参数,若第二接入上存在正在进行移动管理流程,停止移动管理流程。
示例性的,第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
在一种实施方式中,该通信装置还可以用于实现图7的实施例中核心网设备执行的方法,具体可以参阅前文的相关描述,这里不再重复赘述。该装置可以是核心网设备本身,也可以是核心网设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。其中,处理模块801,用于确定第一指示信息。通信模块802,用于通过终端设备的第一接入向终端设备发送第一指示信息;第一指示信息指示是否删除第一接入的第一移动性管理参数,第一接入和第二接入属于不同的接入类型。
处理模块801,可以具体用于:根据第二指示信息以及第二接入的信息确定第一指示信息,第二指示信息指示核心网设备拒绝终端设备的请求的原因。
第二指示信息不适用于第二接入;处理模块801,可以具体用于:根据第二指示信息以及第二接入的注册信息确定第一指示信息。
处理模块801,可以具体用于:在第二接入的注册信息满足如下条件之一时第一指示信息指示删除第一移动性管理参数:第二接入未注册到PLMN;或者,核心网设备在第二接入的注册信息满足如下条件时第一指示信息指示不删除第一移动性管理参数:第二接入已注册到或者正在注册到PLMN。
第二指示信息适用于第二接入;处理模块801,可以具体用于:根据第二指示信息、第二接入的注册信息以及第二接入上的业务信息确定第一指示信息,第二接入上的业务信息为第二接入上是否正在进行紧急业务的信息。
处理模块801,可以具体用于:在第二接入的注册信息以及第二接入上的业务信息满足如下条件之一时第一指示信息指示删除第一移动性管理参数:第二接入未注册到PLMN;或者,第二接入已注册到或者正在注册到PLMN,第二接入上没有正在进行的紧急业务。
处理模块801,可以具体用于:在第二接入的注册信息以及第二接入上的业务信息满 足如下条件时第一指示信息指示不删除第一移动性管理参数:第二接入已注册到或者正在注册到PLMN,第二接入上存在正在进行紧急业务。
示例性的,第一移动性管理参数包括如下至少一项:密钥集标识、全球唯一临时用户设备标识,密钥集标识用于标识NAS安全上下文信息。
此外,通信装置还可以用于实现图6的实施例中通信设备(例如终端设备或者核心网设备)执行的方法,该装置可以是通信设备本身,也可以是通信设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。
本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,另外,在本申请各个实施例中的各功能模块可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。可以理解的是,本申请实施例中各个模块的功能或者实现可以进一步参考方法实施例的相关描述。
一种可能的方式中,通信装置可以如图9所示,该装置可以是通信设备或者通信设备中的芯片,其中该通信设备可以为上述实施例中的终端设备也可以是上述实施例中的网络设备。该装置包括处理器901和通信接口902,还可以包括存储器903。其中,处理模块801可以为处理器901。通信模块802可以为通信接口902。
处理器901,可以是一个CPU,或者为数字处理单元等等。通信接口902可以是收发器、也可以为接口电路如收发电路等、也可以为收发芯片等等。该装置还包括:存储器903,用于存储处理器901执行的程序。存储器903可以是非易失性存储器,比如硬盘(hard disk drive,HDD)或固态硬盘(solid-state drive,SSD)等,还可以是易失性存储器(volatile memory),例如随机存取存储器(random-access memory,RAM)。存储器903是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质,但不限于此。
处理器901用于执行存储器903存储的程序代码,具体用于执行上述处理模块801的动作,本申请在此不再赘述。通信接口902具体用于执行上述通信模块802的动作,本申请在此不再赘述。
本申请实施例中不限定上述通信接口902、处理器901以及存储器903之间的具体连接介质。本申请实施例在图9中以存储器903、处理器901以及通信接口902之间通过总线904连接,总线在图9中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示,图9中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
本申请实施例还提供了一种计算机可读存储介质,用于存储为执行上述处理器所需执行的计算机软件指令,其包含用于执行上述处理器所需执行的程序。
本申请实施例还提供一种通信系统,包括用于实现图4的实施例中终端设备功能的通信装置和用于实现图4的实施例中网络设备功能的通信装置。
本申请实施例还提供一种通信系统,包括用于实现图5的实施例中终端设备功能的通信装置和用于实现图5的实施例中网络设备功能的通信装置。
本申请实施例还提供一种通信系统,包括用于实现图6的实施例中终端设备功能的通信装置和用于实现图6的实施例中网络设备功能的通信装置。
本申请实施例还提供一种通信系统,包括用于实现图7的实施例中终端设备功能的通 信装置和用于实现图7的实施例中网络设备功能的通信装置。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (20)

  1. 一种通信方法,其特征在于,所述方法应用于终端设备,所述方法包括:
    所述终端设备通过第一接入注册到第一公共陆地移动网络PLMN;
    确定所述终端设备的第一接入从所述第一PLMN切换到第二PLMN;所述第二PLMN不是所述第一PLMN,也不是所述第一PLMN的等效PLMN;
    若所述终端设备在第二接入的状态为未在所述第一PLMN进行注册,或者未注册到所述第一PLMN上,确定删除第一移动性管理参数;
    其中,所述第一接入和所述第二接入属于不同的接入类型。
  2. 如权利要求1所述的方法,其特征在于,所述方法还包括:
    确定不删除所述第一移动性管理参数;
    若所述第二接入从所述第一PLMN切换到第三PLMN,确定删除所述第一移动性管理参数。
  3. 如权利要求1或2所述的方法,其特征在于,所述第一移动性管理参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,所述密钥集标识用于标识非接入层NAS安全上下文信息。
  4. 如权利要求3所述的方法,其特征在于,所述NAS安全上下文信息包括安全加密算法,所述安全加密算法为空加密算法。
  5. 一种通信方法,其特征在于,所述方法应用于终端设备,所述方法包括:
    通过所述终端设备的第一接入获取第一信息,所述第一信息指示核心网设备拒绝所述终端设备的请求的原因;
    根据所述第一信息以及所述终端设备的第二接入的信息确定是否删除第一参数;
    其中,所述第一接入和所述第二接入属于不同的接入类型。
  6. 如权利要求5所述的方法,其特征在于,所述第一信息不适用于所述第二接入;
    所述根据所述第一信息以及所述终端设备的第二接入的信息确定是否删除第一参数,包括:
    根据所述第一信息以及所述第二接入的注册信息确定是否删除所述第一参数。
  7. 如权利要求6所述的方法,其特征在于,所述根据所述第一信息以及所述第二接入的注册信息确定是否删除所述第一参数,包括:
    所述第二接入的注册信息满足如下条件之一时确定删除所述第一参数:所述第二接入未注册到公共陆地移动网络PLMN、或者所述第二接入注册的PLMN与所述第一接入注册的PLMN不同。
  8. 如权利要求6或7所述的方法,其特征在于,所述根据所述第一信息以及所述第二接入的注册信息确定是否删除所述第一参数,包括:
    所述第二接入的注册信息满足如下条件时确定不删除所述第一参数:所述第二接入注册的PLMN与所述第一接入注册的PLMN相同。
  9. 如权利要求5所述的方法,其特征在于,所述第一信息适用于所述第二接入;
    所述根据所述第一信息以及所述终端设备的第二接入的信息确定是否删除第一参数,包括:
    根据所述第一信息、所述第二接入的注册信息以及所述第二接入上的业务信息确定是 否删除所述第一参数,所述第二接入上的业务信息为所述第二接入上是否存在正在进行紧急业务的信息。
  10. 如权利要求9所述的方法,其特征在于,所述根据所述第一信息、所述第二接入的注册信息以及所述第二接入上的业务信息处理所述第一参数,包括:
    所述第二接入的注册信息以及所述第二接入上的业务信息满足如下条件之一时确定删除所述第一参数:
    所述第二接入未注册到PLMN;
    或者,所述第二接入注册的PLMN与所述第一接入注册的PLMN不同;
    或者,所述第二接入注册的PLMN与所述第一接入注册的PLMN相同,所述第二接入上没有正在进行的紧急业务。
  11. 如权利要求9或10所述的方法,其特征在于,所述根据所述第一信息、所述第二接入的注册信息以及所述第二接入上的业务信息确定是否删除所述第一参数,包括:
    所述第二接入的注册信息以及所述第二接入上的业务信息满足如下条件时确定不删除所述第一参数:所述第二接入注册的PLMN与所述第一接入注册的PLMN相同,所述第二接入上存在正在进行紧急业务。
  12. 如权利要求11所述的方法,其特征在于,所述方法还包括:
    在所述紧急业务结束之后确定删除所述第一参数。
  13. 如权利要求5-12任一项所述的方法,其特征在于,若确定删除所述第一参数,所述方法还包括:
    删除第二参数,所述第二参数包括如下至少一项:在所述第二接入上的最后访问的跟踪区标识、或者所述第二接入的跟踪区标识列表。
  14. 如权利要求5-13任一项所述的方法,其特征在于,若确定删除所述第一参数,所述方法还包括:
    停止所述第二接入上正在进行的业务。
  15. 如权利要求5-14任一项所述的方法,其特征在于,若确定删除所述第一参数,所述方法还包括:
    启动所述第二接入的第一定时器,所述第一定时器用于触发所述终端设备释放N1非接入层信令连接;或者,
    释放N1非接入层信令连接。
  16. 如权利要求5-15任一项所述的方法,其特征在于,若确定删除所述第一参数,所述方法还包括:
    若所述第二接入上存在正在进行移动管理流程,停止所述移动管理流程。
  17. 如权利要求5-16任一项所述的方法,其特征在于,所述第一参数包括如下至少一项:密钥集标识、或者全球唯一临时用户设备标识,所述密钥集标识用于标识安全上下文信息。
  18. 一种通信装置,其特征在于,包括用于执行如权利要求1至4中任一项所述方法的单元或模块,或者包括用于执行如权利要求5-17任一项所述方法的单元或模块。
  19. 一种通信装置,其特征在于,所述装置包括处理器和存储器,所述处理器与所述存储器耦合;
    所述存储器,用于存储程序或指令;
    所述处理器,用于调用所述程序或指令使所述通信装置执行如权利要求1-4中任一项所述的方法或者执行如权利要求5-17中任一项所述的方法。
  20. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质用于存储计算机指令,当所述计算机指令在计算机上运行时,使得所述计算机执行如权利要求1~17中任意一项所述的方法。
PCT/CN2023/088506 2022-05-05 2023-04-14 一种通信方法及装置 WO2023213181A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210479701.2A CN117062187A (zh) 2022-05-05 2022-05-05 一种通信方法及装置
CN202210479701.2 2022-05-05

Publications (1)

Publication Number Publication Date
WO2023213181A1 true WO2023213181A1 (zh) 2023-11-09

Family

ID=88646236

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/088506 WO2023213181A1 (zh) 2022-05-05 2023-04-14 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN117062187A (zh)
WO (1) WO2023213181A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200229206A1 (en) * 2017-12-30 2020-07-16 Intel Corporation Methods and devices for wireless communications
CN113556811A (zh) * 2016-05-13 2021-10-26 北京三星通信技术研究有限公司 一种轻连接控制的方法及设备
CN113785634A (zh) * 2019-03-11 2021-12-10 欧芬诺有限责任公司 通过无线网络进行无线设备寻呼
CN114270900A (zh) * 2019-08-19 2022-04-01 中兴通讯股份有限公司 通过接入和移动性管理功能重新分配进行注册的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113556811A (zh) * 2016-05-13 2021-10-26 北京三星通信技术研究有限公司 一种轻连接控制的方法及设备
US20200229206A1 (en) * 2017-12-30 2020-07-16 Intel Corporation Methods and devices for wireless communications
CN113785634A (zh) * 2019-03-11 2021-12-10 欧芬诺有限责任公司 通过无线网络进行无线设备寻呼
CN114270900A (zh) * 2019-08-19 2022-04-01 中兴通讯股份有限公司 通过接入和移动性管理功能重新分配进行注册的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G security; Handover interface for Lawful Interception (LI) (Release 12)", 3GPP DRAFT; 33108-CE0, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 11 June 2017 (2017-06-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051289814 *

Also Published As

Publication number Publication date
CN117062187A (zh) 2023-11-14

Similar Documents

Publication Publication Date Title
US11102828B2 (en) User plane function selection for isolated network slice
US11665668B2 (en) Offset of international mobile subscriber identity
US11729854B2 (en) Network assisted connection
US11963133B2 (en) Core paging handling
KR102601585B1 (ko) Nas 메시지의 보안 보호를 위한 시스템 및 방법
US20220353799A1 (en) Relay Node Selection
US20220248318A1 (en) Control of Network Slice
US20220264444A1 (en) Session Management for A Network Slice
US11317374B2 (en) RAN paging handling
US20230199632A1 (en) Access to Second Network
US20210385283A1 (en) Multimedia Priority Service
WO2021120744A1 (zh) 一种恢复ims业务的方法及装置
US20230189192A1 (en) Access to Second Network by Wireless Device
US20230164523A1 (en) Communication Method, Device, and System
US20230388863A1 (en) Communication method and apparatus
WO2023213181A1 (zh) 一种通信方法及装置
WO2023082858A1 (zh) 确定移动性管理策略的方法、通信装置及通信系统
RU2772709C1 (ru) Системы и способ защиты безопасности сообщений nas
CN114642079B (zh) 通信方法及装置
WO2023061207A1 (zh) 一种通信方法、通信装置及通信系统
WO2023246649A1 (zh) 通信方法、通信装置及通信系统
WO2021088060A1 (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: 23799168

Country of ref document: EP

Kind code of ref document: A1