Communication method, user equipment, network device, and communication system

Abstract

The embodiments of the present disclosure relate to a communication method, a user equipment, a network device, and a communication system. The communication method comprises: a user equipment (UE) sending an attach request to a first network device, and receiving a first radio frame, which is fed back by the first network device, wherein the first radio frame at least carries one of the following parameters: a first parameter or a second parameter, the first parameter identifies whether the first network device supports voice over new radio (VoNR), and the second parameter identifies whether the first network device supports voice over wireless fidelity (WiFi); and executing a registration operation according to the first radio frame. Therefore, a voice service with a stable call quality is selected according to information about capabilities, which are supported by the first network device, so as to avoid voice interruption during a call, thereby improving the quality of the voice service and the quality of a data service.

Description

Communication method, user equipment, network equipment and communication system Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method, user equipment, network equipment, and a communication system. Background Art

[0002] In the early stages of Stand Alone (SA) network deployment, the network is still being finalized and some functions may be unstable. Therefore, a mechanism is needed to prevent the voice and data experience under SA from being affected.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a communication method, user equipment, network equipment, and communication system to improve the voice call quality and data service quality under SA.

[0005] In one aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0006] The user equipment UE sends an attach request to the first network device, and receives a first radio frame fed back by the first network device; wherein the first radio frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports VoNR; the second parameter indicates whether the first network device supports Wi-Fi voice;

[0007] A registration operation is performed according to the first radio frame.

[0008] On the other hand, an embodiment of the present disclosure further provides a communication method, the method comprising:

[0009] The first network device sends a first radio frame to the UE in response to the attach request of the UE;

[0010] The first radio frame carries at least one of the following parameters: a first parameter or a second parameter;

[0011] The first parameter identifies whether the first network device supports VoNR;

[0012] The second parameter identifies whether the first network device supports WiFi voice.

[0013] On the other hand, an embodiment of the present disclosure further provides a communication method, the method comprising:

[0014] The second network device receives a third registration request sent by the user equipment UE requesting to register with Vowifi;

[0015] The third registration request is sent by the UE when it is determined that the first network device does not support VoNR but supports WiFi voice.

[0016] On the other hand, an embodiment of the present disclosure further provides a user equipment, the user equipment comprising:

[0017] A first sending module is configured to send an attachment request to a first network device and receive a first radio frame fed back by the first network device; wherein the first radio frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports VoNR; and the second parameter indicates whether the first network device supports Voice over WiFi.

[0018] A registration module is configured to perform a registration operation according to the first wireless frame.

[0019] On the other hand, an embodiment of the present disclosure further provides a network device, wherein the network device is a first network device, and the first network device includes:

[0020] A second sending module, configured to send a first radio frame to the UE in response to an attach request of the UE;

[0021] The first radio frame carries at least one of the following parameters: a first parameter or a second parameter;

[0022] The first parameter identifies whether the first network device supports VoNR;

[0023] The second parameter identifies whether the first network device supports WiFi voice.

[0024] On the other hand, an embodiment of the present disclosure further provides a network device, wherein the network device is a second network device, and the second network device includes:

[0025] A receiving module, configured to receive a third registration request sent by a user equipment UE requesting to register with Vowifi;

[0026] The third registration request is sent by the UE when it is determined that the first network device does not support VoNR but supports WiFi voice.

[0027] On the other hand, an embodiment of the present disclosure further provides a user equipment, including:

[0028] one or more processors;

[0029] The processor calls the instruction to enable the user equipment to execute the communication method described in the embodiment of the present disclosure.

[0030] On the other hand, an embodiment of the present disclosure further provides a network device, wherein the network device is a first network device, including:

[0031] one or more processors;

[0032] The processor calls an instruction to enable the first network device to execute the communication method described in the embodiment of the present disclosure.

[0033] On the other hand, an embodiment of the present disclosure further provides a network device, which is a second network device and includes:

[0034] one or more processors;

[0035] The processor calls the instruction to enable the second network device to execute the communication method described in the embodiment of the present disclosure.

[0036] An embodiment of the present disclosure also provides a communication system, including a user device, a first network device, and a second network device; wherein the user device is configured to implement the communication method described in the embodiment of the present disclosure, the first network device is configured to implement the communication method described in the embodiment of the present disclosure, and the second network device is configured to implement the method described in the embodiment of the present disclosure.

[0037] The embodiment of the present disclosure further provides a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the communication method as described in the embodiment of the present disclosure.

[0038] In the embodiment of the present disclosure, the UE performs a registration operation based on the capability information supported by the first network device, and when subsequently initiating or receiving a voice call, it either performs VoNR voice, Vowifi voice, or falls back to LTE; based on the capability information supported by the first network device, a voice service with stable call quality is selected to avoid voice interruption during the call, thereby improving the quality of voice service and data service.

[0039] Additional aspects and advantages of the embodiments of the present disclosure will be given in part in the following description, which will become apparent from the following description or be learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0041] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0042] FIG2 is one of exemplary interaction diagrams of a method provided according to an embodiment of the present disclosure;

[0043] FIG3 is a second exemplary interaction diagram of the method provided according to an embodiment of the present disclosure;

[0044] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure;

[0045] FIG5 is a second flow chart of the communication method provided in an embodiment of the present disclosure;

[0046] FIG6 is a third flow chart of the communication method provided in an embodiment of the present disclosure;

[0047] FIG7 is a schematic diagram of the structure of a user equipment proposed in an embodiment of the present disclosure;

[0048] FIG8 is a schematic structural diagram of a first network device proposed in an embodiment of the present disclosure;

[0049] FIG9 is a schematic structural diagram of a second network device proposed in an embodiment of the present disclosure;

[0050] FIG10 is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure;

[0051] FIG11 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0052] The embodiments of the present disclosure provide a communication method, user equipment, network equipment, and a communication system.

[0053] In a first aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0054] The user equipment UE sends an attach request to the first network device, and receives a first radio frame fed back by the first network device; wherein the first radio frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports Voice over New Radio (VoNR); and the second parameter indicates whether the first network device supports Voice over Wireless Fidelity (WiFi).

[0055] A registration operation is performed according to the first radio frame.

[0056] In the above embodiment, the UE performs a registration operation according to the capability information supported by the first network device, and when subsequently initiating or receiving a voice call, it either performs VoNR voice, Vowifi voice, or falls back to LTE; according to the capability information supported by the first network device, a voice service with stable call quality is selected to avoid voice interruption during the call.

[0057] In combination with some embodiments of the first aspect, in some embodiments, the attachment request identifier indicates that the UE requests to attach to a new radio interface NR.

[0058] In the above embodiment, when the UE requests to attach to the NR, the first network device feeds back its capability information to the UE, so that the UE performs a registration operation according to the capability information supported by the first network device, thereby providing a network basis for the UE to subsequently initiate or receive voice calls.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, performing a registration operation according to the first radio frame includes at least one of the following:

[0060] The first parameter indicates that the first network device supports VoNR, and a first registration request is sent to the first network device requesting registration with NR;

[0061] The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device does not support Wi-Fi voice, and sending a second registration request to the first network device requesting registration to NR;

[0062] The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device supports WiFi voice, and a third registration request is sent to the second network device requesting registration to Wireless Fidelity Voice Vowifi.

[0063] In the above embodiment, the first parameter indicates that the first network device 102 supports VoNR, then UE101 can initiate a registration request on NR and send a first registration request to the first network device 102 requesting registration to NR; the first parameter indicates that the first network device 102 does not support VoNR and the second parameter indicates that the first network device 102 does not support WiFi voice, then UE101 can initiate a registration request on NR; if the first network device 102 does not support VoNR and WiFi voice, when UE101 initiates or receives a voice call, UE101 falls back to the LTE network and establishes a voice transmission channel through the LTE network to carry voice services.

[0064] In combination with some embodiments of the first aspect, in some embodiments, after sending a first registration request to the first network device requesting registration with the NR, the method includes:

[0065] To initiate a voice call or receive a voice call, the UE resides on the independent network SA and performs a VoNR voice call.

[0066] In the above embodiment, when the UE initiates or accepts a voice call, the UE will remain on SA and implement data services through SA, that is, SA data + VoNR voice, so that both data services and voice services are retained in the NR network, ensuring the quality of data communication and voice transmission.

[0067] In combination with some embodiments of the first aspect, in some embodiments, after sending a second registration request to the first network device requesting registration with the NR, the method includes:

[0068] To initiate a voice call or receive a voice call, the UE falls back to the Long Term Evolution (LTE) network and performs Evolved Packet System (EPSFB) fallback for the voice call.

[0069] In the above embodiment, when the UE initiates or receives a voice call, the NR instructs the UE to access LTE through a switching or redirection process, and uses the IP Multimedia Subsystem (IMS) network to provide VoLTE voice services, thereby avoiding voice interruption caused by switching between UE and LTE and affecting user experience.

[0070] In combination with some embodiments of the first aspect, in some embodiments, after sending a third registration request to the first network device requesting registration with Vowifi, the method includes:

[0071] To initiate a voice call or receive a voice call, the UE resides on the SA and performs a Vowifi voice call.

[0072] In the above embodiment, the UE initiates the VoWifi registration process, retains the data service in the NR network, and registers the voice service in the WiFi network. Subsequently, when the UE initiates or receives a voice call, the UE will remain on SA, that is, SA data service + VoWifi voice service, so that the voice service remains in the NR high RAT state, providing users with a continuous high data experience and high-quality voice experience.

[0073] In a second aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0074] The first network device sends a first radio frame to the UE in response to the attach request of the UE;

[0075] The first radio frame carries at least one of the following parameters: a first parameter or a second parameter;

[0076] The first parameter identifies whether the first network device supports VoNR;

[0077] The second parameter identifies whether the first network device supports WiFi voice.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the attachment request identifier indicates that the UE requests to attach to the NR.

[0079] In conjunction with some embodiments of the second aspect, in some embodiments, after sending the first radio frame to the UE, the method further includes:

[0080] receiving a first registration request or a second registration request sent by the UE requesting registration with the NR;

[0081] The first parameter indicates that the first network device supports VoNR, and the UE sends the first registration request;

[0082] The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device does not support WiFi voice, and the UE sends the second registration request.

[0083] In combination with some embodiments of the second aspect, in some embodiments, after receiving the first registration request sent by the UE requesting registration to the NR, the method includes:

[0084] The UE initiates a voice call or receives a voice call, initiates the EPSFB process of the UE, instructs the UE to fall back to the LTE network, and performs the EPSFB voice call.

[0085] In a third aspect, an embodiment of the present disclosure further provides a communication method, the method comprising:

[0086] The second network device receives a third registration request sent by the user equipment UE requesting to register with Vowifi;

[0087] The third registration request is sent by the UE when it is determined that the first network device does not support VoNR but supports WiFi voice.

[0088] In a fourth aspect, an embodiment of the present disclosure further provides a user device, wherein the user device includes a first sending module and at least one of the sending modules; wherein the user device is used to execute the optional implementation method of the first aspect.

[0089] In a fifth aspect, an embodiment of the present disclosure further provides a network device, which is a first network device and includes: a second sending module; wherein the above-mentioned first network device is used to execute the optional implementation method of the second aspect.

[0090] In a sixth aspect, an embodiment of the present disclosure further provides a network device, wherein the network device is a second network device, and the second network device includes:

[0091] A receiving module, configured to receive a third registration request sent by a user equipment UE requesting to register with Vowifi;

[0092] The third registration request is sent by the UE when it is determined that the first network device does not support VoNR but supports WiFi voice.

[0093] In a seventh aspect, an embodiment of the present disclosure further provides a user equipment, including:

[0094] one or more processors;

[0095] The processor calls the instruction to enable the user equipment to execute the optional implementation method of the first aspect.

[0096] In an eighth aspect, an embodiment of the present disclosure further provides a network device, wherein the network device is a first network device, including:

[0097] one or more processors;

[0098] The processor calls an instruction to enable the first network device to execute an optional implementation of the second aspect.

[0099] In the ninth aspect, an embodiment of the present disclosure further provides a communication system, comprising a user device, a first network device, and a second network device; wherein the user device is configured to perform the optional implementation method as described in the first aspect, the first network device is configured as the optional implementation method as described in the second aspect, and the second network device is configured as the optional implementation method as described in the third aspect.

[0100] In the tenth aspect, an embodiment of the present disclosure further provides a storage medium storing instructions, which, when executed on a communication device, enables the communication device to execute the optional implementation methods described in the first, second, and third aspects.

[0101] In an eleventh aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

[0102] In a twelfth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first, second, and third aspects.

[0103] In a thirteenth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first, second, and third aspects above.

[0104] It is understandable that the above-mentioned user equipment, network equipment, communication system, storage medium, program product, computer program, chip or chip system are all used to perform the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0105] The embodiments of the present disclosure provide a communication method, a user device, a network device, and a communication system. In some embodiments, the terms communication method, signal transmission method, wireless frame transmission method, etc. are interchangeable, and the terms information processing system, communication system, etc. are interchangeable.

[0106] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0107] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0108] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0109] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0110] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0111] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0112] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0113] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0114] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0115] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0116] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0117] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0118] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0119] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0120] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0121] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0122] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0123] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0124] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0125] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0126] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0127] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0128] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0129] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0130] As shown in FIG1 , a communication system 100 includes a user equipment (UE) 101 , a first network device 102 , and a second network device 103 .

[0131] In some embodiments, UE101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0132] Specifically, the UE 101 or the second network device 103 may be a terminal device with a wireless fidelity (WiFi) chip. Optionally, the site device 101 may support multiple WLAN standards such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, 802.11bf, and 802.11bn, as well as the next generation 802.11 protocol, but is not limited thereto.

[0133] In some embodiments, the first network device 102 and the second network device 103 may include at least one of an access network device and a core network device.

[0134] In some embodiments, the access network device may be an access point AP for a mobile terminal to enter a wired network. The AP is equivalent to a bridge connecting a wired network and a wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet. Specifically, the AP may be a terminal device or a second network device with a wireless fidelity chip. Optionally, the AP may support multiple WLAN standards such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a, 802.11bf, 802.11bn, and support the next generation 802.11 protocol, but is not limited thereto. In some embodiments, the core network device may be a device including one or more network elements, or may be multiple devices or a group of devices, each including all or part of the above one or more network elements. The network element may be virtual or physical. The core network, for example, includes at least one of the Evolved Packet Core (EPC), the 5G Core Network (5GCN), and the Next Generation Core (NGC).

[0135] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0136] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0137] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other resource determination methods, and next-generation systems based on and extending these systems. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0138] The various embodiments of the present disclosure can also be applied to wireless local area networks (WLANs), such as those using the 802.11 series of protocols. In a WLAN, a Basic Service Set (BSS) is a fundamental component of a WLAN. A BSS network consists of station devices with some association within a specific coverage area. One scenario of association is that stations communicate directly with each other in an ad hoc network, which is called an Independent Basic Service Set (IBSS). Another more common scenario is that in a BSS network, there is only one central station dedicated to managing the BSS, called an access point, and all other STAs in the network are associated with it. Other stations in the BSS network that are not the central station are called terminals, also called non-AP STAs. Terminals and non-AP STAs are collectively referred to as STAs. When describing STAs, there is no need to distinguish between APs and non-AP STAs. In the same BSS network, due to distance, transmission power, and other factors, a STA cannot detect other STAs that are farther away, and the two STAs are each other's hidden nodes.

[0139] 2 to 4 are interactive schematic diagrams illustrating a communication method according to embodiments of the present disclosure.

[0140] As shown in FIG2 , the above method includes:

[0141] In step 201, user equipment UE101 sends an attach request to the first network device 102; optionally, the attach request indicates that the UE requests to attach to a new radio (NR).

[0142] The "NR" described in the embodiments of this disclosure may also be referred to as 5G or 5G NR, but those skilled in the art will understand its meaning. The technical solutions described in the embodiments of this disclosure are applicable to 5G NR systems and to subsequent evolution systems of 5G NR systems.

[0143] After UE101 initiates an Attach request on NR, the first network device 102 responds to the Attach request and feeds back a first radio frame to UE101, such as an Attach Accept message.

[0144] Among them, the first wireless frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports voice over new radio (VoNR); the second parameter indicates whether the first network device supports WiFi voice.

[0145] Specifically, VoNR is a technical solution for carrying voice over 5G NR. The UE resides on NR, and both voice and data services are carried on the NR network. When the UE moves to the edge of NR coverage, the voice service is switched to long-term evolution (LTE). VoNR has a short call setup time and data services can still be transmitted at high speed during voice calls, giving users a better user experience. It is understandable that in the embodiments of the present disclosure, the voice call can be a video call.

[0146] The second parameter indicates whether the first network device 102 supports WiFi voice, that is, whether the first network device 102 is VoWiFi. Specifically, VoWiFi (Voice over WiFi, wireless fidelity voice or WiFi calling) refers to the use of a user terminal with VoWiFi capability to make voice and video calls in a WiFi environment through traditional dial-up methods.

[0147] Optionally, the first parameter is, for example, "ims_Vonr_support", and the "ims_Vonr_support" parameter is set to 1, indicating that the first network device supports VoNR; the "ims_Vonr_support" parameter is set to 0, indicating that the first network device does not support VoNR. The second parameter is, for example, "(ims_Vops_N3GPP", and the "(ims_Vops_N3GPP" parameter is set to 1, indicating that the first network device supports WiFi voice; the "(ims_Vops_N3GPP" parameter is set to 0, indicating that the first network device does not support WiFi voice.

[0148] Step 202: Receive a first wireless frame fed back by the first network device 102; wherein the first wireless frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports VoNR; the second parameter indicates whether the first network device supports WiFi voice.

[0149] Among them, UE101 receives the first radio frame and obtains at least one of the first parameter or the second parameter carried in the first radio frame; determines whether the first network device 102 supports VoNR through the first parameter; and / or determines whether the first network device 102 supports VoWiFi through the second parameter.

[0150] Step 203: Perform a registration operation according to the first radio frame.

[0151] UE101 initiates a registration operation based on the first parameter and / or the second parameter of the first radio frame. For example, if it is determined by the first parameter that the first network device 102 supports VoNR, UE101 can initiate a registration request on NR and complete the registration process; in this way, when UE101 initiates or accepts a voice call, the UE will remain on SA and implement data services through SA, that is, SA data + VoNR voice, so that both data services and voice services are retained in the NR network, ensuring data communication and voice quality. For another example, if it is determined by the first parameter that the first network device 102 does not support VoNR but supports VoWiFi, a VoWiFi registration process can be initiated to retain the data service in the NR network and register the voice service in the WiFi network. Subsequently, when the UE initiates or accepts a voice call, the UE will remain on SA, that is, SA data service + VoWiFi voice service, improving the voice service quality through VoWiFi while ensuring the data service quality.

[0152] In some embodiments, step 203 includes step 2031 , step 2032 or step 2033 .

[0153] Step 2031: The first parameter indicates that the first network device supports VoNR, and a first registration request is sent to the first network device to request registration with NR.

[0154] Among them, the first parameter indicates that the first network device 102 supports VoNR, then UE101 can initiate a registration request on NR, send a first registration request requesting registration to NR to the first network device 102, and the first network device 102 receives the first registration request requesting registration to NR sent by the UE101. For example, if the ims_Vonr_support parameter is set to 1, it indicates that the first network device 102 supports VoNR, and UE101 can initiate a registration request on NR and complete the registration process.

[0155] In some embodiments, after step 2031, the method includes:

[0156] To initiate a voice call or receive a voice call, the UE resides on the SA and performs a VoNR voice call.

[0157] In this way, when UE101 initiates or receives a voice call, the UE will remain on SA and implement data services through SA, that is, SA data + VoNR voice, so that both data services and voice services are retained in the NR network, ensuring the quality of data communication and voice transmission.

[0158] Step 2032: The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device does not support WiFi voice, and a second registration request is sent to the first network device requesting registration to NR.

[0159] Among them, the first parameter indicates that the first network device 102 does not support VoNR and the second parameter indicates that the first network device 102 does not support WiFi voice, then UE101 can initiate a registration request on NR, and send a second registration request requesting registration to NR to the first network device 102, and the first network device 102 receives the second registration request sent by the UE101 requesting registration to NR; and when UE101 initiates or accepts a voice call, the UE can fall back to the LTE network and realize data services and voice services through the LTE network.

[0160] For example, if the ims_Vonr_support parameter is set to 0, it indicates that the first network device 102 does not support VoNR; and the ims_Vops_N3GPP parameter is set to 0, it indicates that the first network device 102 does not support WiFi voice either. Then, UE101 can initiate a registration request on NR and complete the registration process.

[0161] In some embodiments, after step 2032, after sending a second registration request to the first network device requesting registration with the NR, the method includes:

[0162] To initiate a voice call or receive a voice call, the UE falls back to the LTE network and performs EPSFB voice call.

[0163] Among them, EPSFB stands for evolved packet system (EPS) fall back (FB). If the first network device 102 does not support VoNR and WiFi voice, when UE 101 initiates or receives a voice call, UE 101 falls back to the LTE network and establishes a voice transmission channel through the LTE network to carry voice services. That is, LTE data + EPSFB voice call, which enables data services to be retained in the NR network and voice services to fall back to LTE, ensuring data communication and voice quality.

[0164] In this way, when UE101 initiates or receives a voice call, NR instructs UE101 to access LTE through a switching or redirection process, and uses the IMS (IP Multimedia Subsystem) network to provide VoLTE voice services, avoiding voice interruption caused by switching between UE101 and LTE and NR, which affects the user experience.

[0165] Step 2033: The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device supports WiFi voice, and a third registration request is sent to the second network device to request registration to Vowifi.

[0166] Optionally, in an embodiment of the present disclosure, the second network device 103 is, for example, an N3IWF (Non-3GPP InterWorking Function) device, which is responsible for connecting an untrusted non-3GPP access network to the 5G core network.

[0167] Among them, UE101 determines through the first parameter that the first network device 102 does not support VoNR, and determines through the second parameter that it supports VoWiFi, then VoWiFi can be used as a voice supplement to SA. During the call, there is no need to EPSFB to a low RAT (Radio Access Technology) state.

[0168] For example, if the ims_Vonr_support parameter is set to 0, it indicates that the first network device 102 does not support VoNR; and the ims_Vops_N3GPP parameter is set to 1, it indicates that the first network device 102 supports WiFi voice, then UE101 can initiate a registration request on VoWiFi and complete the registration process.

[0169] In some embodiments, after step 2033, the method includes:

[0170] To initiate a voice call or receive a voice call, the UE resides on the SA and performs a Vowifi voice call.

[0171] Among them, when the first network device 102 does not support VoNR but supports WiFi voice, UE101 initiates the Vowifi registration process, retains the data service in the NR network, and registers the voice service to the WiFi network. Subsequently, when the UE initiates or accepts a voice call, the UE will remain on SA, that is, SA data service + Vowifi voice service, so that the voice service remains in the NR high RAT state, providing users with a continuous high data experience and high-quality voice experience.

[0172] Optionally, referring to FIG3 , FIG3 shows a schematic diagram of a communication process of UE 101; as shown in FIG3 , it includes:

[0173] Step 301, NR attachment request; UE101 sends an attachment request to the first network device 102.

[0174] Step 302, NR admission request: UE 101 receives an attach accept message from the first network device 102. For example, the NR responds to the attach accept message and carries relevant network parameters, such as the ims_Vops_N3GPP parameter (supporting IMS voice services in 5G networks, including EPSFB and VoNR), the ims_Vops_3GPP parameter (supporting WiFi voice), and the ims_Vonr_support parameter indicating whether VoNR is supported.

[0175] Step 303: Determine whether the first network device supports VoNR. If so, execute step 304; otherwise, execute step 306. For example, the UE determines whether the network supports VoNR based on the ims_Vonr_support parameter sent by the network. If the network supports VoNR, such as ims_Vonr_support = 1, execute steps 304 to 305; if the network does not support VoNR, such as ims_Vonr_support = 0, execute steps 306 to 310.

[0176] Step 304, first registration request; the first parameter indicates that the first network device 102 supports VoNR, then UE101 can initiate a registration request on NR and send a first registration request to the first network device 102 requesting registration to NR.

[0177] For example, if the network supports VoNR, that is, the ims_Vonr_support parameter is set to 1, it indicates that the first network device 102 supports VoNR, and the UE 101 can initiate a registration request on NR.

[0178] Step 305, SA data service + VoNR voice service; when UE101 initiates or accepts a voice call, the UE will remain on SA and implement data service through SA, that is, SA data + VoNR voice, so that both data service and voice service are retained in the NR network, ensuring the quality of data communication and voice transmission.

[0179] Step 306: Determine whether the first network device supports Wi-Fi voice. If so, execute step 309; otherwise, execute step 307. For example, the UE determines whether the network supports Wi-Fi voice based on the ims_Vops_N3GPP parameter issued by the network. If the network does not support Wi-Fi voice, such as ims_Vops_N3GPP = 0, execute steps 307 to 308; if the network supports Wi-Fi voice, such as ims_Vops_N3GPP = 1, execute steps 309 to 310.

[0180] Step 307, second registration request; if the first network device 102 does not support VoNR and WiFi voice, when UE101 initiates or receives a voice call, UE101 falls back to the LTE network and establishes a voice transmission channel through the LTE network to carry voice services.

[0181] For example, if the ims_Vonr_support parameter is set to 0, indicating that the first network device 102 does not support VoNR; and the ims_Vops_N3GPP parameter is set to 0, indicating that the first network device 102 also does not support Wi-Fi voice, then UE 101 can initiate a registration request on NR and complete the registration process. Subsequently, when UE 101 initiates or receives a voice call, UE 101 falls back to the LTE network.

[0182] Step 308, LTE data + EPSFB voice; when UE101 initiates or receives a voice call, NR instructs UE101 to access LTE through a switching or redirection process, that is, LTE data + EPSFB voice call, so that the data service is retained in the NR network and the voice service is fallen back to LTE, ensuring the quality of data communication and voice.

[0183] Step 309, third registration request; UE101 determines through the first parameter that the first network device 102 does not support VoNR, and determines through the second parameter that it supports VoWiFi, then VoWiFi can be used as a voice supplement to SA.

[0184] For example, if the ims_Vonr_support parameter is set to 0, it indicates that the first network device 102 does not support VoNR; and the ims_Vops_N3GPP parameter is set to 1, it indicates that the first network device 102 supports WiFi voice, then UE101 can initiate a registration request on VoWiFi and complete the registration process.

[0185] Step 310: SA data service + VoWi-Fi voice service. When the UE initiates or accepts a voice call, the UE will remain in SA, i.e., SA data service + VoWi-Fi voice service, so that the voice service remains in the NR high RAT state, providing users with a continuous high data experience and high-quality voice experience.

[0186] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0187] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0188] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0189] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0190] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0191] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0192] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 201 can be implemented as an independent embodiment, and step 202 can be implemented as an independent embodiment; the combination of step 201 and step 202 can be implemented as an independent embodiment, the combination of step 202 and step 203 can be implemented as an independent embodiment, the combination of step 201, step 202, and step 203 can be implemented as an independent embodiment, the combination of step 201, step 202, and step 203 can be implemented as an independent embodiment, the combination of step 201, step 202, and step 2033 can be implemented as an independent embodiment, the combination of step 201, step 202, and step 2033 can be implemented as an independent embodiment, and the combination of step 201, step 202, and step 2033 can be implemented as an independent embodiment, but is not limited thereto.

[0193] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0194] FIG4 is a flowchart of a communication method according to an embodiment of the present disclosure.

[0195] As shown in FIG4 , the above method may be applied to user equipment 101, and the above method includes:

[0196] In step 401, a user equipment (UE) sends an attach request to a first network device and receives a first radio frame fed back by the first network device; wherein the first radio frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports Voice over New Radio (VoNR); the second parameter indicates whether the first network device supports Voice over Wireless Fidelity (WiFi); optionally, in an embodiment of the present disclosure, the authentication between the first network device and the second network device includes:

[0197] Step 402: Perform a registration operation according to the first wireless frame.

[0198] Optionally, in an embodiment of the present disclosure, the attachment request identifier indicates that the UE requests to attach to a new radio interface NR.

[0199] Optionally, in the embodiment of the present disclosure, step 402 includes:

[0200] Step 4021: The first parameter indicates that the first network device supports VoNR, and a first registration request is sent to the first network device requesting registration with NR.

[0201] Step 4022: The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device does not support Wi-Fi voice. A second registration request is sent to the first network device requesting registration with NR.

[0202] In step 4023, the first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device supports Wi-Fi voice, and a third registration request is sent to the second network device requesting registration to Wi-Fi voice Vowifi.

[0203] Optionally, in the embodiment of the present disclosure, after sending the first registration request to the first network device requesting registration with the NR, the method includes:

[0204] Step 4024: Initiate a voice call or receive a voice call. The UE resides on the independent network SA and performs a VoNR voice call.

[0205] Optionally, in the embodiment of the present disclosure, after sending the second registration request to the first network device requesting registration with the NR, the method includes:

[0206] Step 4025: Initiate a voice call or receive a voice call, the UE falls back to the Long Term Evolution (LTE) network, and performs Evolved Packet System Fallback (EPSFB) voice call.

[0207] Optionally, in the embodiment of the present disclosure, after sending the third registration request to the first network device requesting registration with Vowifi, the method includes:

[0208] Step 4026: Initiate a voice call or receive a voice call. The UE resides on the SA and performs a Vowifi voice call.

[0209] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 401 can be implemented as an independent embodiment, and step 402 can be implemented as an independent embodiment; the combination of step 401 and step 402 can be implemented as an independent embodiment, the combination of step 401, step 402 and step 403 can be implemented as an independent embodiment, the combination of step 401, step 402 and step 4021 can be implemented as an independent embodiment, the combination of step 401, step 402 and step 4022 can be implemented as an independent embodiment, the combination of step 401, step 402 and step 4023 can be implemented as an independent embodiment, the combination of step 4021 and step 4024 can be implemented as an independent embodiment, the combination of step 4022 and step 4023 can be implemented as an independent embodiment, and the combination of step 4023 and step 4026 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0210] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4 .

[0211] FIG5 is a second flowchart of a communication method according to an embodiment of the present disclosure.

[0212] As shown in FIG5 , the above method may be applied to the first network device 102 , and the above method includes:

[0213] Step 501: A first network device sends a first radio frame to a UE in response to an attach request from the UE.

[0214] The first radio frame carries at least one of the following parameters: a first parameter or a second parameter;

[0215] The first parameter identifies whether the first network device supports VoNR;

[0216] The second parameter identifies whether the first network device supports WiFi voice.

[0217] Optionally, in an embodiment of the present disclosure, the attachment request identifies that the UE requests to attach to the NR.

[0218] Optionally, in the embodiment of the present disclosure, after sending the first radio frame to the UE, the method further includes:

[0219] Step 502: Receive a first registration request or a second registration request sent by the UE requesting registration with the NR;

[0220] The first parameter indicates that the first network device supports VoNR, and the UE sends the first registration request;

[0221] The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device does not support WiFi voice, and the UE sends the second registration request.

[0222] Optionally, in the embodiment of the present disclosure, after receiving the first registration request sent by the UE requesting registration with the NR, the method includes:

[0223] Step 503: The UE initiates a voice call or receives a voice call, initiates the EPSFB process of the UE, instructs the UE to fall back to the LTE network, and performs the EPSFB voice call.

[0224] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 501 may be implemented as an independent embodiment, step 502 may be implemented as an independent embodiment, and step 503 may be implemented as an independent embodiment; the combination of step 501 and step 502 may be implemented as an independent embodiment, and the combination of step 502 and step 503 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0225] FIG6 is a third flowchart of a communication method according to an embodiment of the present disclosure.

[0226] As shown in FIG6 , the above method can be applied to the second network device 103, including:

[0227] Step 601: The second network device receives a third registration request sent by a user equipment UE requesting to register with Vowifi;

[0228] The third registration request is sent by the UE when it is determined that the first network device does not support VoNR but supports WiFi voice.

[0229] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments.

[0230] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a second network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0231] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0232] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0233] FIG7 is a schematic diagram of the structure of a user equipment proposed in an embodiment of the present disclosure. As shown in FIG7 , the user equipment 700 may include: a first sending module 701 and a registration module 702 .

[0234] In some embodiments, the above-mentioned first sending module 701 is used to send an attachment request to the first network device and receive a first wireless frame fed back by the first network device; wherein, the first wireless frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports VoNR; the second parameter indicates whether the first network device supports WiFi voice.

[0235] The registration module 702 is configured to perform a registration operation according to the first radio frame.

[0236] Optionally, the above-mentioned first sending module 701 is used to execute at least one of the communication steps (for example, step 201, step 301, step 401, but not limited to this) performed by the user equipment 101 in any of the above methods, and the registration module 702 is used to execute steps 203, step 2031, step 2032, step 2033, step 304, step 307, step 309, step 402, step 4021, step 4022, and step 4023, which are not repeated here.

[0237] FIG8 is a schematic diagram of the structure of a first network device according to an embodiment of the present disclosure. As shown in FIG8 , the first network device 200 may include: a second sending module 801 .

[0238] In some embodiments, the second sending module 801 is configured to send a first radio frame to the UE in response to an attach request of the UE;

[0239] The first radio frame carries at least one of the following parameters: a first parameter or a second parameter;

[0240] The first parameter identifies whether the first network device supports VoNR;

[0241] The second parameter identifies whether the first network device supports WiFi voice.

[0242] Optionally, the second sending module 801 is configured to execute at least one of the communication steps (such as step 501 , but not limited thereto) executed by the first network device 102 in any of the above methods, which will not be described in detail here.

[0243] FIG9 is a schematic diagram of the structure of the second network device proposed in an embodiment of the present disclosure. As shown in FIG9 , the second network device 900 may include: a receiving module 901, configured to receive a third registration request sent by a user equipment UE requesting to register with Vowifi;

[0244] The third registration request is sent by the UE when it is determined that the first network device does not support VoNR but supports WiFi voice.

[0245] Optionally, the receiving module 901 is configured to execute at least one of the communication steps (eg, step 601 , but not limited thereto) executed by the second network device 103 in any of the above methods, which will not be described in detail herein.

[0246] Figure 10 is a schematic diagram of the structure of a terminal 1000 (e.g., user equipment) proposed in an embodiment of the present disclosure. Terminal 1000 can be a chip, chip system, or processor that supports a second network device in implementing any of the above methods, or a chip, chip system, or processor that supports a terminal in implementing any of the above methods. Terminal 1000 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0247] As shown in Figure 10, terminal 1000 includes one or more processors 1001. Processor 1001 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Terminal 1000 is used to perform any of the above methods.

[0248] In some embodiments, the terminal 1000 further includes one or more memories 1002 for storing instructions. Optionally, all or part of the memory 1002 may be located outside the terminal 1000.

[0249] In some embodiments, the terminal 1000 further includes one or more transceivers 1004. When the terminal 1000 includes one or more transceivers 1004, the transceiver 1004 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 201, step 202, step 2031, step 2032, step 2033, step 301, step 302, step 304, step 307, step 309, step 401, step 4021, step 4022, step 4023, step 501, step 502, step 601, but not limited thereto), and the processor 1001 performs at least one of the other steps (for example, step 203, step 303, step 305, step 306, step 308, step 4024, step 4025, step 4026, step 503, but not limited thereto).

[0250] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0251] In some embodiments, terminal 1000 may include one or more interface circuits 1003. Optionally, interface circuit 1003 is connected to memory 1002. Interface circuit 1003 may be configured to receive signals from memory 1002 or other devices, and may be configured to send signals to memory 1002 or other devices. For example, interface circuit 1003 may read instructions stored in memory 1002 and send the instructions to processor 1001.

[0252] The terminal 1000 described in the above embodiments may be a communication device such as a user device, but the scope of the terminal 1000 described in the present disclosure is not limited thereto, and the structure of the terminal 1000 may not be limited by FIG10. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a second network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0253] FIG11 is a schematic diagram of the structure of a chip 1100 according to an embodiment of the present disclosure. If the terminal 1000 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 1100 shown in FIG11 , but the present disclosure is not limited thereto.

[0254] The chip 1100 includes one or more processors 1101 , and the chip 1100 is configured to execute any of the above methods.

[0255] In some embodiments, chip 1100 further includes one or more 1103. Optionally, interface circuit 1103 is connected to memory 1102. Interface circuit 1103 can be used to receive signals from memory 1102 or other devices, and interface circuit 1103 can be used to send signals to memory 1102 or other devices. For example, interface circuit 1103 can read instructions stored in memory 1102 and send the instructions to processor 1101.

[0256] In some embodiments, the interface circuit 1103 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step 201, step 202, step 2031, step 2032, step 2033, step 301, step 302, step 304, step 307, step 309, step 401, step 4021, step 4022, step 4023, step 501, step 502, step 601, but not limited to these), and the processor 1101 executes at least one of the other steps (for example, step 203, step 303, step 305, step 306, step 308, step 4024, step 4025, step 4026, step 503, but not limited to these).

[0257] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0258] In some embodiments, the chip 1100 further includes one or more memories 1102 for storing instructions. Alternatively, all or part of the memory 1102 may be external to the chip 1100.

[0259] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the terminal 1000, the terminal 1000 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0260] The present disclosure also provides a program product, which, when executed by the terminal 1000, enables the terminal 1000 to perform any of the above methods. Optionally, the program product is a computer program product.

[0261] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication method, characterized in that: The method comprises: The user equipment UE sends an attachment request to the first network device, and receives a first radio frame fed back by the first network device; wherein the first radio frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports new air interface voice VoNR; the second parameter indicates whether the first network device supports wireless fidelity WiFi voice; A registration operation is performed according to the first radio frame.

2. The communication method according to claim 1, characterized in that: The attach request identifier indicates that the UE requests to attach to a new radio interface NR.

3. The communication method according to claim 1 or 2, characterized in that: The performing a registration operation according to the first radio frame includes at least one of the following: The first parameter indicates that the first network device supports VoNR, and a first registration request is sent to the first network device requesting registration with NR; The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device does not support WiFi voice, and sending a second registration request to the first network device requesting registration to NR; The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device supports WiFi voice, and sends a third registration request to the second network device requesting registration to Wireless Fidelity Voice Vowifi.

4. The communication method according to claim 3, characterized in that: After sending the first registration request to the first network device requesting registration with the NR, the method includes: To initiate a voice call or receive a voice call, the UE resides on an independent network SA and performs a VoNR voice call.

5. The communication method according to claim 3, characterized in that: After sending a second registration request to the first network device requesting registration to the NR, the method includes: To initiate a voice call or receive a voice call, the UE falls back to the Long Term Evolution LTE network and performs an Evolved Packet System Fallback EPSFB voice call.

6. The communication method according to claim 3, characterized in that: After sending the third registration request for registering to Vowifi to the first network device, the method includes: To initiate a voice call or receive a voice call, the UE resides on the SA and performs a Vowifi voice call.

7. A communication method, characterized in that: The method comprises: The first network device sends a first radio frame to the UE in response to the attachment request of the UE; The first radio frame carries at least one of the following parameters: a first parameter or a second parameter; The first parameter identifies whether the first network device supports VoNR; The second parameter identifies whether the first network device supports WiFi voice.

8. The communication method according to claim 7, characterized in that: The attach request identifies that the UE requests to attach to the NR.

9. The communication method according to claim 7 or 8, characterized in that: After sending the first radio frame to the UE, the method further includes: receiving a first registration request or a second registration request sent by the UE requesting registration with the NR; The first parameter indicates that the first network device supports VoNR, and the UE sends the first registration request; The first parameter indicates that the first network device does not support VoNR, and the second parameter indicates that the first network device does not support WiFi voice, and the UE sends the second registration request.

10. The communication method according to claim 9, characterized in that: After receiving the first registration request sent by the UE to request registration to the NR, the method includes: The UE initiates a voice call or receives a voice call, initiates the EPSFB process of the UE, instructs the UE to fall back to the LTE network, and performs the EPSFB voice call.

11. A communication method, characterized in that: The method comprises: The second network device receives a third registration request sent by the user equipment UE to request registration to Vowifi; The third registration request is sent by the UE when it is determined that the first network device does not support VoNR but supports WiFi voice.

12. A user equipment, characterized in that: The user equipment comprises: A first sending module is configured to send an attachment request to a first network device, and receive a first wireless frame fed back by the first network device; wherein the first wireless frame carries at least one of the following parameters: a first parameter or a second parameter; the first parameter indicates whether the first network device supports VoNR; the second parameter indicates whether the first network device supports WiFi voice; A registration module is used to perform a registration operation according to the first wireless frame.

13. A network device, the network device being a first network device, characterized in that: The first network device comprises: A second sending module, configured to send a first radio frame to the UE in response to an attachment request of the UE; The first radio frame carries at least one of the following parameters: a first parameter or a second parameter; The first parameter identifies whether the first network device supports VoNR; The second parameter identifies whether the first network device supports WiFi voice.

14. A network device, the network device being a second network device, characterized in that: The second network device comprises: A receiving module, configured to receive a third registration request sent by a user equipment UE to request registration to Vowifi; The third registration request is sent by the UE when it is determined that the first network device does not support VoNR but supports WiFi voice.

15. A user equipment, characterized in that: include: one or more processors; The processor calls the instruction to enable the user equipment to execute the communication method according to any one of claims 1 to 6.

16. A network device, the network device being a first network device, characterized in that: include: one or more processors; The processor calls the instruction to enable the first network device to execute the communication method described in any one of claims 7 to 10.

17. A network device, the network device being a second network device, characterized in that: include: one or more processors; The processor calls the instruction to enable the second network device to execute the communication method according to claim 11.

18. A communication system, characterized in that: It includes a user device, a first network device, and a second network device; wherein the user device is configured to implement the communication method described in any one of claims 1 to 6, the first network device is configured to implement the communication method described in any one of claims 7 to 10, and the second network device is configured to implement the communication method described in claim 11.

19. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the communication method according to any one of claims 1 to 6, or executes the communication method according to any one of claims 7 to 10, or executes the communication method according to claim 11.

Images