WO2023124991A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2023124991A1
WO2023124991A1 PCT/CN2022/138829 CN2022138829W WO2023124991A1 WO 2023124991 A1 WO2023124991 A1 WO 2023124991A1 CN 2022138829 W CN2022138829 W CN 2022138829W WO 2023124991 A1 WO2023124991 A1 WO 2023124991A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
network
terminal device
core network
network device
Prior art date
Application number
PCT/CN2022/138829
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 WO2023124991A1 publication Critical patent/WO2023124991A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/14Mobility data transfer between corresponding nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data

Definitions

  • the embodiments of the present application relate to the field of wireless communication, and in particular, to a communication method and device.
  • EPS evolved packet system
  • AMF access and mobility management function
  • MME mobility management entity
  • the AMF of the visited network and the MME of the home network have not opened an interface, so the terminal equipment that does not support VONR cannot establish a voice transmission channel to 4G through the EPS fallback process. Therefore, voice services cannot be performed, and the user experience is poor.
  • the embodiments of the present application provide a communication method and device, which can avoid the problem that the terminal equipment cannot perform voice services after accessing the visited network because the terminal equipment does not support new air interface voice VoNR.
  • the present application provides a communication method, and the execution subject of the method may be a terminal device, or may be a chip applied in the terminal device.
  • the following description is made by taking the execution subject as a terminal device as an example.
  • the method includes: the terminal equipment sends the first information to the core network equipment of the home network. Wherein, the first information is used to indicate that the terminal device supports VoNR or inter-network roaming. Alternatively, the first information is used to request to obtain PLMN information of the visited network, and the operator of the visited network is different from the operator of the home network of the terminal device. Afterwards, the terminal device receives the PLMN information of the visited network from the core network device.
  • the core network device sends the PLMN information of the visited network to the terminal device only when it determines that the terminal device supports VoNR, or the terminal device requests to acquire the PLMN information of the visited network. Even if the operator of the visited network is different from the operator of the home network, the terminal equipment can still access the visited network and perform voice services through the visited network, avoiding the problem that the terminal equipment cannot perform voice services after accessing the visited network because the terminal equipment does not support VoNR.
  • the terminal device sends the first information to the core network device of the home network through an attach request message, so that the terminal device can send the first information to the core network device during the 4G registration process, and the core network device It can be learned that the terminal device supports VoNR, or the terminal device requests to obtain the PLMN information of the visited network, so as to prevent the core network device from sending the PLMN information of the visited network to the terminal device that does not support VoNR.
  • the terminal device sends the first information to the core network device of the home network through a registration request message, so that the terminal device can send the first information to the core network device during the 5G registration process, so that the core
  • the network device learns that the terminal device supports VoNR, or the terminal device requests to obtain the PLMN information of the visited network, so as to prevent the core network device from sending the PLMN information of the visited network to the terminal device that does not support VoNR.
  • the first information is carried in a field indicating network capabilities of the user equipment.
  • the first information is carried in preset bits, where the preset bits include fixed bits in a field indicating network capabilities of the user equipment, such as bits in a spare (Spare) state.
  • the preset bits include fixed bits in a field indicating network capabilities of the user equipment, such as bits in a spare (Spare) state.
  • the first information is carried in one of the following: the user equipment network capability field, or the user equipment network capability field of the N1 interface.
  • the first information is carried in one of the following: a mobility management capability field, or a user equipment network capability field of the S1 interface.
  • the terminal device sends the first information to the core network device of the home network through a security mode complete message.
  • the security mode completion message is a message protected by an encryption key, thereby reducing the possibility of the first information being tampered with or leaked, and improving the reliability of information transmission.
  • the terminal device sends the first information to the core network device of the home network through a tracking area update TAU request message, so that the terminal device can send the first information to the core network device during the TAU process, to Let the core network device know that the terminal device supports VoNR, or the terminal device requests to obtain the PLMN information of the visited network, so as to prevent the core network device from sending the PLMN information of the visited network to the terminal device that does not support VoNR.
  • the present application provides a communication method, and the execution subject of the method may be a core network device, or may be a chip applied to the core network device.
  • the following description will be made by taking the execution subject as an example of a core network device.
  • the method includes: a core network device receiving first information from a terminal device. Wherein, the first information is used to indicate that the terminal device supports VoNR or inter-network roaming. Alternatively, the first information is used to request to acquire PLMN information of the visited network, the operator of the visited network is different from the operator of the home network of the terminal device, and the core network device is the core network device of the home network of the terminal device. Afterwards, the core network device sends the PLMN information of the visited network to the terminal device according to the first information.
  • the core network device receives the first information from the terminal device through an attach request message.
  • the core network device receives the first information from the terminal device through a registration request message.
  • the first information is carried in a field indicating network capabilities of the user equipment.
  • the first information is carried in preset bits, and the preset bits include fixed bits in a field indicating network capabilities of the user equipment.
  • the first information is carried in one of the following: the user equipment network capability field, or the user equipment network capability field of the N1 interface.
  • the first information is carried in one of the following: a mobility management capability field, or a user equipment network capability field of the S1 interface.
  • the core network device receives the first information from the terminal device through a security mode completion message.
  • the core network device receives the first information from the terminal device through a tracking area update TAU request message.
  • the present application provides a communication method, and the execution subject of the method may be a core network device, or may be a chip applied in the core network device.
  • the following description will be made by taking the execution subject as an example of a core network device.
  • the method includes: the core network equipment determines that the terminal equipment supports new air interface voice VoNR, wherein the core network equipment is the core network equipment of the network to which the terminal equipment belongs. Afterwards, the core network device sends the PLMN information of the visited network to the terminal device, where the operator of the visited network is different from the operator of the home network of the terminal device.
  • the core network device sends the PLMN information of the visited network to the terminal device only when it is determined that the terminal device supports the VoNR function. Even if the operator of the visited network is different from the operator of the home network, the terminal equipment can still access the visited network and perform voice services through the visited network, avoiding the problem that the terminal equipment cannot perform voice services after accessing the visited network because the terminal equipment does not support VoNR.
  • the communication method in this embodiment of the present application further includes: the core network device receiving wireless capability information from the access network device.
  • the wireless capability information indicates the wireless capability of the terminal device.
  • the core network device determines that the terminal device supports VoNR, including: the core network device determines that the terminal device supports VoNR according to the wireless capability information.
  • the core network device can autonomously determine that the terminal device supports the VoNR function based on the wireless capability information.
  • the communication method in this embodiment of the present application further includes: when the core network device does not save the wireless capability information, the core network device sends an initial context establishment request to the access network device, wherein the initial context establishment request does not carry The wireless capability information, so that the access network equipment provides the wireless capability information to the core network equipment.
  • the communication method in the embodiment of the present application further includes: the core network device receives indication information from the access network device, where the indication information indicates that the terminal device supports VoNR.
  • the core network device determining that the terminal device supports VoNR includes: the core network device determines that the terminal device supports VoNR according to the indication information.
  • the access network device determines that the terminal device supports the VoNR function, and then notifies the core network device, so that the core network device learns that the terminal device supports the VoNR function.
  • the core network device receives the indication information from the access network device through a wireless capability matching response message. That is to say, the wireless capability matching response message carries the above indication information, so that the core network equipment acquires the above indication information.
  • the communication method in the embodiment of the present application further includes: the core network device sending a first request message to the access network device.
  • the first request message requests to obtain the indication information, so that the access network device provides the indication information to the core network device in response to the first request message.
  • the core network device sends the first request message to the access network device through a terminal device capability information indication message. That is to say, the capability information indication message carries the first request message, so as to send the indication information to the access network device.
  • the core network device sends the PLMN information of the visited network to the terminal device through the registration acceptance message, so that the terminal device can obtain the PLMN information of the visited network through the registration process, effectively preventing the terminal device that does not support VoNR from receiving the PLMN information of the visited network.
  • PLMN information of the visited network is a possible design.
  • the core network equipment includes a mobility management entity MME, or a mobility management function AMF network element.
  • the present application provides a communication device, which may be a terminal device in any possible design of the above-mentioned first aspect or the first aspect, or a chip that realizes the functions of the above-mentioned terminal device; the communication device includes To realize the corresponding modules, units, or means (means) of the above method, the modules, units, or means can be implemented by hardware, software, or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a processing unit, a sending unit and a receiving unit.
  • the processing unit is used to control the sending unit to send the first information to the core network equipment of the home network, wherein the first information is used to indicate that the communication device supports Voice over New Air Interface (VoNR) or inter-network roaming, or the first information is used to request to obtain
  • VoIPNR Voice over New Air Interface
  • the processing unit is further configured to control the receiving unit to receive the PLMN information of the visited network from the core network device.
  • the sending unit is specifically configured to send the first information to the core network device of the home network through an attach request message.
  • the sending unit is specifically configured to send the first information to the core network device of the home network through a registration request message.
  • the first information is carried in a field indicating network capabilities of the user equipment.
  • the first information is carried in preset bits, where the preset bits include fixed bits in a field indicating network capabilities of the user equipment.
  • the first information is carried in one of the following: the user equipment network capability field, or the user equipment network capability field of the N1 interface.
  • the first information is carried in one of the following: a mobility management capability field, or a user equipment network capability field of the S1 interface.
  • the sending unit is specifically configured to send the first information to the core network device of the home network through a security mode completion message.
  • the sending unit is specifically configured to send the first information to the core network device of the home network through a tracking area update TAU request message.
  • the present application provides a communication device, which may be the core network device in any possible design of the above-mentioned second aspect or the second aspect, or a chip that realizes the functions of the above-mentioned core network device; the communication
  • the device includes corresponding modules, units, or means (means) for realizing the above methods, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software on hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a processing unit, a sending unit and a receiving unit.
  • the processing unit is used to control the receiving unit to receive the first information from the terminal device, wherein the first information is used to indicate that the terminal device supports Voice over New Air Interface (VoNR) or inter-network roaming, or the first information is used to request to obtain the information of the visited network.
  • VoIP Voice over New Air Interface
  • the operator of the visited network is different from the operator of the home network of the terminal equipment, and the communication device is the core network equipment of the home network of the terminal equipment.
  • the processing unit is further configured to control the sending unit to send the PLMN information of the visited network to the terminal device according to the first information.
  • the receiving unit is specifically configured to receive the first information from the terminal device through an attach request message.
  • the receiving unit is specifically configured to receive the first information from the terminal device through a registration request message.
  • the first information is carried in a field indicating network capabilities of the user equipment.
  • the first information is carried in preset bits, and the preset bits include fixed bits in a field indicating network capabilities of the user equipment.
  • the first information is carried in one of the following: the user equipment network capability field, or the user equipment network capability field of the N1 interface.
  • the first information is carried in one of the following: a mobility management capability field, or a user equipment network capability field of the S1 interface.
  • the receiving unit is specifically configured to receive the first information from the terminal device through a security mode completion message.
  • the receiving unit is specifically configured to receive the first information from the terminal device through a tracking area update TAU request message.
  • the present application provides a communication device, which may be the core network device in any possible design of the above-mentioned third aspect or the third aspect, or a chip that realizes the functions of the above-mentioned core network device; the communication
  • the device includes corresponding modules, units, or means (means) for realizing the above methods, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software on hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a processing unit, a sending unit and a receiving unit.
  • the processing unit is configured to determine that the terminal equipment supports VoNR, wherein the communication device is a core network equipment of the home network of the terminal equipment.
  • the sending unit is configured to send the PLMN information of the visited network to the terminal device, where the operator of the visited network is different from the operator of the home network of the terminal device.
  • the receiving unit is further configured to receive wireless capability information from the access network device, where the wireless capability information indicates the wireless capability of the terminal device.
  • the processing unit is configured to determine that the terminal device supports VoNR, including: determining that the terminal device supports VoNR according to the wireless capability information.
  • the sending unit is further configured to send an initial context establishment request to the access network device when the communication device does not save the wireless capability information, where the initial context establishment request does not carry the wireless capability information.
  • the receiving unit is further configured to receive indication information from the access network device, where the indication information indicates that the terminal device supports VoNR.
  • the processing unit is configured to determine that the terminal device supports VoNR, including: determining that the terminal device supports VoNR according to the indication information.
  • the receiving unit is specifically configured to receive the indication information from the access network device through a wireless capability matching response message.
  • the sending unit is further configured to send a first request message to the access network device, where the first request message requests acquisition of indication information.
  • the sending unit is specifically configured to send the first request message to the access network device through a terminal device capability information indication message.
  • the sending unit is specifically configured to send the PLMN information of the visited network to the terminal device through a registration acceptance message.
  • the communication device includes a mobility management entity MME, or a mobility management function AMF network element.
  • the embodiment of the present application provides a communication device, including: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device performs any of the above aspects or any On the one hand, a method executed by a terminal device in any possible design.
  • the communication device may be the terminal device in the first aspect or any possible design of the first aspect, or a chip that implements the functions of the terminal device.
  • the embodiment of the present application provides a communication device, including: a processor; the processor is coupled to a memory, and is used to read and execute instructions in the memory, so that the communication device performs any of the above aspects Or a method executed by a terminal device in any possible design of any aspect.
  • the communication device may be the terminal device in the first aspect or any possible design of the first aspect, or a chip that implements the functions of the terminal device.
  • the embodiment of the present application provides a chip, including a processing circuit and an input/output interface.
  • the input-output interface is used to communicate with modules other than the chip, for example, the chip may be a chip that realizes the function of the terminal device in the above-mentioned first aspect or any possible design of the first aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above first aspect or any possible design of the first aspect.
  • the embodiment of the present application provides a communication device, including: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device performs any of the above aspects or any
  • any possible design is a method executed by a core network device.
  • the communication device may be the core network equipment in the above-mentioned second aspect or any possible design of the second aspect, or the communication device may be the core network device in the above-mentioned third aspect or any possible design of the third aspect equipment, or a chip that implements the functions of the above-mentioned core network equipment.
  • the embodiment of the present application provides a communication device, including: a processor; the processor is coupled with a memory, and is used to read and execute instructions in the memory, so that the communication device performs any of the above-mentioned A method executed by a core network device in any possible design of any aspect or any aspect.
  • the communication device may be the core network equipment in the above-mentioned second aspect or any possible design of the second aspect, or the communication device may be the core network device in the above-mentioned third aspect or any possible design of the third aspect equipment, or a chip that implements the functions of the above-mentioned core network equipment.
  • the embodiment of the present application provides a chip, including a processing circuit and an input/output interface.
  • the input and output interface is used to communicate with modules other than the chip, for example, the chip may be a chip that implements the core network device function in the second aspect or any possible design of the second aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above second aspect or any possible design of the second aspect.
  • the chip may be a chip that realizes the function of the core network device in the third aspect or any possible design of the third aspect.
  • the processing circuit is used to run computer programs or instructions to implement the method in the above third aspect or any possible design of the third aspect.
  • the embodiment of the present application provides a computer-readable storage medium, which stores instructions, and when it is run on a computer, the computer can execute any one of the above-mentioned aspects. method.
  • the embodiment of the present application provides a computer program product containing instructions, which when run on a computer, enables the computer to execute the method in any one of the above aspects.
  • an embodiment of the present application provides a circuit system, the circuit system includes a processing circuit configured to execute the method in any one of the above aspects.
  • the embodiment of the present application provides a communication system, where the communication system includes core network equipment and access network equipment.
  • the access network device is configured to send the first information to the core network device, where the first information indicates the wireless capability of the terminal device, or the first information indicates that the terminal device supports VoNR.
  • the core network device is configured to receive the first information from the access network device, where the core network device is a core network device of a network to which the terminal device belongs.
  • the core network device is further configured to determine, according to the first information, that the terminal device supports VoNR.
  • the core network device is further configured to send the PLMN information of the visited network to the terminal device, where the operator of the visited network is different from the operator of the home network of the terminal device.
  • FIG. 1 is a schematic structural diagram of a communication system applied in an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of another communication system applied in an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of another communication system applied in an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of another communication system applied in an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of another communication system applied in an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • Fig. 7a is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 7b is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 7c is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • Fig. 7d is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 10a is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 10b is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 10c is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • Fig. 12a is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • Fig. 12b is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • Fig. 12c is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a communication system provided by an embodiment of the present application. As shown in Figure 1, the communication system includes terminal equipment, access network equipment and a core network.
  • terminal equipment includes equipment that provides voice and/or data connectivity to users, specifically, equipment that provides voice to users, or equipment that provides data connectivity to users, or equipment that provides voice and data connectivity to users sexual equipment.
  • Examples may include a handheld device with wireless connectivity, or a processing device connected to a wireless modem.
  • the terminal device can communicate with the core network via a radio access network (radio access network, RAN), exchange voice or data with the RAN, or exchange voice and data with the RAN.
  • radio access network radio access network
  • the terminal equipment may include user equipment (user equipment, UE), wireless terminal equipment, mobile terminal equipment, device-to-device communication (device-to-device, D2D) terminal equipment, vehicle to everything (vehicle to everything, V2X) terminal equipment , machine-to-machine/machine-type communications (machine-to-machine/machine-type communications, M2M/MTC) terminal equipment, Internet of things (internet of things, IoT) terminal equipment, subscriber unit, subscriber station station), mobile station (mobile station), remote station (remote station), access point (access point, AP), remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user Agent (user agent), or user equipment (user device), etc.
  • IoT Internet of things
  • it may include mobile phones (or “cellular” phones), computers with mobile terminal equipment, portable, pocket, hand-held, computer built-in mobile devices, and the like.
  • personal communication service personal communication service, PCS
  • PCS personal communication service
  • cordless telephone session initiation protocol (session initiation protocol, SIP) telephone
  • wireless local loop wireless local loop
  • WLL wireless local loop
  • PDA personal digital assistant
  • constrained devices such as devices with low power consumption, or devices with limited storage capabilities, or devices with limited computing capabilities, etc.
  • it includes barcodes, radio frequency identification (radio frequency identification, RFID), sensors, global positioning system (global positioning system, GPS), laser scanners and other information sensing devices.
  • the various terminal devices described above if they are located on the vehicle (for example, placed in the vehicle or installed in the vehicle), can be considered as vehicle-mounted terminal devices. ).
  • the terminal device may further include a relay (relay).
  • a relay relay
  • all devices capable of performing data communication with the base station can be regarded as terminal devices.
  • the device for realizing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to realize the function, such as a chip system, and the device may be installed in the terminal device.
  • the system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • the terminal equipment is used as an example for implementing terminal functions, and the introduction is made.
  • the access network device may be an access point for wireless communication or wired communication, such as a base station or a base station controller, a wireless-fidelity (wireless-fidelity, wifi) access point or wifi controller, or an access point for fixed network access wait.
  • the base station may include various types of base stations, such as micro base stations (also called small stations), macro base stations, relay stations, access points, etc., which are not specifically limited in this embodiment of the present application.
  • the base station may be a global system for mobile communication (GSM), a base station (base transceiver station, BTS) in code division multiple access (code division multiple access, CDMA), broadband Base station (node B) in code division multiple access (wideband code division multiple access, WCDMA), evolved base station (evolutional node B, eNB or e-NodeB) in long term evolution (long term evolution, LTE), Internet of things ( Internet of things (IoT) or eNB in narrowband-internet of things (NB-IoT), the fifth generation (the fifth generation, 5G) mobile communication network or the future evolution of public land mobile network (public land) A base station in a mobile network (PLMN), which is not limited in this embodiment of the present application.
  • GSM global system for mobile communication
  • BTS base station
  • CDMA code division multiple access
  • node B in code division multiple access
  • WCDMA wideband code division multiple access
  • evolutional node B, eNB or e-NodeB in long
  • the core network includes various core network devices.
  • the core network device may include a mobility management entity (mobility management entity, MME), for details, refer to the introduction in FIG. 2 .
  • the core network equipment may also include an access and mobility management function (core access and mobility management function, AMF) network element, for details, refer to the introduction in FIG. 3 .
  • AMF access and mobility management function
  • the core network equipment may also include other network elements, such as user plane function (user plane function, UPF) network elements, session management function (session management function, SMF) network elements, etc., which will not be repeated here.
  • FIG. 2 shows a schematic structural diagram of a fourth generation (the fourth generation, 4G) communication system.
  • the 4G communication system includes evolved universal mobile telecommunications system (universal mobile telecommunications system, UMTS) terrestrial radio access network (evolved UMTS territorial radio access network, E-UTRAN) equipment, MME, serving gateway (serving gateway, SGW), packet Data network (packet data network, PDN) gateway (PDN gateway, PGW), policy and charging rules function (policy and charging rules function, PCRF) network elements and home subscriber server (home subscriber server, HSS) and other network elements or equipment.
  • UMTS universal mobile telecommunications system
  • E-UTRAN evolved Universal Mobile telecommunications system
  • MME serving gateway
  • SGW packet Data network
  • PDN gateway packet Data network gateway
  • PGW policy and charging rules function
  • PCRF policy and charging rules function
  • home subscriber server home subscriber server
  • HSS home subscriber server
  • terminal equipment accesses E-UTRAN equipment through LTE-Uu
  • E-UTRAN equipment communicates with MME through S1-MME
  • E-UTRAN equipment communicates with SGW through S1-U
  • different MMEs communicate through S10
  • the MME communicates with the HSS through S6a
  • the MME communicates with the SGW through S11
  • the PGW communicates with the PCRF network element through Gx
  • the PCRF network element communicates with the server through Rx
  • the SGW communicates with the PGW through S5
  • the PGW accesses the server through the SGi.
  • the E-UTRAN equipment is used to implement functions related to the evolved network radio.
  • the MME is responsible for the mobility management of the control plane, including user context and mobility state management, and allocation of temporary user identities.
  • the SGW is the user plane anchor point between the 3rd generation partnership project (3GPP) access networks, and is the interface for terminating E-TURAN.
  • the PGW is the anchor point of the user plane between the 3GPP access network and the non-3GPP access network, and is the interface between the termination and the external PDN.
  • the PCRF network element is used for policy control decision and flow charging control function.
  • the HSS is used to store user subscription information.
  • the server is used to provide internet protocol (internet protocol, IP) services, such as voice/video services based on internet protocol multimedia subsystem (internet protocol multimedia subsystem, IMS), packet switched streaming service (packet switched streaming service, PSS), etc.
  • IP internet protocol
  • IMS internet protocol multimedia subsystem
  • PSS packet switched streaming service
  • FIG. 3 shows a schematic structural diagram of a fifth generation (the fifth generation, 5G) communication system.
  • the 5G communication system includes radio access network (radio access network, RAN) equipment, UPF network elements, AMF network elements, SMF network elements, authentication server function (authentication server function, AUSF) network elements, network slice selection function (network slice selection function) selection function (NSSF) network element, network exposure function (network exposure function, NEF) network element, network function storage function (network exposure function repository function, NRF) network element, policy control function (policy control function, PCF) network element, Unified data management (UDM) network elements, unified data storage (unified data repository, UDR) network elements, application function (application function, AF) network elements or charging function (charging function, CHF) network elements, etc.
  • radio access network radio access network
  • UPF radio access network
  • AMF authentication server function
  • AUSF authentication server function
  • NEF network exposure function
  • NRF network exposure function repository function
  • PCF policy control function
  • FIG. 3 is only an example of some examples of network elements or entities in the 5G communication system, and the 5G communication system may also include some diagrams such as network data analysis function (network data analytics function, NWDAF) network elements, etc. 3 Network elements or entities not shown in the figure, which are not specifically limited in this embodiment of the present application.
  • NWDAF network data analytics function
  • the terminal device accesses the 5G network through the RAN device, and the terminal device communicates with the AMF through the N1 interface (N1 for short); the RAN device communicates with the AMF network element through the N2 interface (N2 for short); the RAN device communicates with the AMF network element through the N3 interface
  • the interface (N3 for short) communicates with the UPF network element; the SMF network element communicates with the UPF network element through the N4 interface (N4 for short), and the UPF network element accesses the data network (data network, DN) through the N6 interface (N6 for short).
  • N1, N2, N3, N4 and N6 respectively represent reference points (reference points) between relevant network elements/network functions.
  • AUSF network element AMF network element, SMF network element, NSSF network element, NEF network element, NRF network element, PCF network element, UDM network element, UDR network element, CHF network element or AF network element shown in Figure 3
  • Other control plane functions use service-oriented interfaces to interact.
  • the service interface provided by the AUSF network element is Nausf; the service interface provided by the AMF network element is Namf; the service interface provided by the SMF network element is Nsmf; the service interface provided by the NSSF network element is Nnssf;
  • the service interface provided by NEF network elements is Nnef; the service interface provided by NRF network elements is Nnrf; the service interface provided by PCF network elements is Npcf; the service interface provided by UDM network elements is Nudm;
  • the service interface provided by the element is Nudr; the service interface provided by the CHF network element is Nchf; the service interface provided by the AF network element is Naf.
  • the relevant function description and interface description can refer to the 5G system architecture (5G system architecture) diagram in the 23501 standard, and will not be repeated here.
  • an AMF network element may also be called an AMF or an AMF entity, which will be described uniformly here and will not be described in detail below.
  • the core network device may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • the above functional modules may be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (eg, cloud platform).
  • the visiting network party refers to the operator that provides inter-network roaming services to the terminal equipment of other operators within the roaming area.
  • a network that provides inter-network roaming services to terminal devices of other operators is described as a visited network (visited network).
  • the inter-network roaming service may be a 5G core network inter-network roaming service.
  • the home network party refers to the operator that provides the roaming service across different networks to the terminal equipment of this network through the network of other operators in the roaming area.
  • the network that provides inter-network roaming services to terminal devices on this network through other operator networks is described as a home network (home network).
  • the inter-network roaming service may be a 5G core network inter-network roaming service.
  • Inter-network roaming means that a terminal device can use services provided by a home network by accessing a visited network.
  • the operator of the visited network is different from the operator of the home network of the terminal device, but they belong to the same country.
  • inter-network roaming may also be referred to as national roaming (national roaming). In this embodiment of the present application, only inter-network roaming is taken as an example for introduction.
  • the access network and core network of both operators in inter-network roaming are independently constructed and managed, and mobile users are independently managed.
  • the two operators that provide the inter-network roaming service provide corresponding services for roaming terminal devices based on the inter-network roaming agreement.
  • Cross-network roaming is implemented by home routing, that is, roaming user data returns to the home network, and services are provided by the home network to terminal equipment.
  • the terminal device cannot access the home network in the roaming area, but uses 5G services by accessing the visited network, such as data services, IMS-based voice/video services, and short message services wait.
  • inter-network roaming can also be described as 5G core network inter-network roaming, or 5G core network roaming.
  • 5G core network inter-network roaming is used as an example for introduction.
  • the terminal device enters the roaming area, accesses the visited network, connects to the home network through the roaming interworking interface, and then the home network provides services.
  • the visited network may be the 5G network of the visited operator
  • the home network may be the 5G network of the home operator.
  • the visited network and the home network are connected through a boarder gateway (BG).
  • BG boarder gateway
  • the network elements in the visited network and the network elements in the home network are connected, as shown in FIG. 5 .
  • the visiting operator's 4G network does not provide 5G core network inter-network roaming services, and does not support voice fallback to the visiting operator's 4G network.
  • the terminal device connects to the home network when it leaves the roaming area and searches for a signal of the home network.
  • the terminal device is configured with a subscriber identity module (subscriber identity module, SIM) card.
  • SIM subscriber identity module
  • the SIM card can be used as the identification of the network identity of the mobile user.
  • the SIM card is used to store user data and complete user identity authentication.
  • One SIM card corresponds to one mobile user.
  • the SIM card can store user identifiers.
  • the subscriber identifier may be: an international mobile subscriber identification number (IMSI) or a subscription permanent identifier (SUPI).
  • IMSI international mobile subscriber identification number
  • SUPI subscription permanent identifier
  • a SIM card can be implemented in the form of a physical card, such as a standard SIM card, Mini-SIM card, Micro SIM card, and Nano SIM card. This type of SIM card can also be called a universal subscriber identity module (USIM) card.
  • the SIM card can also be implemented in the form of a built-in chip, such as an embedded-SIM (eSIM) card.
  • eSIM embedded-SIM
  • the SIM card stores an identifier (identity, ID) of the home operator PLMN.
  • ID identifier
  • the terminal device When the terminal device is turned on, it preferentially selects the PLMN of the home operator to reside and execute services.
  • the terminal device receives the system broadcast message of the access network device.
  • the system broadcast message includes the PLMN ID.
  • the terminal device selects a network, it determines the operator by analyzing the PLMN ID in the system broadcast message, and preferentially selects the PLMN belonging to the operator to reside on.
  • the terminal equipment After the terminal equipment resides in the home operator's PLMN, it sends a registration (attach or registration) request message to the home operator's core network equipment, and then the core network equipment sends an equivalent public land mobile network (equivalent public land mobile network) request message to the terminal equipment.
  • network, EPLMN network
  • the EPLMN information includes one or more PLMN IDs.
  • the PLMN ID in the EPLMN information may be the PLMN ID of the operator of the visited network party.
  • the terminal device stores the received EPLMN information, and treats the PLMN contained in the EPLMN information and the PLMN of the home operator in the subsequent network selection, that is, it is considered to have the same network selection priority.
  • the terminal device moves to the coverage area of the visited network
  • the PLMN ID of the operator of the visited network party is obtained by analyzing the system broadcast message of the access network device.
  • the terminal device determines that it is the same as the PLMN ID obtained in the registration acceptance message, the terminal device camps on the base station of the operator of the visited network party, and initiates a registration request to the core network device of the operator of the visited network party, thereby receiving access the network.
  • terminal devices there are two ways for terminal devices to perform voice services in the 5G independent networking mode:
  • VoNR refers to establishing a voice transmission channel in the NR network to realize the VoNR function.
  • Method 2 cannot establish a voice transmission channel through the NR network, and the terminal device needs to fall back to the 4G network, and establish a voice transmission channel through the 4G network to perform voice services.
  • the AMF network element of the 5G core network needs to open an interface with the MME network element of the 4G core network.
  • both the method 1 and the method 2 implement the voice service based on the IMS.
  • the operator's network does not support VoNR.
  • the released terminal equipment supporting 5G SA does not support the VoNR function, and performs voice services through the EPS fallback function.
  • the interface between the AMF network element is opened between the visited network and the home network, but the connection between the AMF network element on the visited network side and the MME network element on the home network side is not opened. Interface. Therefore, terminal devices cannot perform voice services through EPS fallback, resulting in users being unable to answer incoming calls and affecting user experience.
  • the embodiment of the present application provides two communication methods, and the communication method (such as the first communication method or the second communication method) of the embodiment of the present application can be applied to the communication system shown in FIG. 1 to FIG. 5 .
  • the terminal device sends the first information to the core network device of the home network.
  • the first information is used to indicate that the terminal device supports VoNR or inter-network roaming.
  • the first information is used to request to obtain PLMN information of the visited network, and the operator of the visited network is different from the operator of the home network of the terminal device.
  • the terminal device receives the PLMN information of the visited network from the core network device.
  • the core network device sends the PLMN information of the visited network to the terminal device only when it determines that the terminal device supports VoNR, or the terminal device requests to acquire the PLMN information of the visited network.
  • the terminal equipment can still access the visited network and perform voice services through the visited network, avoiding the problem that the terminal equipment cannot perform voice services after accessing the visited network because the terminal equipment does not support VoNR.
  • the first communication method 600 provided in the embodiment of the present application includes the following steps:
  • the terminal device sends first information to the core network device of the home network.
  • the core network device of the home network receives the first information from the terminal device.
  • the core network device may be the MME shown in FIG. 2 , or the AMF shown in FIG. 3 . It should be understood that with the evolution of communication technologies, core network devices may also have other names, which are not limited in this embodiment of the present application.
  • the first information has two possible implementation modes (namely the following modes 1 and 2), which are specifically introduced as follows:
  • the first information is used to indicate that the terminal device supports VoNR or inter-network roaming.
  • VoNR and inter-network roaming can refer to the glossary of terms, and will not be repeated here.
  • the terminal device if the terminal device supports inter-network roaming, the terminal device also supports the VoNR function. Since a terminal device that does not support VoNR cannot perform voice services in the visited network, this type of terminal device cannot reside in the visited network, but can only reside in the home network. We can consider that this type of terminal device does not support roaming across networks; otherwise Only the terminal devices that support VoNR can reside in the visited network and perform voice services through VoNR. We can consider that this type of terminal supports roaming across networks. Therefore, support for inter-network roaming and support for VoNR can be regarded as equivalent.
  • the first information may be in a direct indication manner, indicating that the terminal device supports VoNR or inter-network roaming.
  • the first information may also use an indirect indication to indicate that the terminal device supports VoNR or inter-network roaming.
  • Table 1a shows a possible mapping relationship.
  • support for inter-network roaming corresponds to A1
  • support for VoNR corresponds to A2.
  • the first information includes A1, it can be understood that the first information is used to indicate that the terminal device supports inter-network roaming. If the first information includes A2, it can be understood that the first information is used to indicate that the terminal device supports VoNR.
  • the first information may also be indicated in other forms, which is not limited in this embodiment of the present application.
  • the above only takes the terminal equipment supporting VoNR or inter-network roaming as an example for introduction.
  • the first information may also indicate accordingly.
  • the terminal device does not support inter-network roaming
  • the first information indicates that the terminal device does not support inter-network roaming.
  • the terminal device does not support VoNR
  • the first information indicates that the terminal device does not support VoNR.
  • the first information may be in a direct indication manner, indicating that the terminal device does not support VoNR or does not support inter-network roaming.
  • the first information may also use an indirect indication to indicate that the terminal device does not support VoNR or does not support inter-network roaming. Exemplarily, taking Table 1b as an example, Table 1b shows a possible mapping relationship.
  • B1 does not support inter-network roaming
  • B2 does not support VoNR.
  • the first information includes B1
  • it can be understood that the first information is used to indicate that the terminal device does not support inter-network roaming.
  • the first information includes B2, it can be understood that the first information is used to indicate that the terminal device does not support VoNR.
  • the first information is used to request to obtain the PLMN information of the visited network.
  • the operator of the visited network is different from the operator of the home network of the terminal device.
  • the PLMN information includes a PLMN ID.
  • the first information may directly indicate a request to obtain the PLMN information of the visited network, or indirectly indicate a request to obtain the PLMN information of the visited network, for example, the first information is indicated by 1 bit.
  • the value of this bit is 1, indicating that it is requested to obtain the PLMN information of the visited network.
  • the value of this bit is 0, indicating that it is not necessary to obtain the PLMN information of the visited network.
  • the value of this bit is 0, indicating that it is requested to acquire the PLMN information of the visited network.
  • the value of this bit is 1, indicating that there is no need to obtain the PLMN information of the visited network.
  • the first information when the first information is sent, it indicates a request to acquire PLMN information of the visited network. If the first information is not sent, it means that the PLMN information of the visited network does not need to be obtained, which is not limited in this embodiment of the present application.
  • the terminal device involved in the embodiment of the present application sends the first information to the core network device, which means that the terminal device sends the first information to the access network device, and the access network device then sends the first information to the As for the core network device, since the access network device plays the role of transparent transmission in this step, for the sake of brevity of description, it is directly described as terminal device sending the first information to the core network device in the embodiment of the present application and the accompanying drawings.
  • S601 can be implemented as S601a:
  • the terminal device sends the first information to the MME of the home network through an attach request (attach request) message.
  • the MME of the home network receives the first information from the terminal device through an attach request message.
  • the attach request message carries the first information.
  • the terminal device can send the first information to the MME during the 4G registration process, so that the MME can know that the terminal device supports VoNR, or the terminal device requests to obtain the PLMN information of the visited network, so as to prevent the MME from sending a call to a terminal device that does not support VoNR.
  • Network PLMN information may be used to obtain the PLMN information of the visited network.
  • the first information may be carried in a field indicating the network capability of the user equipment in the attach request message.
  • the first information may be carried in the field indicating the 4G network capability of the user equipment, such as the field of the user equipment network capability (UE network capability), and may also be carried in the field indicating the 5G network capability of the user equipment, such as the user network capability of the N1 interface.
  • the N1 interface is an interface for performing communication connection between the terminal device and the AMF network element.
  • the first information may also be carried in other fields in the attach request message, which is not limited in this embodiment of the present application.
  • the field indicating the network capability of the user equipment may carry the first information through a certain number of preset bits.
  • the preset bits may include fixed bits in the field indicating the network capability of the user equipment, such as bits in a spare (spare) state.
  • byte 1 indicates an information element identifier (information element identifier, IEI), that is, UE network capability IEI.
  • IEI information element identifier
  • Byte 2 indicates the length of UE network capability contents (length of UE network capability contents).
  • Byte 3 carries the information of the universal mobile telecommunications system (evolved packet system, EPS) encryption algorithm, byte 4 carries the information of the EPS integrity algorithm, and byte 5 carries the information of the universal mobile telecommunications system (universal mobile telecommunications system, UMTS) encryption algorithm Information, byte 6 carries UMTS integrity algorithm information and universal multiple-octet coded character set (universal multiple-octet coded character set, UCS) information.
  • IEI information element identifier
  • UCS universal multiple-octet coded character set
  • Byte 7 to Byte 10 (eg, Bit 1 to Bit 5 of Byte 10), information of Property 1 to Property 29 may be included. Wherein, for characteristics 1 to 29, reference may be made to the introduction in related technologies, and details are not repeated here.
  • byte 10 eg, bit 6, bit 7, and bit 8 of byte 10
  • bits in a spare state are included.
  • the fixed bit bits include at least one of the following bits: some bits in byte 10 (such as bit 6, bit 7 and bit 8 in byte 10), byte 11, byte 12, All bits in byte 13, byte 14, and byte 15.
  • Table 3 shows a possible N1 UE network capability field.
  • the bits that can carry the first information in the N1 UE network capability field are shown as circles.
  • bit 1 indicates the IEI, that is, N1 UE network capability IEI.
  • Byte 2 indicates the length of N1 UE network capability contents (length of N1 UE network capability contents).
  • bit 1 to bit 6 of byte 3 information of characteristic 1 to characteristic 5 may be included. Wherein, for characteristics 1 to 5, reference may be made to the introduction in related technologies, and details are not repeated here.
  • bit 3 eg, bit 7 and bit 8 of byte 3
  • bits in a spare state are included.
  • the fixed bits include at least one of the following bits: some bits in byte 3 (such as bits 7 and 8 in byte 3), and all bits in byte 4.
  • S601 can be implemented as S601b:
  • the terminal device sends the first information to the MME of the home network through a tracking area update (tracking area update, TAU) request message.
  • the MME of the home network receives the first information from the terminal device through a TAU request message.
  • the TAU request message carries the first information.
  • the terminal device can send the first information to the MME during the TAU process, so that the MME can know that the terminal device supports VoNR, or the terminal device requests to obtain the PLMN information of the visited network, so as to prevent the MME from sending a visit to a terminal device that does not support VoNR.
  • Network PLMN information may be used to obtain the PLMN information of the visited network.
  • the mobile network uses a tracking area (tracking area, TA) to determine the location of the terminal equipment, so as to perform location management and paging on the terminal equipment.
  • the core network device configures a tracking area list (tracking area list, TA list) for the terminal device.
  • a TA list includes one or more tracking area codes (tracking area code, TAC), and a TAC is used to identify a TA.
  • TAC tracking area code
  • a TA can contain one or more cells. Subsequently, if the terminal device moves within the cell indicated by the configured TA list, TAU does not need to be executed.
  • the core network device when the terminal device has services arriving, the core network device will page the terminal device in the area corresponding to the configured TA list. Conversely, if the terminal device moves out of the cell indicated by the TA list, the core network device does not know the latest location of the terminal device. The terminal device needs to execute TAU and send a TAU request message to the core network device, so that the core network device knows the current location of the terminal device. TA, and then the core network device can update the TA list of the terminal device.
  • the first information may be carried in a spare field or other fields in the TAU request message, which is not limited in this embodiment of the present application.
  • S601 can be implemented as S601c:
  • the terminal device sends the first information to the AMF of the home network through a registration request (registration request) message.
  • the AMF of the home network receives the first information from the terminal device through a registration request message.
  • the registration request message carries the first information.
  • the terminal device can send the first information to the AMF during the 5G registration process, so that the AMF knows that the terminal device supports VoNR, or the terminal device requests to obtain the PLMN information of the visited network, so as to prevent the AMF from sending a call to a terminal device that does not support VoNR.
  • Network PLMN information may be used.
  • the first information may also be carried in a field indicating the network capability of the terminal device in the registration request message.
  • the first information may be carried in a field indicating the 4G network capability of the terminal device, such as the user equipment network capability (S1UE network capability) of the S1 interface.
  • the S1 interface is an interface between the eNB in the E-UTRAN equipment and the core network equipment.
  • the S1 interface includes the S1-MME interface and the S1-U interface.
  • the S1-MME interface is the control plane interface, which is the communication connection interface between the E-UTRAN equipment and the MME;
  • the S1-U interface is the user plane interface.
  • the interface is an interface for communication connection between the E-UTRAN equipment and the SGW.
  • the first information may also be carried in a field indicating the 5G network capability of the terminal device, for example, a mobility management capability field, which may specifically include a 5G mobility management capability (5G mobility management, 5GMM capability). It should be understood that the first information may also be carried in other fields in the registration request message, which is not limited in this embodiment of the present application.
  • the above-mentioned field indicating the network capability of the terminal device may carry the first information through a certain number of preset bits.
  • the preset bits may include fixed bits in the field indicating the network capability of the user equipment, such as bits in a spare (spare) state.
  • byte 1 indicates IEI, which is 5GMM capability IEI.
  • Byte 2 indicates the length of 5GMM capability contents (length of 5GMM capability contents).
  • Byte 3 to Byte 6 (such as Bit 1 to Bit 3 in Byte 6), information of Property 1 to Property 27 may be included. Wherein, for characteristics 1 to 27, reference may be made to introductions in related technologies, and details are not repeated here.
  • byte 6 eg, bit 4 to bit 8 in byte 6) to byte 15, bits in a spare state are included.
  • the fixed bit bits include at least one of the following bits: some bits in byte 6 (such as bit 4 to bit 8 in byte 6), byte 7, byte 8, byte 9 , Byte 10, Byte 11, Byte 12, Byte 13, Byte 14, All bits in Byte 15.
  • some bits in byte 6 such as bit 4 to bit 8 in byte 6
  • byte 7, byte 8, byte 9 Byte 10, Byte 11, Byte 12, Byte 13, Byte 14, All bits in Byte 15.
  • Table 4 for a bit indicated by a circle, when the bit takes a value of 0, it indicates that the first information is carried, and when the bit takes a value of 1, it indicates that the first information is not carried.
  • the value of this bit is 1, it indicates that the first information is carried, and when the value of this bit is 0, it indicates that the first information is not carried, which is not limited in this embodiment of the present application.
  • S601 can be implemented as S601d:
  • the terminal device sends the first information to the AMF through a security mode complete (security mode complete, SMC) message.
  • the AMF receives the first information from the terminal device through a security mode completion message.
  • the security mode completion message carries the first information.
  • the security mode completion message is a message protected by an encryption key, thereby reducing the possibility of the first information being tampered with or leaked, and improving the reliability of information transmission.
  • the first information may also be carried in a field indicating the network capability of the terminal device in the security mode completion message.
  • the first information may be carried in a field indicating the 5G network capability of the terminal device, such as the mobility management capability field, which may specifically include the 5GMM capability field.
  • the first information may also be carried in other fields in the security mode completion message, which is not limited in this embodiment of the present application.
  • the terminal device before performing S601d, the terminal device first sends a registration request message to the AMF.
  • the AMF receives the registration request message from the terminal device.
  • the registration request message carries concealed identity information (subscriber concealed identifier, SUCI).
  • SUCI is generated by an end device.
  • SUCI includes at least one of the following information:
  • the first item, the subscription permanent identifier (SUPI Type) can have 7 values, which are used to identify the 7 types of SUPI encrypted in SUCI.
  • SUPI Type when the value of SUPI Type is 0, it means that SUPI is an international mobile subscriber identification number (IMSI).
  • IMSI international mobile subscriber identification number
  • the IMSI is a sign for distinguishing terminal equipment.
  • IMSI includes mobile country code (mobile country code, MCC), mobile network code (mobile network code, MNC) and mobile subscriber identification number (mobile subscriber identification number, MSIN).
  • MCC mobile country code
  • MNC mobile network code
  • MSIN mobile subscriber identification number
  • the MCC is used to uniquely identify the country to which the mobile user belongs, for example, the MCC in my country is 460.
  • the MNC is used to identify which operator the mobile user belongs to.
  • MSIN is used to identify a mobile subscriber in a certain mobile communication network.
  • SUPI Type When the value of SUPI Type is 1, it means that SUPI is
  • the second item is the home network identifier.
  • the home network indicator may include MCC and MNC.
  • MCC and MNC are used to uniquely represent the network operator of the terminal equipment.
  • the registration request message carrying SUCI does not carry the above-mentioned first information.
  • the AMF After the AMF receives the registration request message carrying the SUCI, the AMF authenticates the terminal device based on the SUCI. Then, the AMF sends a security mode command (security mode command) message to the terminal device. Correspondingly, the terminal device receives the security mode command message from the AMF.
  • security mode command security mode command
  • the security mode command message carries encryption key information, such as the key negotiated and used between the AMF and the terminal device.
  • the encryption key carried in the security mode command message is used to protect the security mode completion message. For details, refer to the introduction of S601d, which will not be repeated here.
  • the core network device sends the PLMN information of the visited network to the terminal device.
  • the terminal device receives the PLMN information of the visited network from the core network device.
  • the PLMN information in S602 is consistent with the PLMN information in S601 , and will not be repeated here.
  • the PLMN ID used by operator A for inter-network roaming in region X is 46030, then when the terminal equipment supporting VoNR of operator B registers with operator B, it receives 46030 sent by the core network equipment.
  • the terminal device that receives 46030 can choose the network of operator A and register to the network of operator A. Conversely, a terminal device that does not support VoNR will not receive the 46030 sent by the core network device, and will not be able to register with the network of operator A.
  • S602 can be implemented as S602a:
  • the MME sends the PLMN information of the visited network to the terminal device through a registration accept (attach accept) message.
  • the terminal device receives the PLMN information of the visited network from the MME through the registration acceptance message.
  • the registration acceptance message carries the PLMN information of the visited network.
  • the registration accept message For the specific implementation process of sending the PLMN information of the visited network through the registration accept message, please refer to the introduction of sending the EPLMN through the registration accept message, which will not be repeated here.
  • S602 can be implemented as S602b:
  • the MME sends the PLMN information of the visited network to the terminal device through a TAU acceptance message.
  • the terminal device receives the PLMN information of the visited network from the MME through the TAU Accept message.
  • the TAU acceptance message carries the PLMN information of the visited network.
  • the terminal device when the terminal device supports VoNR, or the terminal device requests to obtain the PLMN information of the visited network, the terminal device can obtain the PLMN information of the visited network during the TAU process, so that the terminal device can perform voice services through the visited network.
  • S602 can be implemented as S602c:
  • the AMF sends the PLMN information of the visited network to the terminal device through a registration acceptance message.
  • the terminal device receives the PLMN information of the visited network from the AMF through the registration acceptance message.
  • the registration acceptance message carries the PLMN information of the visited network.
  • the registration accept message For the specific implementation process of sending the PLMN information of the visited network through the registration accept message, please refer to the introduction of sending the EPLMN through the registration accept message, which will not be repeated here.
  • FIG. 7a to FIG. 7d it is only an example of which messages are used to send the PLMN information of the visited network.
  • other messages can also be used to send the PLMN information of the visited network, which is not discussed in the embodiment of the present application. limited.
  • the terminal device sends the first information to the core network device, so that the core network device determines that the terminal device supports the VoNR function, or requests the core network device to obtain the PLMN information of the visited network.
  • the core network device sends the terminal device Send the PLMN information of the visited network.
  • the embodiment of the present application also provides a second communication method.
  • the core network device determines that the terminal device supports VoNR.
  • the core network device is the core network device of the network to which the terminal device belongs.
  • the core network device sends the PLMN information of the visited network to the terminal device, where the operator of the visited network is different from the operator of the home network of the terminal device. In this way, the core network device sends the PLMN information of the visited network to the terminal device only when it is determined that the terminal device supports the VoNR function.
  • the terminal equipment can still access the visited network and perform voice services through the visited network, avoiding the problem that the terminal equipment cannot perform voice services after accessing the visited network because the terminal equipment does not support VoNR.
  • the second communication method 800 provided by the embodiment of the present application includes the following steps:
  • the core network device determines that the terminal device supports VoNR.
  • the core network device is the core network device in the network to which the terminal device belongs.
  • the core network device may be the MME shown in FIG. 2 , or the AMF shown in FIG. 3 . It should be understood that with the evolution of communication technologies, core network devices may also have other names, which are not limited in this embodiment of the present application.
  • VoNR the introduction of VoNR can be found in the explanation of terms, and will not be repeated here.
  • the implementation process of S801 includes the following two examples (Example 1 and Example 2):
  • S801 is implemented as S801a and S801b:
  • the access network device sends wireless capability information to the core network device.
  • the core network equipment receives the wireless capability information from the access network equipment.
  • the wireless capability information indicates the wireless capability of the terminal device.
  • the radio capability information may include UE radio capability info.
  • the wireless capability information may include IMS parameters (IMS-Parameters), and the IMS-ParametersFRX-Diff field of the parameters may include a VoNR field whose value is supported (supported), to indicate that the terminal device supports VoNR.
  • the IMS-ParametersFRX-Diff field may not include the VoNR field, or, the value of the VoNR field indicates not supported (not supported), to indicate that the terminal device does not support VoNR.
  • FIG. 10a shows a schematic flow chart of transmitting wireless capability information, and the specific steps are as follows:
  • Step 11 the terminal device sends a registration request message to the core network device.
  • the core network device receives the registration request message from the terminal device.
  • the registration request message is used to initiate registration.
  • the registration request message is used for the terminal device to register to the 4G network.
  • the registration request message can also be described as an attach request (attach request), as shown in FIG. 10b.
  • attach request attach request
  • the registration request message is used for the terminal device to register to the 5G network.
  • the registration request message may also be recorded as registration equest, as shown in Figure 10c.
  • Step 12 the core network device sends a capability matching request message to the access network device.
  • the access network device receives the capability matching request message from the core network device.
  • the capability matching request message is used to request the access network device to determine whether the terminal device supports IMS voice.
  • the access network device may be an eNB, and the capability matching request may also be described as a user equipment capability matching request of an application protocol (application protocol, AP) of the S1 interface , as recorded as S1-AP UE Capability match request, as shown in Figure 10b.
  • the access network device can be a gNB, and the capability matching request can also be described as a user equipment capability matching request on the N2 interface, such as N2 UE Capability match request, as shown in Figure 10c shown.
  • Step 13 the access network device sends a capability query message to the terminal device.
  • the terminal device receives the capability query message from the access network device.
  • the capability query message is used to query the wireless capability of the terminal device.
  • the capability query message may include the capability query message of the user equipment, that is, UE Capability enquiry.
  • Step 14 the terminal device sends the capability information of the access network device.
  • the access network device receives the capability information from the terminal device.
  • the capability information indicates the wireless capability of the terminal device.
  • the capability information may be recorded as UE capability information.
  • Step 15 the access network device sends a capability matching response message to the core network device.
  • the core network device receives the capability matching response message from the access network device.
  • the capability matching response message at least indicates whether the terminal device supports IMS voice.
  • the capability matching response message may also be described as a UE radio capability match response (UE radio capability match response).
  • the core network device waits to receive wireless capability information, that is, the core network device first performs S801a, and then performs S801b.
  • the wireless capability information in S801a may be determined based on the capability information in step 14, or the wireless capability information in S801a includes the capability information in step 14, which is not limited in this embodiment of the present application.
  • FIG. 11 shows a schematic flow chart of transmitting wireless capability information, and the specific steps are as follows:
  • Step 21 the terminal device sends a registration request message to the core network device.
  • the core network device receives the registration request message from the terminal device.
  • step 21 reference may be made to the introduction of step 11, which will not be repeated here.
  • Step 22 when the core network device does not save the wireless capability information, the core network device sends an initial context setup request (initial context setup request) to the access network device.
  • the access network device receives the initial context establishment request from the core network device.
  • the initial context establishment request does not carry wireless capability information.
  • the wireless capability information indicates the wireless capability of the terminal device, and reference may be made to the introduction of S801a, which will not be repeated here.
  • the initial context establishment request may carry security context information, which is not limited in this embodiment of the present application.
  • the access network device learns that the core network device does not save the wireless capability information of the terminal device, and then the access network device performs step 23, step 24 and step S801a:
  • Step 23 the access network device sends a capability query message to the terminal device.
  • the terminal device receives the capability query message from the access network device.
  • step 23 reference may be made to the introduction of step 13, which will not be repeated here.
  • Step 24 the terminal device sends the capability information of the access network device.
  • the access network device receives the capability information from the terminal device.
  • step 24 reference may be made to the introduction of step 14, which will not be repeated here.
  • S801a is performed.
  • the wireless capability information in S801a may be determined based on the capability information in step 24, or the wireless capability information in S801a includes the capability information in step 24, which is not limited in this embodiment of the present application.
  • the core network device first executes S801a, and then executes S801b.
  • the core network device may be implemented as the MME in FIG. 2 , and in this case, the access network device may be an eNB, as shown in FIG. 10 b .
  • the core network device can also be implemented as the AMF in FIG. 3 .
  • the access network device can be a gNB, as shown in FIG. 10c , which will not be repeated here.
  • the core network device determines that the terminal device supports VoNR according to the wireless capability information.
  • the core network device determines that the terminal device supports VoNR.
  • the core network determines that the end device does not support VoNR.
  • the core network device can autonomously determine that the terminal device supports the VoNR function based on the wireless capability information.
  • S801 is implemented as S801c and S801d:
  • the access network device sends indication information to the core network device.
  • the core network equipment receives the indication information from the access network equipment.
  • the indication information indicates that the terminal equipment supports VoNR, for details, please refer to the introduction of S601, which will not be repeated here.
  • the characteristic indicated by the indication information is determined based on the capability information of the terminal device. Still taking the IMS parameter in the capability information as an example, when the IMS-ParametersFRX-Diff field of this parameter includes the VoNR field whose value is supported (supported), the access network device determines that the terminal device supports VoNR. Correspondingly, the indication information indicates that the terminal equipment supports VoNR. When the IMS-ParametersFRX-Diff field does not include the VoNR field, or the value of the VoNR field indicates not supported (not supported), the access network device determines that the terminal device does not support VoNR. Correspondingly, the indication information indicates that the terminal device does not support VoNR.
  • S801c may be replaced by the following step: the access network device sends indication information to the core network device through a wireless capability matching response message.
  • the core network device receives the indication information from the access network device through the wireless capability matching response message.
  • the wireless capability matching response message carries indication information through a preset number of spare fields.
  • the wireless capability matching response message carries the above indication information, so that the core network equipment acquires the above indication information.
  • the foregoing only uses the wireless capability matching response message as an example to introduce the bearing of the indication information.
  • the indication information may also be transmitted through other messages, or carried in an independent message, which is not limited in this embodiment of the present application.
  • the access network device may execute S801c autonomously, or may execute S801c in response to a request of the core network device.
  • the core network device also executes S801e before executing S801c:
  • the core network device sends a first request message to the access network device.
  • the access network device receives the first request message from the core network device.
  • the first request message requests to obtain indication information.
  • the indication information in S801e is consistent with the indication information in S801c, and will not be repeated here.
  • S801e may be replaced by the following step: the core network device sends the first request message to the access network device through a capability information indication message.
  • the access network device receives the first request message from the core network device through the capability information indication message.
  • the capability information indication message carries the first request message through a preset number of spare fields.
  • the transmission process of the first request message is introduced: in the case that the core network device is implemented as the MME in FIG. 2, the access network device may be an eNB, and the capability information indication message may include The user equipment capability information indication of the application protocol of the S1 interface (S1-AP UE capability info indication), as shown in Figure 12b.
  • the access network device may be a gNB, and the capability information indication message may include an N2 interface user equipment capability information indication (N2 UE capability info indication), as shown in Figure 12c.
  • N2 UE capability info indication N2 interface user equipment capability information indication
  • the capability information indication message carries the first request message, so as to send the indication information to the access network device.
  • the foregoing only uses the capability information indication message as an example to introduce the bearer of the first request message.
  • the first request message may also be transmitted through other messages, or be carried in an independent message for transmission, which is not limited in this embodiment of the present application.
  • the core network device determines that the terminal device supports VoNR according to the indication information.
  • the core network device can determine that the terminal device supports VoNR.
  • the core network device can determine that the terminal device does not support VoNR.
  • the access network device determines whether the terminal device supports the VoNR function, and then informs the core network device, so that the core network device knows whether the terminal device supports the VoNR function. Support VoNR function.
  • the core network device For the core network device, if it is determined that the terminal device supports VoNR, the core network device performs S802; otherwise, when it is determined that the terminal device does not support VoNR, the core network device does not perform S802.
  • the core network device sends the PLMN information of the visited network to the terminal device.
  • the terminal device receives the PLMN information of the visited network from the core network device.
  • the core network device sends the PLMN information of the visited network to the terminal device only when it is determined that the terminal device supports the VoNR function. Even if the operator of the visited network is different from the operator of the home network, the terminal equipment can still access the visited network and perform voice services through the visited network, avoiding the problem that the terminal equipment cannot perform voice services after accessing the visited network because the terminal equipment does not support VoNR.
  • the embodiment of the present application further provides a communication device, and the communication device may be the network element in the foregoing method embodiment, or a device including the foregoing network element, or may be a component applicable to the network element.
  • the communication device includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • FIG. 13 shows a schematic structural diagram of a communication device 1300 .
  • the communication device 1300 includes a processing unit 1301 , a sending unit 1302 and a receiving unit 1303 .
  • the processing unit 1301 is configured to support the terminal device to perform other processing operations that the terminal device needs to perform in FIG. 6 .
  • the sending unit 1302 is configured to support the terminal device to perform S601 in FIG. 6 and/or other sending operations that the terminal device needs to perform in the embodiment of the present application.
  • the receiving unit 1303 is configured to support the terminal device to perform S602 in FIG. 6 and/or other receiving operations that the terminal device needs to perform in the embodiment of the present application.
  • the processing unit 1301 is configured to support the terminal device to perform other processing operations that the terminal device needs to perform in FIG. 8 .
  • the sending unit 1302 is configured to support the terminal device to perform other sending operations that the terminal device in FIG. 8 needs to perform.
  • the receiving unit 1303 is configured to support the terminal device to perform S802 in FIG. 8 and/or other receiving operations that the terminal device needs to perform in the embodiment of the present application.
  • the processing unit 1301 is configured to support the core network device to perform other processing operations that the core network device in FIG. 6 needs to perform.
  • the sending unit 1302 is configured to support the core network device to perform S602 in FIG. 6 , and/or other sending operations that the core network device needs to perform in the embodiment of the present application.
  • the receiving unit 1303 is configured to support the core network device to perform S601 in FIG. 6 , and/or other receiving operations that the core network device needs to perform in the embodiment of the present application.
  • the processing unit 1301 is configured to support the core network device to execute S801 in FIG. Processing operations.
  • the sending unit 1302 is configured to support the core network device to perform S802 in FIG. 8 , and/or other sending operations that the core network device needs to perform in the embodiment of the present application.
  • the receiving unit 1303 is configured to support the core network device to perform other receiving operations that the core network device in FIG. 8 needs to perform.
  • the communication device 1300 may further include a storage unit 1304 for storing program codes and data of the communication device, and the data may include but not limited to original data or intermediate data.
  • the processing unit 1301 may be a processor or a controller, such as a CPU, a general-purpose processor, an application specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other Programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor can also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of DSP and a microprocessor, and so on.
  • the sending unit 1302 may be a communication interface, a transmitter, or a sending circuit, etc., where the communication interface is collectively referred to as, in a specific implementation, the communication interface may include multiple interfaces, for example, may include: interface and/or other interfaces.
  • the receiving unit 1303 may be a communication interface, a receiver or a receiving circuit, etc., wherein the communication interface is collectively referred to as, in a specific implementation, the communication interface may include multiple interfaces, for example, it may include: interface and/or other interfaces.
  • the sending unit 1302 and the receiving unit 1303 may be physically or logically implemented as the same unit.
  • the storage unit 1304 may be a memory.
  • the processing unit 1301 is a processor
  • the sending unit 1302 and the receiving unit 1303 are communication interfaces
  • the storage unit 1304 is a memory
  • the communication device involved in this embodiment of the present application may be as shown in FIG. 14 .
  • the communication device includes: a processor 1401 , a communication interface 1402 , and a memory 1403 .
  • the communication device may further include a bus 1404 .
  • the communication interface 1402, the processor 1401 and the memory 1403 can be connected to each other through the bus 1404;
  • the bus 1404 can be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus etc.
  • the bus 1404 can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 14 , but it does not mean that there is only one bus or one type of bus.
  • the embodiments of the present application further provide a computer program product carrying computer instructions, and when the computer instructions are run on a computer, the computer is made to execute the method described in the foregoing embodiments.
  • an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer executes the method described in the above-mentioned embodiments.
  • an embodiment of the present application further provides a chip, including: a processing circuit and a transceiver circuit, and the processing circuit and the transceiver circuit are used to implement the methods described in the foregoing embodiments.
  • the processing circuit is used to execute the processing action in the corresponding method
  • the transceiver circuit is used to execute the receiving/sending action in the corresponding method.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state drive (solid state drive, SSD)) wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a tape
  • an optical medium for example, a digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state drive (solid state drive, SSD)
  • the disclosed system, device and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the modules is only a logical function division. In actual implementation, there may be other division methods.
  • multiple modules or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or modules may be in electrical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple devices. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Landscapes

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

Abstract

本申请提供了通信方法及装置,涉及无线通信技术领域,能够避免由于终端设备不支持新空口语音VoNR接入拜访网络后无法进行语音业务的问题。该方法包括:终端设备向归属网络的核心网设备发送第一信息。其中,第一信息用于指示终端设备支持VoNR或异网漫游,或者,第一信息用于请求获取拜访网络的公共陆地移动网络PLMN信息,拜访网络的运营商与终端设备归属网络的运营商不同。之后,终端设备从核心网设备接收拜访网络的PLMN信息。

Description

通信方法及装置
本申请要求于2021年12月27日提交国家知识产权局、申请号为202111618289.X、申请名称为“一种注册传输的方法、装置”的中国专利申请的优先权,以及2022年1月17日提交国家知识产权局、申请号为202210051820.8、申请名称为“通信方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及无线通信领域,尤其涉及一种通信方法及装置。
背景技术
在第五代(fifth generation,5G)独立组网(standalong,SA)布网初期,运营商网络和终端设备不支持新空口语音(voice over new radio,VoNR),终端设备需要通过演进分组系统(evolved packet system,EPS)回落(fallback)到第四代(forth generation,4G)网络进行语音业务。执行EPS fallback需要5G的核心网网元接入及移动性管理功能(access and mobility management function,AMF)与4G的核心网网元移动管理实体(mobility management entity,MME)间开通接口,从而完成从5G到4G的回落过程,并在4G网络中建立语音传输通道。
然而,在5G核心网异网漫游场景中,拜访网络方的AMF与归属网络方的MME间并未开通接口,因此不支持的VONR的终端设备无法通过执行EPS fallback过程到4G建立语音传输通道,也就无法进行语音业务,用户体验差。
发明内容
本申请实施例提供一种通信方法及装置,能够避免由于终端设备不支持新空口语音VoNR接入拜访网络后无法进行语音业务的问题。
为达到上述目的,本申请实施例采用如下技术方案:
第一方面,本申请提供一种通信方法,该方法的执行主体可以是终端设备,也可以是应用于终端设备中的芯片。下面以执行主体是终端设备为例进行描述。该方法包括:终端设备向归属网络的核心网设备发送第一信息。其中,第一信息用于指示终端设备支持新空口语音VoNR或异网漫游。或者,第一信息用于请求获取拜访网络的公共陆地移动网络PLMN信息,拜访网络的运营商与终端设备归属网络的运营商不同。之后,终端设备从核心网设备接收拜访网络的PLMN信息。
如此,核心网设备确定终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息的情况下,才向终端设备发送拜访网络的PLMN信息。即使拜访网络的运营商与归属网络的运营商不同,终端设备也能够接入拜访网络,通过拜访网络执行语音业务,避免由于终端设备不支持VoNR接入拜访网络后无法进行语音业务的问题。
在一种可能的设计中,终端设备通过附着请求消息向归属网络的核心网设备发送第一信息,以使终端设备在4G注册过程中,即可向核心网设备发送第一信息,核心网设备即可获知终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息,避免核心网设备向不支持VoNR的终端设备发送拜访网络的PLMN信息。
在一种可能的设计中,终端设备通过注册请求消息向归属网络的核心网设备发送第一信息,以使终端设备在5G注册过程中,即可向核心网设备发送第一信息,以使核心网设备获知终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息,避免核心网设备向不支持VoNR的终端设备发送拜访网络的PLMN信息。
在一种可能的设计中,第一信息承载于指示用户设备网络能力的字段。
在一种可能的设计中,第一信息承载于预设比特,其中,预设比特包括指示用户设备网络能力的字段中固定比特位的比特,如原处于备用(Spare)状态的比特。
在一种可能的设计中,第一信息承载于以下其中一项:用户设备网络能力字段,或者,N1接口的用户设备网络能力字段。
在一种可能的设计中,第一信息承载于以下其中一项:移动管理能力字段,或者,S1接口的用户设备网络能力字段。
在一种可能的设计中,终端设备通过安全模式完成消息向归属网络的核心网设备发送第一信息。其中,安全模式完成消息是采用加密密钥进行保护的消息,从而降低第一信息被篡改、泄露的可能性,提高信息传输可靠性。
在一种可能的设计中,终端设备通过跟踪区更新TAU请求消息向归属网络的核心网设备发送第一信息,以使终端设备在TAU过程中,即可向核心网设备发送第一信息,以使核心网设备获知终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息,以避免核心网设备向不支持VoNR的终端设备发送拜访网络的PLMN信息。
第二方面,本申请提供一种通信方法,该方法的执行主体可以是核心网设备,也可以是应用于核心网设备中的芯片。下面以执行主体是核心网设备为例进行描述。该方法包括:核心网设备接收来自终端设备的第一信息。其中,第一信息用于指示终端设备支持新空口语音VoNR或异网漫游。或者,第一信息用于请求获取拜访网络的公共陆地移动网络PLMN信息,拜访网络的运营商与终端设备归属网络的运营商不同,核心网设备是终端设备归属网络的核心网设备。之后,核心网设备根据第一信息向终端设备发送拜访网络的PLMN信息。
在一种可能的设计中,核心网设备通过附着请求消息接收来自终端设备的第一信息。
在一种可能的设计中,核心网设备通过注册请求消息接收来自终端设备的第一信息。
在一种可能的设计中,第一信息承载于指示用户设备网络能力的字段。
在一种可能的设计中,第一信息承载于预设比特,预设比特包括指示用户设备网络能力的字段中固定比特位的比特。
在一种可能的设计中,第一信息承载于以下其中一项:用户设备网络能力字段,或者,N1接口的用户设备网络能力字段。
在一种可能的设计中,第一信息承载于以下其中一项:移动管理能力字段,或者,S1接口的用户设备网络能力字段。
在一种可能的设计中,核心网设备通过安全模式完成消息接收来自终端设备的第一信息。
在一种可能的设计中,核心网设备通过跟踪区更新TAU请求消息接收来自终端设备的第一信息。
第三方面,本申请提供一种通信方法,该方法的执行主体可以是核心网设备,也可以是应用于核心网设备中的芯片。下面以执行主体是核心网设备为例进行描述。该方法包括:核心网设备确定终端设备支持新空口语音VoNR,其中,核心网设备是终端设备归属网络的核 心网设备。之后,核心网设备向终端设备发送拜访网络的公共陆地移动网络PLMN信息,其中,拜访网络的运营商与终端设备归属网络的运营商不同。
如此,核心网设备在确定终端设备支持VoNR功能的情况下,才向终端设备发送拜访网络的PLMN信息。即使拜访网络的运营商与归属网络的运营商不同,终端设备也能够接入拜访网络,通过拜访网络执行语音业务,避免由于终端设备不支持VoNR接入拜访网络后无法进行语音业务的问题。
在一种可能的设计中,本申请实施例通信方法还包括:核心网设备接收来自接入网设备的无线能力信息。其中,无线能力信息指示终端设备的无线能力。核心网设备确定终端设备支持VoNR,包括:核心网设备根据无线能力信息,确定终端设备支持VoNR。
如此,核心网设备即可基于无线能力信息,来自主确定终端设备支持VoNR功能。
在一种可能的设计中,本申请实施例通信方法还包括:当核心网设备未保存无线能力信息时,核心网设备向接入网设备发送初始上下文建立请求,其中,初始上下文建立请求未携带无线能力信息,以使接入网设备向核心网设备提供无线能力信息。
在一种可能的设计中,本申请实施例通信方法还包括:核心网设备接收来自接入网设备的指示信息,其中,指示信息指示终端设备支持VoNR。核心网设备确定终端设备支持VoNR,包括:核心网设备根据指示信息,确定终端设备支持VoNR。
如此,接入网设备来确定终端设备支持VoNR功能,再告知核心网设备,以使核心网设备获知终端设备支持VoNR功能。
在一种可能的设计中,核心网设备通过无线能力匹配响应消息接收来自接入网设备的指示信息。也就是说,无线能力匹配响应消息携带上述指示信息,从而使得核心网设备获取到上述指示信息。
在一种可能的设计中,本申请实施例通信方法还包括:核心网设备向接入网设备发送第一请求消息。其中,第一请求消息请求获取指示信息,以使接入网设备响应于第一请求消息,来向核心网设备提供指示信息。
在一种可能的设计中,核心网设备通过终端设备能力信息指示消息向接入网设备发送第一请求消息。也就是说,能力信息指示消息携带上述第一请求消息,从而向接入网设备发送上述指示信息。
在一种可能的设计中,核心网设备通过注册接受消息向终端设备发送拜访网络的PLMN信息,以使终端设备通过注册过程获取到拜访网络的PLMN信息,有效避免不支持VoNR的终端设备接收到拜访网络的PLMN信息。
在一种可能的设计中,核心网设备包括移动性管理实体MME,或移动管理功能AMF网元。
第四方面,本申请提供一种通信装置,该通信装置可以为上述第一方面或第一方面任一种可能的设计中的终端设备,或者实现上述终端设备功能的芯片;所述通信装置包括实现上述方法相应的模块、单元、或手段(means),该模块、单元、或means可以通过硬件实现,软件实现,或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括处理单元、发送单元和接收单元。其中,处理单元用于控制发送单元向归属网络的核心网设备发送第一信息,其中,第一信息用于指示通信装置支持新空口语音 VoNR或异网漫游,或者,第一信息用于请求获取拜访网络的公共陆地移动网络PLMN信息,拜访网络的运营商与通信装置归属网络的运营商不同。处理单元还用于控制接收单元从核心网设备接收拜访网络的PLMN信息。
在一种可能的设计中,发送单元,具体用于通过附着请求消息向归属网络的核心网设备发送第一信息。
在一种可能的设计中,发送单元,具体用于通过注册请求消息向归属网络的核心网设备发送第一信息。
在一种可能的设计中,第一信息承载于指示用户设备网络能力的字段。
在一种可能的设计中,第一信息承载于预设比特,其中,预设比特包括指示用户设备网络能力的字段中固定比特位的比特。
在一种可能的设计中,第一信息承载于以下其中一项:用户设备网络能力字段,或者,N1接口的用户设备网络能力字段。
在一种可能的设计中,第一信息承载于以下其中一项:移动管理能力字段,或者,S1接口的用户设备网络能力字段。
在一种可能的设计中,发送单元,具体用于通过安全模式完成消息向归属网络的核心网设备发送第一信息。
在一种可能的设计中,发送单元,具体用于通过跟踪区更新TAU请求消息向归属网络的核心网设备发送第一信息。
第五方面,本申请提供一种通信装置,该通信装置可以为上述第二方面或第二方面任一种可能的设计中的核心网设备,或者实现上述核心网设备功能的芯片;所述通信装置包括实现上述方法相应的模块、单元、或手段(means),该模块、单元、或means可以通过硬件实现,软件实现,或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括处理单元、发送单元和接收单元。其中,处理单元用于控制接收单元接收来自终端设备的第一信息,其中,第一信息用于指示终端设备支持新空口语音VoNR或异网漫游,或者,第一信息用于请求获取拜访网络的公共陆地移动网络PLMN信息,拜访网络的运营商与终端设备归属网络的运营商不同,通信装置是终端设备归属网络的核心网设备。处理单元还用于根据第一信息控制发送单元向终端设备发送拜访网络的PLMN信息。
在一种可能的设计中,接收单元,具体用于通过附着请求消息接收来自终端设备的第一信息。
在一种可能的设计中,接收单元,具体用于通过注册请求消息接收来自终端设备的第一信息。
在一种可能的设计中,第一信息承载于指示用户设备网络能力的字段。
在一种可能的设计中,第一信息承载于预设比特,预设比特包括指示用户设备网络能力的字段中固定比特位的比特。
在一种可能的设计中,第一信息承载于以下其中一项:用户设备网络能力字段,或者,N1接口的用户设备网络能力字段。
在一种可能的设计中,第一信息承载于以下其中一项:移动管理能力字段,或者,S1接口的用户设备网络能力字段。
在一种可能的设计中,接收单元,具体用于通过安全模式完成消息接收来自终端设备的第一信息。
在一种可能的设计中,接收单元,具体用于通过跟踪区更新TAU请求消息接收来自终端设备的第一信息。
第六方面,本申请提供一种通信装置,该通信装置可以为上述第三方面或第三方面任一种可能的设计中的核心网设备,或者实现上述核心网设备功能的芯片;所述通信装置包括实现上述方法相应的模块、单元、或手段(means),该模块、单元、或means可以通过硬件实现,软件实现,或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
该通信装置包括处理单元、发送单元和接收单元。其中,处理单元,用于确定终端设备支持新空口语音VoNR,其中,通信装置是终端设备归属网络的核心网设备。发送单元,用于向终端设备发送拜访网络的公共陆地移动网络PLMN信息,其中,拜访网络的运营商与终端设备归属网络的运营商不同。
在一种可能的设计中,接收单元,还用于接收来自接入网设备的无线能力信息,其中,无线能力信息指示终端设备的无线能力。处理单元,用于确定终端设备支持VoNR,包括:根据无线能力信息,确定终端设备支持VoNR。
在一种可能的设计中,发送单元,还用于当通信装置未保存无线能力信息时,向接入网设备发送初始上下文建立请求,其中,初始上下文建立请求未携带无线能力信息。
在一种可能的设计中,接收单元,还用于接收来自接入网设备的指示信息,其中,指示信息指示终端设备支持VoNR。处理单元,用于确定终端设备支持VoNR,包括:根据指示信息,确定终端设备支持VoNR。
在一种可能的设计中,接收单元,具体用于通过无线能力匹配响应消息接收来自接入网设备的指示信息。
在一种可能的设计中,发送单元,还用于向接入网设备发送第一请求消息,其中,第一请求消息请求获取指示信息。
在一种可能的设计中,发送单元,具体用于通过终端设备能力信息指示消息向接入网设备发送第一请求消息。
在一种可能的设计中,发送单元,具体用于通过注册接受消息向终端设备发送拜访网络的PLMN信息。
在一种可能的设计中,通信装置包括移动性管理实体MME,或移动管理功能AMF网元。
第七方面,本申请实施例提供了一种通信装置,包括:处理器和存储器;该存储器用于存储计算机指令,当该处理器执行该指令时,使得该通信装置执行上述任一方面或任一方面任一种可能的设计中终端设备所执行的方法。该通信装置可以为上述第一方面或第一方面任一种可能的设计中的终端设备,或者实现上述终端设备功能的芯片。
第八方面,本申请实施例提供了一种通信装置,包括:处理器;所述处理器与存储器耦合,用于读取存储器中的指令并执行,以使该通信装置执行如上述任一方面或任一方面任一种可能的设计中的终端设备所执行的方法。该通信装置可以为上述第一方面或第一方面任一种可能的设计中的终端设备,或者实现上述终端设备功能的芯片。
第九方面,本申请实施例提供一种芯片,包括处理电路和输入输出接口。其中,输入输 出接口用于与芯片之外的模块通信,例如,该芯片可以为实现上述第一方面或第一方面任一种可能的设计中的终端设备功能的芯片。处理电路用于运行计算机程序或指令,以实现以上第一方面或第一方面任一种可能的设计中的方法。
第十方面,本申请实施例提供了一种通信装置,包括:处理器和存储器;该存储器用于存储计算机指令,当该处理器执行该指令时,使得该通信装置执行上述任一方面或任一方面任一种可能的设计中核心网设备所执行的方法。该通信装置可以为上述第二方面或第二方面任一种可能的设计中的核心网设备,或者,该通信装置可以为上述第三方面或第三方面任一种可能的设计中的核心网设备,或者实现上述核心网设备功能的芯片。
第十一方面,本申请实施例提供了一种通信装置,包括:处理器;所述处理器与存储器耦合,用于读取存储器中的指令并执行,以使该通信装置执行如上述任一方面或任一方面任一种可能的设计中的核心网设备所执行的方法。该通信装置可以为上述第二方面或第二方面任一种可能的设计中的核心网设备,或者,该通信装置可以为上述第三方面或第三方面任一种可能的设计中的核心网设备,或者实现上述核心网设备功能的芯片。
第十二方面,本申请实施例提供一种芯片,包括处理电路和输入输出接口。其中,输入输出接口用于与芯片之外的模块通信,例如,该芯片可以为实现上述第二方面或第二方面任一种可能的设计中的核心网设备功能的芯片。处理电路用于运行计算机程序或指令,以实现以上第二方面或第二方面任一种可能的设计中的方法。再如,该芯片可以为实现上述第三方面或第三方面任一种可能的设计中的核心网设备功能的芯片。处理电路用于运行计算机程序或指令,以实现以上第三方面或第三方面任一种可能的设计中的方法。
第十三方面,本申请实施例提供一种计算机可读存储介质,该计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机可以执行上述任一方面中任一项的方法。
第十四方面,本申请实施例提供一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机可以执行上述任一方面中任一项的方法。
第十五方面,本申请实施例提供一种电路系统,电路系统包括处理电路,处理电路被配置为执行如上述任一方面中任一项的方法。
第十六方面,本申请实施例提供一种通信系统,该通信系统包括核心网设备和接入网设备。其中,接入网设备,用于向核心网设备发送第一信息,其中,第一信息指示终端设备的无线能力,或第一信息指示终端设备支持新空口语音VoNR。核心网设备,用于接收来自接入网设备的第一信息,其中,核心网设备是终端设备归属网络的核心网设备。核心网设备,还用于根据第一信息确定终端设备支持VoNR。核心网设备,还用于向终端设备发送拜访网络的公共陆地移动网络PLMN信息,其中,拜访网络的运营商与终端设备归属网络的运营商不同。
其中,第二方面至第十六方面中任一种设计所带来的技术效果可参考上文所提供的对应的方法中的有益效果,此处不再赘述。
附图说明
图1为本申请的实施例应用的一种通信系统的架构示意图;
图2为本申请的实施例应用的再一种通信系统的架构示意图;
图3为本申请的实施例应用的又一种通信系统的架构示意图;
图4为本申请的实施例应用的又一种通信系统的架构示意图;
图5为本申请的实施例应用的又一种通信系统的架构示意图;
图6为本申请实施例提供的一种通信方法的流程示意图;
图7a为本申请实施例提供的再一种通信方法的流程示意图;
图7b为本申请实施例提供的又一种通信方法的流程示意图;
图7c为本申请实施例提供的又一种通信方法的流程示意图;
图7d为本申请实施例提供的又一种通信方法的流程示意图;
图8为本申请实施例提供的又一种通信方法的流程示意图;
图9为本申请实施例提供的又一种通信方法的流程示意图;
图10a为本申请实施例提供的又一种通信方法的流程示意图;
图10b为本申请实施例提供的又一种通信方法的流程示意图;
图10c为本申请实施例提供的又一种通信方法的流程示意图;
图11为本申请实施例提供的又一种通信方法的流程示意图;
图12a为本申请实施例提供的又一种通信方法的流程示意图;
图12b为本申请实施例提供的又一种通信方法的流程示意图;
图12c为本申请实施例提供的又一种通信方法的流程示意图;
图13为本申请实施例提供的一种通信装置的结构示意图;
图14为本申请实施例提供的再一种通信装置的结构示意图。
具体实施方式
图1为本申请实施例提供的一种通信系统的架构示意图。如图1所示,该通信系统包括终端设备、接入网设备和核心网。
其中,终端设备,包括向用户提供语音和/或数据连通性的设备,具体的,包括向用户提供语音的设备,或包括向用户提供数据连通性的设备,或包括向用户提供语音和数据连通性的设备。例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网(radio access network,RAN)与核心网进行通信,与RAN交换语音或数据,或与RAN交互语音和数据。该终端设备可以包括用户设备(user equipment,UE)、无线终端设备、移动终端设备、设备到设备通信(device-to-device,D2D)终端设备、车到一切(vehicle to everything,V2X)终端设备、机器到机器/机器类通信(machine-to-machine/machine-type communications,M2M/MTC)终端设备、物联网(internet of things,IoT)终端设备、签约单元(subscriber unit)、签约站(subscriber station),移动站(mobile station)、远程站(remote station)、接入点(access point,AP)、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、或用户装备(user device)等。例如,可以包括移动电话(或称为“蜂窝”电话),具有移动终端设备的计算机,便携式、袖珍式、手持式、计算机内置的移动装置等。例如,个人通信业务(personal communication service,PCS)电话、无绳电话、会话发起协议(session initiation protocol,SIP)话机、无线本地环路(wireless local loop,WLL)站、个人数字助理(personal digital assistant,PDA)等设备。还包括受限设备,例如功耗较低的设备,或存储能力有限的设备,或计算能力有限的设备等。例如包括条码、射频识别(radio frequency identification,RFID)、传感器、全球定位系统(global positioning system,GPS)、激光扫描器等信息传感设备。
而如上介绍的各种终端设备,如果位于车辆上(例如放置在车辆内或安装在车辆内),都可以认为是车载终端设备,车载终端设备例如也称为车载单元(on-board unit,OBU)。
本申请实施例中,终端设备还可以包括中继(relay)。或者理解为,能够与基站进行数据通信的都可以看作终端设备。
本申请实施例中,用于实现终端设备的功能的装置可以是终端设备,也可以是能够支持终端设备实现该功能的装置,例如芯片系统,该装置可以被安装在终端设备中。本申请实施例中,芯片系统可以由芯片构成,也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中,以用于实现终端的功能的装置是终端设备为例,进行介绍。
接入网设备可以是无线通信或者有线通信的接入点,例如基站或基站控制器,无线保真(wireless-fidelity,wifi)的接入点或者wifi控制器,或者固网接入的接入点等。其中,所述基站可以包括各种类型的基站,例如:微基站(也称为小站),宏基站,中继站,接入点等,本申请实施例对此不作具体限定。在本申请实施例中,所述基站可以是全球移动通信系统(global system for mobile communication,GSM),码分多址(code division multiple access,CDMA)中的基站(base transceiver station,BTS),宽带码分多址(wideband code division multiple access,WCDMA)中的基站(node B),长期演进(long term evolution,LTE)中的演进型基站(evolutional node B,eNB或e-NodeB),物联网(internet of things,IoT)或者窄带物联网(narrow band-internet of things,NB-IoT)中的eNB,第五代(the fifth generation,5G)移动通信网络或者未来演进的公共陆地移动网络(public land mobile network,PLMN)中的基站,本申请实施例对此不作任何限制。
核心网包括各种核心网设备。例如,核心网设备可以包括移动管理实体(mobility management entity,MME),具体可以参见图2的介绍。再如,核心网设备也可以包括接入和移动性管理功能(core access and mobility management function,AMF)网元,具体可以参见图3的介绍。应理解,核心网设备也可以包括其他网元,如用户面功能(user plane function,UPF)网元、会话管理功能(session management function,SMF)网元等,此处不再赘述。
示例性的,图2示出了一种第四代(the fourth generation,4G)通信系统的架构示意图。该4G通信系统包括演进的通用移动通信系统(universal mobile telecommunications system,UMTS)陆地无线接入网(evolved UMTS territorial radio access network,E-UTRAN)设备、MME、服务网关(serving gateway,SGW)、分组数据网络(packet data network,PDN)网关(PDN gateway,PGW)、策略与计费规则功能(policy and charging rules function,PCRF)网元以及归属签约用户服务器(home subscriber server,HSS)等网元或设备。
其中,终端设备通过LTE-Uu接入E-UTRAN设备,E-UTRAN设备通过S1-MME与MME通信,E-UTRAN设备通过S1-U与SGW通信,不同的MME之间通过S10通信(图1中仅是示例性的给出一个MME),MME通过S6a与HSS通信,MME通过S11与SGW通信,PGW通过Gx与PCRF网元通信,PCRF网元通过Rx与服务器通信,SGW通过S5与PGW通信,PGW通过SGi接入服务器。
其中,E-UTRAN设备,用于实现与演进网络无线有关的功能。MME负责控制面的移动性管理,包括用户上下文和移动状态管理,分配用户临时身份标识等。SGW是第三代合作伙伴计划(3rd generation partnership project,3GPP)接入网络间的用户面锚点,是终止E-TURAN的接口。PGW是3GPP接入网络和非3GPP接入网络之间的用户面锚点,是终止和外部PDN 的接口。PCRF网元用于策略控制决定和流计费控制功能。HSS用于存储用户签约信息。服务器用于提供网际互连协议(internet protocol,IP)业务,如基于互联网协议多媒体子系统(internet protocol multimediasubsystem,IMS)的语音/视频业务、包交换流业务(packet switched streaming service,PSS)等。
示例性的,图3示出了一种第五代(the fifth generation,5G)通信系统的架构示意图。该5G通信系统包括无线接入网(radio access network,RAN)设备、UPF网元、AMF网元、SMF网元、认证服务器功能(authentication server function,AUSF)网元、网络切片选择功能(network slice selection function,NSSF)网元、网络开放功能(network exposure function,NEF)网元、网络功能存储功能(network exposure function repository function,NRF)网元、策略控制功能(policy control function,PCF)网元、统一数据管理(unified data management,UDM)网元、统一数据存储(unified data repository,UDR)网元、应用功能(application function,AF)网元或者计费功能(charging function,CHF)网元等。
需要说明的是,图3仅是示例性给出了5G通信系统中网元或实体的一些举例,该5G通信系统还可以包括网络数据分析功能(network data analytics function,NWDAF)网元等一些图3未示意出的网元或实体,本申请实施例对此不做具体限定。
其中,如图3所示,终端设备通过RAN设备接入5G网络,终端设备通过N1接口(简称N1)与AMF通信;RAN设备通过N2接口(简称N2)与AMF网元通信;RAN设备通过N3接口(简称N3)与UPF网元通信;SMF网元通过N4接口(简称N4)与UPF网元通信,UPF网元通过N6接口(简称N6)接入数据网络(data network,DN)。在图3所示的架构中,N1、N2、N3、N4和N6分别代表相关网元/网络功能之间的参考点(reference point)。
此外,图3所示的AUSF网元、AMF网元、SMF网元、NSSF网元、NEF网元、NRF网元、PCF网元、UDM网元、UDR网元、CHF网元或者AF网元等控制面功能采用服务化接口进行交互。比如,AUSF网元对外提供的服务化接口为Nausf;AMF网元对外提供的服务化接口为Namf;SMF网元对外提供的服务化接口为Nsmf;NSSF网元对外提供的服务化接口为Nnssf;NEF网元对外提供的服务化接口为Nnef;NRF网元对外提供的服务化接口为Nnrf;PCF网元对外提供的服务化接口为Npcf;UDM网元对外提供的服务化接口为Nudm;UDR网元对外提供的服务化接口为Nudr;CHF网元对外提供的服务化接口为Nchf;AF网元对外提供的服务化接口为Naf。相关功能描述以及接口描述可以参考23501标准中的5G系统架构(5G system architecture)图,在此不予赘述。
应理解,对于上述各个核心网设备的名称,如上述MME和AMF等,仅是一个名称,对设备本身不构成限定。可以理解的是,在5G网络以及未来其它的网络中,也可以是其他的名称,本申请实施例对此不作具体限定。例如,AMF网元还可以被称为AMF或者AMF实体,在此进行统一说明,以下不再赘述。
可选的,核心网设备可以由一个设备实现,也可以由多个设备共同实现,还可以是一个设备内的一个功能模块,本申请实施例对此不作具体限定。可以理解的是,上述功能模块既可以是硬件设备中的网络元件,也可以是在专用硬件上运行的软件功能模块,或者是平台(例如,云平台)上实例化的虚拟化功能模块。
为了便于理解本申请实施例,下面先对本申请实施例中涉及的术语做简单说明。应理解,这些说明仅为便于理解本申请实施例,而不应对本申请构成任何限定。
1、拜访网络方(visited network operator)
拜访网络方是指,在漫游区域内,向其他运营商的终端设备提供异网漫游服务的运营商。其中,向其他运营商的终端设备提供异网漫游服务的网络,描述为拜访网络(visited network)。示例性的,异网漫游服务,可以是5G核心网异网漫游服务。
2、归属网络方(home network operator)
归属网络方是指,在漫游区域内,通过其他运营商网络,向本网的终端设备提供异网漫游服务的运营商。其中,通过其他运营商网络,向本网的终端设备提供异网漫游服务的网络,描述为归属网络(home network)。示例性的,异网漫游服务,可以是5G核心网异网漫游服务。
3、异网漫游
异网漫游是指,终端设备能够通过接入拜访网络的方式,使用归属网络提供的业务。其中,拜访网络的运营商与终端设备归属网络的运营商不同,但属于相同的国家。其中,异网漫游,也可以称为,国家内漫游(national roaming)。在本申请实施例中,仅以异网漫游为例,进行介绍。
异网漫游运营商双方的接入网、核心网独立建设和管理,移动用户独立管理。提供异网漫游业务的运营商双方基于网间漫游协议,为漫游的终端设备提供相应的服务。异网漫游采用归属路由方式实现,即漫游用户数据回到归属网络,业务由归属网络向终端设备提供。
示例性的,在5G SA场景下,终端设备在漫游区域内,无法接入归属网络,而通过接入拜访网络的方式使用5G业务,如数据业务、基于IMS的语音/视频业务以及短消息业务等。此种情况下,异网漫游,也可以描述为5G核心网异网漫游,或5G核心网漫游。在本申请实施例中,仅以5G核心网异网漫游为例,进行介绍。
4、漫出场景、漫回场景
漫出场景是指,终端设备进入漫游区域,接入拜访网络,通过漫游互通接口与归属网络相连,再由归属网络提供业务。示例性的,拜访网络可以是拜访运营商的5G网络,归属网络可以是归属运营商的5G网络。如图4所示,在5G独立组网方式下,拜访网络和归属网络通过边缘网关(boarder gateway,BG)连接。示例性的,拜访网络中的网元和归属网络中的网元连接情况,如图5所示。
另外,拜访运营商的4G网络不提供5G核心网异网漫游业务,不支持语音回落到拜访运营商的4G网络。
漫回场景是指,终端设备离开漫游区域,搜索到归属网络的信号时,接入到归属网络。
作为一种可能的实现方式,终端设备被配置一张用户识别模块(subscriber identity module,SIM)卡。其中,SIM卡可以作为移动用户的网络身份的标识。SIM卡用于存储用户数据和完成用户身份鉴权。一张SIM卡对应一个移动用户。需要说明的是,SIM卡可以存储用户标识。例如,用户标识可以为:国际移动用户识别码(international mobile subscriber identification number,IMSI)或者签约永久标识(subscription permanent identifier,SUPI)。SIM卡可以通过物理卡片的形式实现,例如标准SIM卡、Mini-SIM卡、Micro SIM卡、以及Nano SIM卡。这种类型的SIM卡又可以称为全球用户识别(universal subscriber identity module,USIM)卡。SIM卡还可以以内置芯片的形式实现,例如嵌入式用户识别模块(embedded-SIM,eSIM)卡。SIM卡还可以以软件的形式实现,本申请实施例对此不作限定。
其中,SIM卡中存储有归属运营商PLMN的标识(identity,ID)。终端设备在开机状态下优先选择归属运营商的PLMN进行驻留和执行业务。终端设备接收接入网设备的系统广播消息。其中,系统广播消息包括PLMN ID。终端设备选网时,通过解析系统广播消息中的PLMN ID,确定运营商,并优先选择归属运营商的PLMN进行驻留。
终端设备在归属运营商的PLMN驻留之后,向归属运营商的核心网设备发送注册(attach或registration)请求消息,之后,核心网设备向终端设备发送等效公用陆地移动网络(equivalent public land mobile network,EPLMN)信息。其中,EPLMN信息包括1个或多个PLMN ID。EPLMN信息中的PLMN ID可以是拜访网络方运营商的PLMN ID。终端设备存储接收到的EPLMN信息,并在后续选网时,将EPLMN信息中包含的PLMN与归属运营商的PLMN等同对待,即认为有相同的选网优先级。例如,当终端设备移动到拜访网络的覆盖范围时,通过解析接入网设备的系统广播消息,获得拜访网络方运营商的PLMN ID。之后,终端设备确定其与在注册接受消息中获得的PLMN ID相同时,终端设备驻留到该拜访网络方运营商的基站,并向拜访网络方运营商的核心网设备发起注册请求,从而接入拜访网络。
对于终端设备而言,终端设备在5G独立组网方式中,执行语音业务有2种方式:
方式1,新空口语音(voice over new radio,VoNR)
VoNR是指,在NR网络中建立语音传输通道,来实现VoNR功能。
方式2,演进的分组系统(evolved packet system,EPS)回退(fallback)
方式2无法通过NR网络建立语音传输通道,终端设备需回退到4G网络,通过4G网络建立语音传输通道,来执行语音业务。此种情况下,5G核心网的AMF网元需要与4G核心网的MME网元之间开通接口。
需要说明的是,方式1和方式2均是基于IMS实现语音业务的。
在5G SA布网初期,运营商的网络不支持VoNR。相应的,已发布的支持5G SA的终端设备也不支持VoNR功能,通过EPS fallback功能进行语音业务。
然而,在5G核心网异网漫游的场景下,拜访网络和归属网络之间开通了AMF网元之间的接口,并未开通拜访网络方的AMF网元与归属网络方的MME网元之间的接口。因此,终端设备无法通过EPS fallback进行语音业务,导致用户无法接听来电,影响用户体验。
有鉴于此,本申请实施例提供两种通信方法,本申请实施例通信方法(如第一种通信方法、或第二种通信方法)可以应用于图1至图5所示的通信系统。
在本申请实施例提供的第一种通信方法中,终端设备向归属网络的核心网设备发送第一信息。其中,第一信息用于指示终端设备支持VoNR或异网漫游。或者,第一信息用于请求获取拜访网络的PLMN信息,拜访网络的运营商与终端设备归属网络的运营商不同。然后,终端设备从核心网设备接收拜访网络的PLMN信息。这样一来,核心网设备确定终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息的情况下,才向终端设备发送拜访网络的PLMN信息。即使拜访网络的运营商与归属网络的运营商不同,终端设备也能够接入拜访网络,通过拜访网络执行语音业务,避免由于终端设备不支持VoNR接入拜访网络后无法进行语音业务的问题。
如图6所示,本申请实施例提供的第一种通信方法600包括如下步骤:
S601、终端设备向归属网络的核心网设备发送第一信息。相应的,归属网络的核心网设备接收来自终端设备的第一信息。
示例性的,核心网设备可以是图2所示的MME,也可以是图3所示的AMF。应理解,随着通信技术的演进,核心网设备也可以有其他的名称,本申请实施例对此不作限定。
其中,第一信息有两种可能的实现方式(即下述方式1和方式2),具体介绍如下:
方式1,第一信息用于指示终端设备支持VoNR或异网漫游。其中,VoNR和异网漫游可以参见名词解释部分,此处不再赘述。
需要说明的是,在本申请实施例中,若终端设备支持异网漫游,则终端设备也支持VoNR功能。由于不支持VoNR的终端设备无法在拜访网络内进行语音业务,因此该类型的终端设备不能驻留到拜访网络,仅能驻留到归属网络,我们可以认为该类终端不支持异网漫游;反之,支持VoNR的终端设备才能驻留到拜访网络通过VoNR进行语音业务,我们可以认为该类终端支持异网漫游。因此,可以将支持异网漫游和支持VoNR看成是等价的。
示例性的,第一信息可以采用直接指示的方式,指示终端设备支持VoNR或异网漫游。或者,第一信息也可以采用间接指示的方式,指示终端设备支持VoNR或异网漫游。示例性的,以表1a为例,表1a示出了一种可能的映射关系。
表1a
字符 特性
A1 支持异网漫游
A2 支持VoNR
在表1a中,支持异网漫游与A1对应,支持VoNR与A2对应。在一些实施例中,若第一信息包括A1,则可以理解为,第一信息用于指示终端设备支持异网漫游。若第一信息包括A2,则可以理解为,第一信息用于指示终端设备支持VoNR。
应理解,第一信息也可以通过其他形式进行指示,本申请实施例对此不作限定。上述仅以终端设备支持VoNR或异网漫游为例,进行介绍。反之,在终端设备不支持VoNR和异网漫游的情况下,第一信息也可以进行相应的指示。例如,若终端设备不支持异网漫游,则第一信息指示终端设备不支持异网漫游。再如,若终端设备不支持VoNR,则第一信息指示终端设备不支持VoNR。类似的,第一信息可以采用直接指示的方式,指示终端设备不支持VoNR或不支持异网漫游。或者,第一信息也可以采用间接指示的方式,指示终端设备不支持VoNR或不支持异网漫游。示例性的,以表1b为例,表1b示出了一种可能的映射关系。
表1b
字符 特性
B1 不支持异网漫游
B2 不支持VoNR
在表1b中,不支持异网漫游与B1对应,不支持VoNR与B2对应。在一些实施例中,若第一信息包括B1,则可以理解为,第一信息用于指示终端设备不支持异网漫游。若第一信息包括B2,则可以理解为,第一信息用于指示终端设备不支持VoNR。
方式2,第一信息用于请求获取拜访网络的PLMN信息。其中,拜访网络的运营商与终端设备归属网络的运营商不同。示例性的,PLMN信息包括PLMN ID。
示例性的,第一信息可以直接指示请求获取拜访网络的PLMN信息,也可以间接指示请求获取拜访网络的PLMN信息,如第一信息通过1比特(bit)来进行指示。例如,该比特取值为1,表示请求获取拜访网络的PLMN信息。相应的,该比特取值为0,表示无需获取拜 访网络的PLMN信息。或者,反之,该比特取值为0,表示请求获取拜访网络的PLMN信息。相应的,该比特取值为1,表示无需获取拜访网络的PLMN信息。或者,第一信息被发送的情况下,表示请求获取拜访网络的PLMN信息。第一信息不发送的情况下,表示无需获取拜访网络的PLMN信息,本申请实施例对此不作限定。
需要说明的是,本申请实施例中所涉及的终端设备向核心网设备发送第一信息,表示的是终端设备向接入网设备发送第一信息,接入网设备再将第一信息发送给核心网设备,由于在该步骤中接入网设备起到透传的作用,为了描述的简洁,在本申请实施例中和附图中直接描述为终端设备向核心网设备发送第一信息。
可选的,结合图2或图3,对第一信息的传输过程进行示例性介绍:
以图2为例,在核心网设备实现为图2中MME的情况下,作为一种可能的实现方式,如图7a所示,S601可以实现为S601a:
S601a、终端设备通过附着请求(attach request)消息向归属网络的MME发送第一信息。相应的,归属网络的MME通过附着请求消息接收来自终端设备的第一信息。
也就是说,附着请求消息携带有第一信息。如此,终端设备在4G注册过程中,即可向MME发送第一信息,以使MME获知终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息,避免MME向不支持VoNR的终端设备发送拜访网络的PLMN信息。
可选的,第一信息可以承载于附着请求消息中指示用户设备的网络能力的字段。例如,第一信息可以承载于指示用户设备的4G网络能力的字段,如用户设备网络能力(UE network capability)的字段,也可以承载于指示用户设备的5G网络能力的字段,如N1接口的用户设备网络能力(N1 UE network capability)的字段。其中,N1接口是终端设备与AMF网元之间进行通信连接的接口,具体可以参见图3的介绍,此处不再赘述。应理解,第一信息还可以承载于附着请求消息中的其他字段,本申请实施例对此不作限定。
示例性的,指示用户设备的网络能力的字段(如UE network capability,或N1 UE network capability字段),可以通过一定数量的预设比特来携带第一信息。其中,预设比特可以包括指示用户设备网络能力的字段中固定比特位的比特,如原处于备用(spare)状态的比特。
参见表2,表2示出了一种可能的UE network capability字段。UE network capability字段中可以携带第一信息的比特如圆圈所示。
表2
Figure PCTCN2022138829-appb-000001
如表2所示,字节1指示信息元素标识(information element identifier,IEI),即UE network capability IEI。字节2指示UE网络能力内容长度(length of UE network capability contents)。字节3携带通用移动通讯系统(evolved packet system,EPS)加密算法的信息,字节4携带EPS完整性算法的信息,字节5携带通用移动通讯系统(universal mobile telecommunications  system,UMTS)加密算法的信息,字节6携带UMTS完整性算法的信息和通用多八位编码字符集(universal multiple-octet coded character set,UCS)的信息。在字节7至字节10(如字节10的比特1至比特5)中,可以包括特性1至特性29的信息。其中,特性1至特性29可以参见相关技术中的介绍,此处不再赘述。在字节10(如字节10的比特6、比特7和比特8)至字节15中,包括处于备用状态的比特。此种情况下,固定比特位的比特包括以下比特中的至少一个:字节10中的部分比特(如字节10中的比特6、比特7和比特8),字节11、字节12、字节13、字节14和字节15中的全部比特。
参见表3,表3示出了一种可能的N1 UE network capability字段。N1 UE network capability字段中可以携带第一信息的比特如圆圈所示。
表3
Figure PCTCN2022138829-appb-000002
如表3所示,字节1指示IEI,即N1 UE network capability IEI。字节2指示N1 UE网络能力内容长度(length of N1 UE network capability contents)。在字节3的比特1至比特6中,可以包括特性1至特性5的信息。其中,特性1至特性5可以参见相关技术中的介绍,此处不再赘述。在字节3(如字节3的比特7和比特8)至字节4中,包括处于备用状态的比特。此种情况下,固定比特位的比特包括以下比特中的至少一个:字节3中的部分比特(如字节3中的比特7和比特8),字节4中的全部比特。
在表2和表3中,对于一个圆圈所示的比特而言,该比特取值为0时,表示携带了第一信息,该比特取值为1时,表示未携带第一信息。或者,反之,该比特取值为1时,表示携带了第一信息,该比特取值为0时,表示未携带第一信息,本申请实施例对此不作限定。
再以图2为例,在核心网设备实现为图2中MME的情况下,作为另一种可能的实现方式,如图7b所示,S601可以实现为S601b:
S601b、终端设备通过跟踪区域更新(tracking area update,TAU)请求消息向归属网络的MME发送第一信息。相应的,归属网络的MME通过TAU请求消息接收来自终端设备的第一信息。
也就是说,TAU请求消息携带有第一信息。如此,终端设备在TAU过程中,即可向MME发送第一信息,以使MME获知终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息,以避免MME向不支持VoNR的终端设备发送拜访网络的PLMN信息。
[根据细则91更正 29.01.2023]
示例性的,移动网络采用跟踪区域(tracking area,TA)的方式来确定终端设备的位置,以便于对终端设备进行位置管理和寻呼。具体的,核心网设备为终端设备配置跟踪区域列表(tracking area list,TA list)。通常,一个TA list包含一个或多个跟踪区域码(tracking area code,TAC),一个TAC用于标识一个TA。一个TA可以包含一个或多个小区。后续,如果终端设备在配置的TA list指示的小区内移动,则不需执行TAU。相应的,当该终端设备有业务到达 后,核心网设备在配置的TA list对应的区域内寻呼此终端设备。反之,若终端设备移出TA list指示的小区,则核心网设备并不获知终端设备最新的位置,终端设备需执行TAU,向核心网设备发送TAU请求消息,使得核心网设备获知该终端设备当前所处TA,进而核心网设备可以更新该终端设备的TA list。
可选的,第一信息可以承载于TAU请求消息中的备用字段,或其他字段,本申请实施例对此不作限定。
以图3为例,在核心网设备实现为图3中AMF的情况下,作为一种可能的实现方式,如图7c所示,S601可以实现为S601c:
S601c、终端设备通过注册请求(registration request)消息向归属网络的AMF发送第一信息。相应的,归属网络的AMF通过注册请求消息接收来自终端设备的第一信息。
也就是说,注册请求消息携带有第一信息。如此,终端设备在5G注册过程中,即可向AMF发送第一信息,以使AMF获知终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息,避免AMF向不支持VoNR的终端设备发送拜访网络的PLMN信息。
可选的,第一信息也可以承载于注册请求消息中指示终端设备的网络能力的字段。例如,第一信息可以承载于指示终端设备的4G网络能力的字段,如S1接口的用户设备网络能力(S1UE network capability)。其中,S1接口是E-UTRAN设备中的eNB与核心网设备之间的接口。S1接口包括S1-MME接口和S1-U接口,如图2所示,S1-MME接口为控制面接口,是E-UTRAN设备与MME之间进行通信连接的接口;S1-U接口为用户面接口,是E-UTRAN设备与SGW之间进行通信连接的接口。第一信息也可以承载于指示终端设备的5G网络能力的字段,比如,移动性管理能力字段,具体可以包括5G移动性管理能力(5G mobility management,5GMM capability)。应理解,第一信息还可以承载于注册请求消息中的其他字段,本申请实施例对此不作限定。
示例性的,上述指示终端设备的网络能力的字段(如S1 UE network capability,或5GMM capability字段),可以通过一定数量的预设比特来携带第一信息。其中,预设比特可以包括指示用户设备网络能力的字段中固定比特位的比特,如原处于备用(spare)状态的比特。
参见表4,表4示出了一种可能的5GMM capability字段。5GMM capability字段中可以携带第一信息的比特如圆圈所示。
表4
Figure PCTCN2022138829-appb-000003
如表4所示,字节1指示IEI,即5GMM capability IEI。字节2指示5GMM能力内容长度(length of 5GMM capability contents)。在字节3至字节6(如字节6中的比特1至比特3)中,可以包括特性1至特性27的信息。其中,特性1至特性27可以参见相关技术中的介绍,此处不再赘述。在字节6(如字节6中的比特4至比特8)至字节15中,包括处于备用状态的比特。此种情况下,固定比特位的比特包括以下比特中的至少一个:字节6中的部分比特(如字节6中的比特4至比特8),字节7、字节8、字节9、字节10、字节11、字节12、字节13、字节14、字节15中的全部比特。在表4中,对于一个圆圈所示的比特而言,该比特取值为0时,表示携带了第一信息,该比特取值为1时,表示未携带第一信息。或者,反之,该比特取值为1时,表示携带了第一信息,该比特取值为0时,表示未携带第一信息,本申请实施例对此不作限定。
再以图3为例,在核心网设备实现为图3中AMF的情况下,作为另一种可能的实现方式,如图7d所示,S601可以实现为S601d:
S601d、终端设备通过安全模式完成(security mode complete,SMC)消息向AMF发送第一信息。相应的,AMF通过安全模式完成消息接收来自终端设备的第一信息。
也就是说,安全模式完成消息携带有第一信息。其中,安全模式完成消息是采用加密密钥进行保护的消息,从而降低第一信息被篡改、泄露的可能性,提高信息传输可靠性。
可选的,第一信息也可以承载于安全模式完成消息中指示终端设备的网络能力的字段。例如,第一信息可以承载于指示终端设备的5G网络能力的字段,比如,移动性管理能力字段,具体可以包括5GMM capability字段,具体可以参见表4的介绍,此处不再赘述。应理解,第一信息还可以承载于安全模式完成消息中的其他字段,本申请实施例对此不作限定。
示例性的,在图7d中,终端设备执行S601d之前,先向AMF发送注册请求消息。相应的,AMF接收来自终端设备的注册请求消息。
其中,注册请求消息携带有隐藏身份信息(subscriber concealed identifier,SUCI)。SUCI是由终端设备生成的。其中,SUCI中包括如下信息中的至少一项:
第一项,用户永久标识类型(subscription permanent identifier,SUPI Type)可以有7个值,用于标识SUCI中加密的SUPI的7种类型。示例性的,当SUPI Type的值为0时,表示SUPI为国际移动用户识别码(international mobile subscriber identification number,IMSI)。其中,IMSI是区别终端设备的标志。IMSI包括移动国家代码(mobile country code,MCC)、移动网络代码(mobile network code,MNC)和移动用户识别号码(mobile subscriber identification number,MSIN)。其中,MCC用于唯一地标识移动用户所属的国家,如我国的MCC为460。MNC用于标识移动用户属于哪个运营商。MSIN用于识别某一移动通信网络中的移动用户。当SUPI Type的值为1时,表示SUPI为网络特定指示符(network specific identifier)。
第二项,家乡网络指示符(home network identifier)。示例性的,当SUPI Type表示SUPI为IMSI时,家乡网络指示符可以包括MCC和MNC。其中,MCC和MNC相结合用于唯一地表示终端设备的网络运营商。
应理解,以上两项信息仅是示例性介绍,SUCI也可以包括其他信息,此处不再一一赘述。
需要说明的是,相比于S601c的注册请求消息,携带SUCI的注册请求消息不携带上述第一信息。
AMF接收到携带SUCI的注册请求消息之后,AMF基于SUCI对终端设备鉴权。然后,AMF向终端设备发送安全模式命令(security mode command)消息。相应的,终端设备接收来自AMF的安全模式命令消息。
其中,安全模式命令消息中携带加密密钥的信息,如AMF和终端设备之间协商使用的密钥。安全模式命令消息中携带的加密密钥用于保护安全模式完成消息,详见S601d的介绍,此处不再赘述。
应理解,在图7a至图7d中,仅是示例性介绍了通过哪些消息来发送第一信息,当然,还可以通过其他消息来发送第一信息,本申请实施例对此不作限定。
S602、核心网设备向终端设备发送拜访网络的PLMN信息。相应的,终端设备接收来自核心网设备的拜访网络的PLMN信息。
其中,S602中的PLMN信息与S601中的PLMN信息一致,此处不再赘述。
示例性的,运营商A在X地区用于异网漫游的PLMN ID是46030,则运营商B的支持VoNR的终端设备在运营商B注册时,接收核心网设备发送的46030。收到46030的终端设备可以选择运营商A的网络,并注册到运营商A的网络。反之,不支持VoNR的终端设备不会收到核心网设备发送的46030,也就无法注册到运营商A的网络。
可选的,结合图2或图3,对拜访网络的PLMN信息的传输过程进行示例性介绍:
以图2所示,在核心网设备实现为图2中MME的情况下,作为一种可能的实现方式,如图7a所示,S602可以实现为S602a:
S602a、MME通过注册接受(attach accept)消息向终端设备发送拜访网络的PLMN信息。相应的,终端设备通过注册接受消息接收来自MME的拜访网络的PLMN信息。
也就是说,注册接受消息携带有拜访网络的PLMN信息。其中,通过注册接受消息发送拜访网络的PLMN信息的具体实现过程,可以参见通过注册接受消息发送EPLMN的介绍,此处不再赘述。
再以图2所示,在核心网设备实现为图2中MME的情况下,作为另一种可能的实现方式,如图7b所示,S602可以实现为S602b:
S602b、MME通过TAU接受消息向终端设备发送拜访网络的PLMN信息。相应的,终端设备通过TAU接受消息接收来自MME的拜访网络的PLMN信息。
也就是说,TAU接受消息携带有拜访网络的PLMN信息。如此,在终端设备支持VoNR,或终端设备请求获取拜访网络的PLMN信息的情况下,终端设备即可在TAU过程中,获取到拜访网络的PLMN信息,以使终端设备通过拜访网络执行语音业务。
以图3为例,在核心网设备实现为图3中AMF的情况下,作为一种可能的实现方式,如图7c和图7d所示,S602可以实现为S602c:
S602c、AMF通过注册接受消息向终端设备发送拜访网络的PLMN信息。相应的,终端设备通过注册接受消息接收来自AMF的拜访网络的PLMN信息。
也就是说,注册接受消息携带有拜访网络的PLMN信息。其中,通过注册接受消息发送拜访网络的PLMN信息的具体实现过程,可以参见通过注册接受消息发送EPLMN的介绍,此处不再赘述。
应理解,在图7a至图7d中,仅是示例性介绍了通过哪些消息来发送拜访网络的PLMN信息,当然,还可以通过其他消息来发送拜访网络的PLMN信息,本申请实施例对此不作限定。
如此,终端设备向核心网设备发送第一信息,以使核心网设备确定终端设备支持VoNR功能,或向核心网设备请求获取拜访网络的PLMN信息,此种情况下,核心网设备才向终端设备发送拜访网络的PLMN信息。即使拜访网络的运营商与归属网络的运营商不同,终端设备也能够接入拜访网络,通过拜访网络执行语音业务,避免由于终端设备不支持VoNR接入拜访网络后无法进行语音业务的问题。
本申请实施例还提供第二种通信方法,在本申请实施例提供的第二种通信方法中,核心网设备确定终端设备支持VoNR。其中,核心网设备是终端设备归属网络的核心网设备。之后,核心网设备向终端设备发送拜访网络的PLMN信息,其中,拜访网络的运营商与终端设备归属网络的运营商不同。这样一来,核心网设备在确定终端设备支持VoNR功能的情况下,才向终端设备发送拜访网络的PLMN信息。即使拜访网络的运营商与归属网络的运营商不同,终端设备也能够接入拜访网络,通过拜访网络执行语音业务,避免由于终端设备不支持VoNR接入拜访网络后无法进行语音业务的问题。
如图8所示,本申请实施例提供的第二种通信方法800包括如下步骤:
S801、核心网设备确定终端设备支持VoNR。
其中,核心网设备是终端设备归属网络中的核心网设备。示例性的,核心网设备可以是图2所示的MME,也可以是图3所示的AMF。应理解,随着通信技术的演进,核心网设备也可以有其他的名称,本申请实施例对此不作限定。
其中,VoNR的介绍可以参见名词解释部分,此处不再赘述。
可选的,S801的实现过程包括如下两种示例(示例1和示例2):
如图9中“示例1”所在的虚线方框所示,S801实现为S801a和S801b:
S801a、接入网设备向核心网设备发送无线能力信息。相应的,核心网设备接收来自接入 网设备的无线能力信息。
其中,无线能力信息指示终端设备的无线能力。示例性的,无线能力信息可以包括UE radio capability info。无线能力信息可以包括IMS参数(IMS-Parameters),该参数的IMS-ParametersFRX-Diff字段可以包括取值为支持(supported)的VoNR字段,以表示终端设备支持VoNR。或者,IMS-ParametersFRX-Diff字段也可以不包括VoNR的字段,或者,VoNR的字段的取值指示不支持(not supported),以表示终端设备不支持VoNR。
作为一种可能的实现方式,参见图10a,图10a示出了一种传输无线能力信息的流程示意图,具体步骤如下:
步骤11,终端设备向核心网设备发送注册请求消息。相应的,核心网设备接收来着终端设备的注册请求消息。
其中,注册请求消息用于发起注册。
示例性的,在核心网设备实现为图2中MME的情况下,注册请求消息用于终端设备注册到4G网络。注册请求消息,也可以描述为附着请求(attach request),如图10b所示。在核心网设备实现为图3中AMF的情况下,注册请求消息用于终端设备注册到5G网络。注册请求消息,也可以记为registration equest,如图10c所示。
步骤12,核心网设备向接入网设备发送能力匹配请求消息。相应的,接入网设备接收来自核心网设备的能力匹配请求消息。
其中,能力匹配请求消息用于请求接入网设备确定终端设备是否支持IMS语音。
示例性的,在核心网设备实现为图2中MME的情况下,接入网设备可以是eNB,能力匹配请求也可以描述为S1接口的应用协议(application protocol,AP)的用户设备能力匹配请求,如记为S1-AP UE Capability match request,如图10b所示。在核心网设备实现为图3中AMF的情况下,接入网设备可以是gNB,能力匹配请求也可以描述为N2接口的用户设备能力匹配请求,如记为N2 UE Capability match request,如图10c所示。
步骤13,接入网设备向终端设备发送能力查询消息。相应的,终端设备接收来自接入网设备的能力查询消息。
其中,能力查询消息用于查询终端设备的无线能力。
示例性的,在核心网设备实现为图2中MME,或图3中AMF的情况下,能力查询消息可以包括用户设备的能力查询消息,即UE Capability enquiry。
步骤14,终端设备向接入网设备的能力信息。相应的,接入网设备接收来自终端设备的能力信息。
其中,能力信息指示终端设备的无线能力。
示例性的,在核心网设备实现为图2中MME,或图3中AMF的情况下,能力信息可以记为UE capability information。
步骤15,接入网设备向核心网设备发送能力匹配响应消息。相应的,核心网设备接收来自接入网设备的能力匹配响应消息。
其中,能力匹配响应消息至少指示终端设备是否支持IMS语音。
示例性的,在核心网设备实现为图2中MME,或图3中AMF的情况下,能力匹配响应消息也可以描述为用户设备无线能力匹配响应(UE radio capability match response)。
由于VoNR是基于IMS语音实现的,所以,在能力匹配响应消息指示终端设备支持IMS 语音的情况下,核心网设备等待接收无线能力信息,即核心网设备先执行S801a,再执行S801b。其中,S801a中的无线能力信息可以是基于步骤14中的能力信息确定的,或者,S801a中的无线能力信息包括步骤14中的能力信息,本申请实施例对此不作限定。
作为另一种可能的实现方式,参见图11,图11示出了一种传输无线能力信息的流程示意图,具体步骤如下:
步骤21,终端设备向核心网设备发送注册请求消息。相应的,核心网设备接收来着终端设备的注册请求消息。
其中,步骤21可以参见步骤11的介绍,此处不再赘述。
步骤22,当核心网设备未保存无线能力信息时,核心网设备向接入网设备发送初始上下文建立请求(initial context setup request)。相应的,接入网设备接收来自核心网设备的初始上下文建立请求。
其中,初始上下文建立请求未携带无线能力信息。无线能力信息指示终端设备的无线能力,可以参见S801a的介绍,此处不再赘述。示例性的,初始上下文建立请求可以携带安全上下文信息,本申请实施例对此不作限定。
此种情况下,接入网设备获知核心网设备未保存终端设备的无线能力信息,之后,接入网设备执行步骤23、步骤24和步骤S801a:
步骤23,接入网设备向终端设备发送能力查询消息。相应的,终端设备接收来自接入网设备的能力查询消息。
其中,步骤23可以参见步骤13的介绍,此处不再赘述。
步骤24,终端设备向接入网设备的能力信息。相应的,接入网设备接收来自终端设备的能力信息。
其中,步骤24可以参见步骤14的介绍,此处不再赘述。
对于接入网设备而言,执行步骤24之后,执行S801a。其中,S801a中的无线能力信息可以是基于步骤24中的能力信息确定的,或者,S801a中的无线能力信息包括步骤24中的能力信息,本申请实施例对此不作限定。对于核心网设备而言,核心网设备先执行S801a,再执行S801b。
应理解,在图11所示的流程示意图中,核心网设备可以实现为图2中MME,此种情况下,接入网设备可以是eNB,如图10b所示。核心网设备也可以实现为图3中AMF,此种情况下,接入网设备可以是gNB,如图10c所示,此处不再赘述。
S801b、核心网设备根据无线能力信息,确定终端设备支持VoNR。
示例性的,以无线能力信息包括IMS参数为例,当该参数的IMS-ParametersFRX-Diff字段包括取值为支持(supported)的VoNR字段时,核心网设备确定终端设备支持VoNR。
应理解,仍以无线能力信息包括IMS-ParametersFRX-Diff字段为例,当IMS-ParametersFRX-Diff字段不包括VoNR的字段,或者,VoNR的字段的取值指示不支持(not supported)时,核心网设备确定终端设备不支持VoNR。
如此,通过图9中“示例1”所在的虚线方框所示的S801a和S801b,核心网设备即可基于无线能力信息,来自主确定终端设备支持VoNR功能。
如图9中“示例2”所在的虚线方框所示,S801实现为S801c和S801d:
S801c、接入网设备向核心网设备发送指示信息。相应的,核心网设备接收来自接入网设 备的指示信息。
其中,指示信息指示终端设备支持VoNR,具体可以参见S601的介绍,此处不再赘述。
示例性的,指示信息指示的特性是基于终端设备的能力信息确定的。仍以能力信息中的IMS参数为例,当该参数的IMS-ParametersFRX-Diff字段包括取值为支持(supported)的VoNR字段时,接入网设备确定终端设备支持VoNR。相应的,指示信息指示终端设备支持VoNR。当IMS-ParametersFRX-Diff字段不包括VoNR的字段,或者,VoNR的字段的取值指示不支持(not supported)时,接入网设备确定终端设备不支持VoNR。相应的,指示信息指示终端设备不支持VoNR。
可选的,如图12a所示,S801c可以替换为如下步骤:接入网设备通过无线能力匹配响应消息向核心网设备发送指示信息。相应的,核心网设备通过无线能力匹配响应消息接收来自接入网设备的指示信息。
示例性的,无线能力匹配响应消息通过预设数量的备用字段来承载指示信息。
也就是说,无线能力匹配响应消息携带上述指示信息,从而使得核心网设备获取到上述指示信息。
应理解,上述仅以无线能力匹配响应消息作为示例,对指示信息的承载进行介绍。当然,指示信息也可以通过其他消息进行传输,或承载于独立的消息进行传输,本申请实施例对此不作限定。
需要说明的是,接入网设备可以自主执行S801c,也可以响应于核心网设备的请求,而执行S801c。此种情况下,如图12a所示,核心网设备在执行S801c之前,还执行S801e:
S801e、核心网设备向接入网设备发送第一请求消息。相应的,接入网设备接收来自核心网设备的第一请求消息。
其中,第一请求消息请求获取指示信息。S801e中的指示信息与S801c中的指示信息一致,此处不再赘述。
可选的,S801e可以替换为如下步骤:核心网设备通过能力信息指示消息向接入网设备发送第一请求消息。相应的,接入网设备通过能力信息指示消息接收来自核心网设备的第一请求消息。
示例性的,能力信息指示消息通过预设数量的备用字段来携带第一请求消息。
示例性的,结合图2或图3,对第一请求消息的传输过程进行介绍:在核心网设备实现为图2中MME的情况下,接入网设备可以是eNB,能力信息指示消息可以包括S1接口的应用协议的用户设备能力信息指示(S1-AP UE capability info indication),如图12b所示。在核心网设备实现为图3中AMF的情况下,接入网设备可以是gNB,能力信息指示消息可以包括N2接口的用户设备能力信息指示(N2 UE capability info indication),如图12c所示。
也就是说,能力信息指示消息携带上述第一请求消息,从而向接入网设备发送上述指示信息。
应理解,上述仅以能力信息指示消息作为示例,对第一请求消息的承载进行介绍。当然,第一请求消息也可以通过其他消息进行传输,或承载于独立的消息进行传输,本申请实施例对此不作限定。
S801d、核心网设备根据指示信息,确定终端设备支持VoNR。
示例性的,在指示信息指示终端设备支持VoNR的情况下,核心网设备即可确定终端设 备支持VoNR。
应理解,在指示信息指示终端设备不支持VoNR的情况下,核心网设备即可确定终端设备不支持VoNR。
如此,通过图9中“示例2”所在的虚线方框所示的S801c和S801d,接入网设备来确定终端设备是否支持VoNR功能,再告知核心网设备,以使核心网设备获知终端设备是否支持VoNR功能。
对于核心网设备而言,在确定终端设备支持VoNR的情况下,核心网设备执行S802,反之,在确定终端设备不支持VoNR的情况下,核心网设备不执行S802。
S802、核心网设备向终端设备发送拜访网络的PLMN信息。相应的,终端设备接收来自核心网设备的拜访网络的PLMN信息。
其中,S802可以参见S602的介绍,此处不再赘述。
也就是说,核心网设备在确定终端设备支持VoNR功能的情况下,才向终端设备发送拜访网络的PLMN信息。即使拜访网络的运营商与归属网络的运营商不同,终端设备也能够接入拜访网络,通过拜访网络执行语音业务,避免由于终端设备不支持VoNR接入拜访网络后无法进行语音业务的问题。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的,本申请实施例还提供了通信装置,该通信装置可以为上述方法实施例中的网元,或者包含上述网元的装置,或者为可用于网元的部件。可以理解的是,该通信装置为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
示例性的,图13示出了一种通信装置1300的结构示意图。该通信装置1300包括处理单元1301、发送单元1302和接收单元1303。
一种可能的示例中,以通信装置1300为终端设备为例,处理单元1301用于支持终端设备执行图6中终端设备需要执行的其他处理操作。发送单元1302用于支持终端设备执行图6中的S601,和/或本申请实施例中终端设备需要执行的其他发送操作。接收单元1303用于支持终端设备执行图6中的S602,和/或本申请实施例中终端设备需要执行的其他接收操作。
再一种可能的示例中,以通信装置1300为终端设备为例,处理单元1301用于支持终端设备执行图8中终端设备需要执行的其他处理操作。发送单元1302用于支持终端设备执行图8中终端设备需要执行的其他发送操作。接收单元1303用于支持终端设备执行图8中的S802,和/或本申请实施例中终端设备需要执行的其他接收操作。
一种可能的示例中,以通信装置1300为核心网设备为例,处理单元1301用于支持核心网设备执行图6中核心网设备需要执行的其他处理操作。发送单元1302用于支持核心网设备执行图6中的S602,和/或本申请实施例中核心网设备需要执行的其他发送操作。接收单元1303用于支持核心网设备执行图6中的S601,和/或本申请实施例中核心网设备需要执行的其他接收操作。
再一种可能的示例中,以通信装置1300为核心网设备为例,处理单元1301用于支持核 心网设备执行图8中的S801,和/或本申请实施例中核心网设备需要执行的其他处理操作。发送单元1302用于支持核心网设备执行图8中的S802,和/或本申请实施例中核心网设备需要执行的其他发送操作。接收单元1303用于支持核心网设备执行图8中核心网设备需要执行的其他接收操作。
可选的,该通信装置1300还可以包括存储单元1304,用于存储通信装置的程序代码和数据,数据可以包括不限于原始数据或者中间数据等。
其中,处理单元1301可以是处理器或控制器,例如可以是CPU,通用处理器,专用集成电路(application specific integrated circuit,ASIC),现场可编程逻辑门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。
发送单元1302可以是通信接口、发送器或发送电路等,其中,该通信接口是统称,在具体实现中,该通信接口可以包括多个接口,例如可以包括:终端设备与核心网设备之间的接口和/或其他接口。
接收单元1303可以是通信接口、接收器或接收电路等,其中,该通信接口是统称,在具体实现中,该通信接口可以包括多个接口,例如可以包括:终端设备与核心网设备之间的接口和/或其他接口。
发送单元1302和接收单元1303可以是物理上或者逻辑上实现为同一个单元。
存储单元1304可以是存储器。
当处理单元1301为处理器,发送单元1302和接收单元1303为通信接口,存储单元1304为存储器时,本申请实施例所涉及的通信装置可以为图14所示。
参阅图14所示,该通信装置包括:处理器1401、通信接口1402、存储器1403。可选的,通信装置还可以包括总线1404。其中,通信接口1402、处理器1401以及存储器1403可以通过总线1404相互连接;总线1404可以是外设部件互连标准(peripheral component interconnect,PCI)总线或扩展工业标准结构(extended industry standard architecture,EISA)总线等。所述总线1404可以分为地址总线、数据总线、控制总线等。为便于表示,图14中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
可选的,本申请实施例还提供一种携带计算机指令的计算机程序产品,当该计算机指令在计算机上运行时,使得计算机执行上述实施例所介绍的方法。
可选的,本申请实施例还提供一种计算机可读存储介质,所述计算机可读存储介质存储计算机指令,当该计算机指令在计算机上运行时,使得计算机执行上述实施例所介绍的方法。
可选的,本申请实施例还提供一种芯片,包括:处理电路和收发电路,处理电路和收发电路用于实现上述实施例所介绍的方法。其中,处理电路用于执行相应方法中的处理动作,收发电路用于执行相应方法中的接收/发送的动作。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算 机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带)、光介质(例如,数字视频光盘(digital video disc,DVD))、或者半导体介质(例如固态硬盘(solid state drive,SSD))等。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述模块的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个模块或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或模块的间接耦合或通信连接,可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个设备上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
通过以上的实施方式的描述,所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在可读取的存储介质中,如计算机的软盘,硬盘或光盘等,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述的方法。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,在本申请揭露的技术范围内的变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。

Claims (31)

  1. 一种通信方法,其特征在于,包括:
    终端设备向归属网络的核心网设备发送第一信息,其中,所述第一信息用于指示所述终端设备支持新空口语音VoNR或异网漫游,或者,所述第一信息用于请求获取拜访网络的公共陆地移动网络PLMN信息,所述拜访网络的运营商与所述终端设备归属网络的运营商不同;
    所述终端设备从所述核心网设备接收所述拜访网络的PLMN信息。
  2. 根据权利要求1所述的方法,其特征在于,所述终端设备通过附着请求消息向所述归属网络的核心网设备发送所述第一信息。
  3. 根据权利要求1所述的方法,其特征在于,所述终端设备通过注册请求消息向所述归属网络的核心网设备发送所述第一信息。
  4. 根据权利要求2或3所述的方法,其特征在于,所述第一信息承载于指示用户设备网络能力的字段。
  5. 根据权利要求2、3或4任一项所述的方法,其特征在于,所述第一信息承载于预设比特,其中,所述预设比特包括指示用户设备网络能力的字段中固定比特位的比特。
  6. 根据权利要求1、2、4或5任一项所述的方法,其特征在于,所述第一信息承载于以下其中一项:
    用户设备网络能力字段,或者,
    N1接口的用户设备网络能力字段。
  7. 根据权利要求1、3、4或5任一项所述的方法,其特征在于,所述第一信息承载于以下其中一项:
    移动管理能力字段,或者,
    S1接口的用户设备网络能力字段。
  8. 根据权利要求1所述的方法,其特征在于,所述终端设备通过安全模式完成消息向所述归属网络的核心网设备发送所述第一信息。
  9. 根据权利要求1所述的方法,其特征在于,所述终端设备通过跟踪区更新TAU请求消息向所述归属网络的核心网设备发送所述第一信息。
  10. 一种注册方法,其特征在于,包括:
    核心网设备接收来自终端设备的第一信息,其中,所述第一信息用于指示所述终端设备支持新空口语音VoNR或异网漫游,或者,所述第一信息用于请求获取拜访网络的公共陆地移动网络PLMN信息,所述拜访网络的运营商与所述终端设备归属网络的运营商不同,所述核心网设备是所述终端设备归属网络的核心网设备;
    所述核心网设备根据所述第一信息向所述终端设备发送所述拜访网络的PLMN信息。
  11. 根据权利要求10所述的方法,其特征在于,所述核心网设备通过附着请求消息接收来自所述终端设备的所述第一信息。
  12. 根据权利要求10所述的方法,其特征在于,所述核心网设备通过注册请求消息接收来自所述终端设备的所述第一信息。
  13. 根据权利要求11或12所述的方法,其特征在于,所述第一信息承载于指示用户设备网络能力的字段。
  14. 根据权利要求11、12或13任一项所述的方法,其特征在于,所述第一信息承载于预设比特,所述预设比特包括指示用户设备网络能力的字段中固定比特位的比特。
  15. 根据权利要求10、11、13或14任一项所述的方法,其特征在于,所述第一信息承载于以下其中一项:
    用户设备网络能力字段,或者,
    N1接口的用户设备网络能力字段。
  16. 根据权利要求10、12、13或14任一项所述的方法,其特征在于,所述第一信息承载于以下其中一项:
    移动管理能力字段,或者,
    S1接口的用户设备网络能力字段。
  17. 根据权利要求10所述的方法,其特征在于,所述核心网设备通过安全模式完成消息接收来自所述终端设备的所述第一信息。
  18. 根据权利要求10所述的方法,其特征在于,所述核心网设备通过跟踪区更新TAU请求消息接收来自所述终端设备的所述第一信息。
  19. 一种通信方法,其特征在于,包括:
    核心网设备确定终端设备支持新空口语音VoNR,其中,所述核心网设备是所述终端设备归属网络的核心网设备;
    所述核心网设备向所述终端设备发送拜访网络的公共陆地移动网络PLMN信息,其中,所述拜访网络的运营商与所述终端设备归属网络的运营商不同。
  20. 根据权利要求19所述的方法,其特征在于,所述方法还包括:
    所述核心网设备接收来自接入网设备的无线能力信息,其中,所述无线能力信息指示所述终端设备的无线能力;
    所述核心网设备确定终端设备支持VoNR,包括:
    所述核心网设备根据所述无线能力信息,确定所述终端设备支持VoNR。
  21. 根据权利要求20所述的方法,其特征在于,所述方法还包括:
    当所述核心网设备未保存所述无线能力信息时,所述核心网设备向所述接入网设备发送初始上下文建立请求,其中,所述初始上下文建立请求未携带所述无线能力信息。
  22. 根据权利要求19所述的方法,其特征在于,所述方法还包括:
    所述核心网设备接收来自接入网设备的指示信息,其中,所述指示信息指示所述终端设备支持VoNR;
    所述核心网设备确定终端设备支持VoNR,包括:
    所述核心网设备根据所述指示信息,确定所述终端设备支持VoNR。
  23. 根据权利要求22所述的方法,其特征在于,所述核心网设备通过无线能力匹配响应消息接收来自所述接入网设备的所述指示信息。
  24. 根据权利要求22或23所述的方法,其特征在于,所述方法还包括:
    所述核心网设备向所述接入网设备发送第一请求消息,其中,所述第一请求消息请求获取所述指示信息。
  25. 根据权利要求24所述的方法,其特征在于,所述核心网设备通过终端设备能力信息指示消息向所述接入网设备发送所述第一请求消息。
  26. 根据权利要求19至25任一项所述的方法,其特征在于,所述核心网设备通过注册接受消息向所述终端设备发送所述拜访网络的PLMN信息。
  27. 根据权利要求19至26任一项所述的方法,其特征在于,所述核心网设备包括移动性管理实体MME,或移动管理功能AMF网元。
  28. 一种通信装置,包括用于执行如权利要求1至9中的任一项所述方法的单元,或包括用于执行如权利要求10至18中的任一项所述方法的单元,或包括用于执行如权利要求19至27中的任一项所述方法的单元。
  29. 一种通信装置,其特征在于,包括处理器和接口电路,所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置,所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至9中任一项所述的方法,或用于实现如权利要求10至18中任一项所述的方法,或用于实现如权利要求19至27中任一项所述的方法。
  30. 一种计算机可读存储介质,其特征在于,所述存储介质中存储有计算机程序或指令,当所述计算机程序或指令被通信装置执行时,实现如权利要求1至9中任一项所述的方法,或实现如权利要求10至18中任一项所述的方法,或实现如权利要求19至27中任一项所述的方法。
  31. 一种通信系统,其特征在于,包括:接入网设备和核心网设备;其中,
    所述接入网设备,用于向所述核心网设备发送第一信息,其中,所述第一信息指示终端设备的无线能力,或所述第一信息指示所述终端设备支持新空口语音VoNR;
    所述核心网设备,用于接收来自所述接入网设备的所述第一信息,其中,所述核心网设备是所述终端设备归属网络的核心网设备;
    所述核心网设备,还用于根据所述第一信息确定所述终端设备支持VoNR;
    所述核心网设备,还用于向所述终端设备发送拜访网络的公共陆地移动网络PLMN信息,其中,所述拜访网络的运营商与所述终端设备归属网络的运营商不同。
PCT/CN2022/138829 2021-12-27 2022-12-13 通信方法及装置 WO2023124991A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202111618289 2021-12-27
CN202111618289.X 2021-12-27
CN202210051820.8A CN116367139A (zh) 2021-12-27 2022-01-17 通信方法及装置
CN202210051820.8 2022-01-17

Publications (1)

Publication Number Publication Date
WO2023124991A1 true WO2023124991A1 (zh) 2023-07-06

Family

ID=86926182

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/138829 WO2023124991A1 (zh) 2021-12-27 2022-12-13 通信方法及装置

Country Status (2)

Country Link
CN (1) CN116367139A (zh)
WO (1) WO2023124991A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020076839A1 (en) * 2018-10-09 2020-04-16 Qualcomm Incorporated Techniques for improving vnr-to-volte fallback
WO2020190875A1 (en) * 2019-03-15 2020-09-24 Apple Inc. Method, computer readable medium and apparatus to determine support of ims voice service in a 5g mobile network
CN113543247A (zh) * 2021-03-15 2021-10-22 中国电信股份有限公司 网络选择系统、方法、存储介质与电子设备
WO2021233588A1 (en) * 2020-05-18 2021-11-25 Telefonaktiebolaget Lm Ericsson (Publ) Voice service handling of a ue in a 5g system
CN115134892A (zh) * 2022-08-30 2022-09-30 荣耀终端有限公司 基于异网漫游的接入方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020076839A1 (en) * 2018-10-09 2020-04-16 Qualcomm Incorporated Techniques for improving vnr-to-volte fallback
WO2020190875A1 (en) * 2019-03-15 2020-09-24 Apple Inc. Method, computer readable medium and apparatus to determine support of ims voice service in a 5g mobile network
WO2021233588A1 (en) * 2020-05-18 2021-11-25 Telefonaktiebolaget Lm Ericsson (Publ) Voice service handling of a ue in a 5g system
CN113543247A (zh) * 2021-03-15 2021-10-22 中国电信股份有限公司 网络选择系统、方法、存储介质与电子设备
CN115134892A (zh) * 2022-08-30 2022-09-30 荣耀终端有限公司 基于异网漫游的接入方法和装置

Also Published As

Publication number Publication date
CN116367139A (zh) 2023-06-30

Similar Documents

Publication Publication Date Title
US10003957B2 (en) Method and apparatus for supporting location privacy protection in wireless access system supporting small cell environment
US9526119B2 (en) Methods and apparatus for multiple data packet connections
JP2018538747A (ja) 移動通信システムにてコアネットワークを選択する方法及び装置
US11917503B2 (en) SMS via NAS carried by non-cellular access
EP4149166A1 (en) Network accessing method, apparatus, and system
CA3075971C (en) Transfer of protected configuration data from home mobile network
US20160149916A1 (en) Method and Nodes for Authorizing Network Access
EP4027744A1 (en) Communication method, communication apparatus, and storage medium
WO2023124457A1 (zh) 选择网络的方法和装置
EP3111611B1 (en) A node and a method for enabling network access authorization
WO2022259830A1 (en) Method of user equipment (ue) and user equipment (ue)
TWI819507B (zh) 啟用snpn的使用者設備的參數處理方法及使用者設備
WO2023124991A1 (zh) 通信方法及装置
KR20220152950A (ko) 네트워크 슬라이스 승인 제어(nsac) 발견 및 로밍 향상들
US20170201959A1 (en) Data transmission method and base station
CN115299168A (zh) 用于切换的方法和装置
EP3800950A1 (en) Method and device for managing user data
US20240205813A1 (en) Method and apparatus to access core networks via gateway functions
EP4322618A1 (en) Method and apparatus to access core networks via gateway functions
WO2023040728A1 (zh) 一种网元的选择方法、通信装置及通信系统
US12021931B2 (en) BSF service registration and discovery enhancement
US20230362862A1 (en) Multi-usim device accessing services of a second cellular network through a first cellular network via a gateway
WO2023286778A1 (en) Core network node, network node, method for core network node and method for network node
WO2023051427A1 (zh) 通信的方法和装置
WO2023142777A1 (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: 22914246

Country of ref document: EP

Kind code of ref document: A1