CN113260042A - Terminal equipment attachment method and terminal equipment - Google Patents

Terminal equipment attachment method and terminal equipment Download PDF

Info

Publication number
CN113260042A
CN113260042A CN202110604806.1A CN202110604806A CN113260042A CN 113260042 A CN113260042 A CN 113260042A CN 202110604806 A CN202110604806 A CN 202110604806A CN 113260042 A CN113260042 A CN 113260042A
Authority
CN
China
Prior art keywords
target network
terminal device
request message
attachment
attach
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN202110604806.1A
Other languages
Chinese (zh)
Inventor
赵瑞卿
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honor Device Co Ltd
Original Assignee
Honor Device Co Ltd
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 Honor Device Co Ltd filed Critical Honor Device Co Ltd
Priority to CN202110604806.1A priority Critical patent/CN113260042A/en
Publication of CN113260042A publication Critical patent/CN113260042A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Landscapes

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

Abstract

The application provides an attachment method of a terminal device and the terminal device, which can flexibly adjust registered services according to actual conditions so as to recover the language conversation capability in time and improve user experience. The method comprises the following steps: the terminal equipment determines whether the target network equipment supports voice service; under the condition that the target network equipment does not support voice service, after the terminal equipment sends a first attachment request message, receiving a first attachment success message from the target network equipment, wherein the first attachment request message carries configuration parameters taking data as a center; when the terminal equipment executes any one operation of starting up, card preparation, restarting or tracking area updating TAU, sending a second attachment request message to the target network equipment, wherein the second attachment request message carries configuration parameters taking voice as a center; in case the voice service of the target network device is resumed, the terminal device receives a second attach success message from the target network device.

Description

Terminal equipment attachment method and terminal equipment
Technical Field
The present application relates to the field of mobile communications, and in particular, to a method for attaching a terminal device and a terminal device.
Background
When a terminal device supporting voice service and/or data service is powered on, it initiates an attach (attach) request, and carries configuration parameters of the terminal device in signaling of the attach request, where the configuration parameters may be data-centric (data _ centric) or voice-centric (voice _ centric).
At present, before a terminal device initiates an attach request, configuration parameters of the terminal device may be loaded according to a Subscriber Identity Module (SIM) card inserted when the terminal device is powered on, so as to implement different operators to load different configurations to register a network.
However, the current attachment method cannot adjust the registered service according to the actual situation, and is poor in flexibility and poor in user experience.
Disclosure of Invention
The application provides an attachment method of a terminal device and the terminal device, which can flexibly adjust registered services according to actual conditions so as to recover the language conversation capability in time and improve user experience.
In a first aspect, an attachment method for a terminal device is provided, including: the terminal equipment determines whether the target network equipment supports voice service; under the condition that the target network equipment does not support voice service, the terminal equipment sends a first attachment request message to the target network equipment, wherein the first attachment request message carries configuration parameters taking data as a center; the terminal equipment receives a first attachment success message from the target network equipment; when the terminal equipment executes any one operation of starting up, card preparation, restarting or tracking area updating TAU, the terminal equipment sends a second attachment request message to target network equipment, wherein the second attachment request message carries configuration parameters taking voice as a center; and under the condition that the voice service of the target network equipment is recovered, the terminal equipment receives a second attachment success message from the target network equipment.
According to the method and the device, the terminal device sends the first attachment request carrying the configuration parameters with data as the center to the target network device under the condition that the target network device is determined not to support the voice service, the attachment is successful, when the terminal device executes any one of startup, card preparation, restart or TAU, the configuration with data as the center is switched to be centered on voice, the second attachment request is restarted, and under the condition that the voice service of the target network device is recovered, the terminal device can flexibly adjust the registered service according to the actual condition, so that the voice conversation capability can be recovered in time, and the user experience is improved.
It should be understood that the first attach request and the second attach request include a manner in which the terminal device initiates registration, and the registration manner is joint registration, that is, the terminal device simultaneously registers voice service and data service.
It should also be understood that, in general, the configuration of the terminal device is data-centric, and there is no requirement that the network device side must have voice services. However, if the terminal device does not re-register the voice service after the network device side recovers the voice service, the terminal device may not perform the voice call.
With reference to the first aspect, in some implementations of the first aspect, after the terminal device sends the second attach request message to the target network device, the method further includes: and under the condition that the target network equipment still does not support the voice service, the terminal equipment receives a second attachment failure message from the target network.
It should be understood that after the terminal device receives the second attach failure message from the target network, the terminal device may directly switch from the voice-centric configuration to the data-centric configuration, and resend the attach request to the target network.
With reference to the first aspect, in some implementations of the first aspect, the determining, by the terminal device, whether the target network device supports a voice service includes: the terminal equipment acquires indication information from the big data platform, wherein the indication information is used for indicating whether the target network equipment supports voice service; the terminal equipment determines whether the target network equipment supports the voice service or not based on the indication information.
The big data platform can be used for counting the abnormal network-resident state of the terminal equipment under the current network. When the terminal equipment fails to stay in the network, the abnormal information before the network is recovered can be uploaded to the cloud big data platform, the cloud big data platform can analyze the received data, the condition of the network equipment which fails to stay in the network of the terminal equipment is obtained, other terminal equipment which needs to stay in the cell is informed, and the cell is abnormal and the network-staying failure can be caused.
According to the embodiment of the application, before the terminal equipment sends the attachment request to the target network equipment, the indication information of whether the target network supports the voice service or not can be obtained in advance through the big data platform, the condition that the target network does not support the voice service can be effectively avoided, the terminal equipment sends the attachment request which takes voice as a center to the target network equipment, and signaling interaction between the terminal equipment and the network equipment is effectively reduced.
With reference to the first aspect, in some implementations of the first aspect, the determining, by the terminal device, whether the target network device supports a voice service includes: the terminal equipment sends a third attachment request message to target network equipment, wherein the third attachment request message carries configuration parameters taking voice as a center; the terminal equipment receives a third attachment success message or a third attachment failure message from the target network equipment; the terminal device determines whether the target network device supports voice service based on the third attach success message or the third attach failure message.
It should be understood that the attach success message indicates that the target network device supports the voice service, and when the attach failure message carries indication information that the voice service is not supported (for example, a Circuit Switched (CS) domain is not available), it indicates that the target network device does not support the voice service.
According to the embodiment of the application, after the terminal device receives the third attachment failure message, the voice-centered configuration is directly switched to the data-centered configuration, so that the problem that the terminal device cannot reside in the target network because the target network device does not support the voice service is avoided. The method can keep the terminal equipment residing on the target network and further improve the network residing rate of the target network.
With reference to the first aspect, in certain implementations of the first aspect, the method further includes: under the condition that the target network equipment supports voice service, the terminal equipment sends a fourth attachment request message to the target network equipment, wherein the fourth attachment request message carries configuration parameters taking voice as a center; the terminal device receives a fourth attach success message from the target network device.
With reference to the first aspect, in some implementations of the first aspect, before the terminal device sends the first attach request message to the target network device, the method further includes: under the condition that the target network equipment does not support voice service, the terminal equipment sends a fifth attachment request message to other network equipment, wherein the fifth attachment request message carries configuration parameters taking voice as a center; the terminal device receives a fifth attach failure message from the other network device.
It should be understood that the other networks described above may be third generation (3 rd-generation, 3G) or second generation (2 rd-generation, 2G) mobile communication networks. The target network device does not support voice service, and indicates that the terminal device will receive the attachment failure message when carrying the configuration parameters with voice as the center to send the attachment request.
In the embodiment of the application, when the target network device does not support the voice service (i.e., when the terminal device sends the attachment request message with voice as the center to the target network device, the terminal device receives the attachment failure message, at this time, the terminal device cannot successfully reside in the target network), the terminal device sends the attachment request message with voice as the center to other network devices again, after the attachment failure message is received, the terminal device switches the configuration with voice as the center into the configuration with data as the center, and re-registers the target network, so that the terminal device can use the data service of the network, thereby ensuring that the user can normally surf the internet.
In a second aspect, a terminal device is provided, which is configured to perform the method in any one of the possible implementation manners of the first aspect. In particular, the terminal device comprises means for performing the method of any one of the possible implementations of the first aspect described above.
In a third aspect, there is provided another terminal device, including a processor, coupled to a memory, and configured to execute instructions in the memory to implement the method in any one of the possible implementations of the first aspect. Optionally, the terminal device further comprises a memory. Optionally, the terminal device further comprises a communication interface, the processor being coupled to the communication interface.
In a fourth aspect, a processor is provided, comprising: input circuit, output circuit and processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, so that the processor performs the method of any one of the possible implementations of the first aspect.
In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.
In a fifth aspect, a processing apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory, and may receive signals via the receiver and transmit signals via the transmitter to perform the method of any one of the possible implementations of the first aspect.
Optionally, there are one or more processors and one or more memories.
Alternatively, the memory may be integrated with the processor, or provided separately from the processor.
In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.
It will be appreciated that the relevant data interaction procedure, e.g. sending an attach request, may be a procedure outputting an attach request from the processor, and receiving capability information may be a procedure receiving input capability information from the processor. In particular, the data output by the processor may be output to a transmitter and the input data received by the processor may be from a receiver. The transmitter and receiver may be collectively referred to as a transceiver, among others.
The processing device in the fifth aspect may be a chip, the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.
In a sixth aspect, there is provided a computer program product comprising: computer program (also called code, or instructions), which when executed, causes a computer to perform the method of any of the possible implementations of the first aspect described above.
In a seventh aspect, a computer-readable storage medium is provided, which stores a computer program (which may also be referred to as code or instructions) that, when executed on a computer, causes the computer to perform the method in any of the possible implementations of the first aspect.
Drawings
Fig. 1 is a schematic diagram of a communication system provided by an embodiment of the present application;
fig. 2 is a schematic flowchart of an attachment method of a terminal device according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another attachment method for a terminal device according to an embodiment of the present application;
fig. 4 is a schematic flowchart of an attachment method of a terminal device according to an embodiment of the present application;
fig. 5 is a schematic block diagram of a terminal device provided in an embodiment of the present application;
fig. 6 is a schematic block diagram of another terminal device provided in an embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
The technical scheme provided by the application can be applied to various communication systems, such as: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a fifth generation (5 th generation, 5G) mobile communication system, a New Radio (NR) system, or another evolved communication system, and a next generation mobile communication system of the 5G communication system, and the like.
For the understanding of the embodiments of the present application, a detailed description will be given of a communication system suitable for the embodiments of the present application with reference to fig. 1.
Fig. 1 is a schematic diagram of a communication system 100 provided in an embodiment of the present application. As shown in fig. 1, the communication system 100 includes at least two communication devices, for example, a network device 110 and a terminal device 120, wherein data communication can be performed between the network device 110 and the terminal device 120 through a wireless connection. Specifically, the network device 110 may send downlink data to the terminal device 120; terminal device 120 may also send upstream data to network device 110.
The terminal device 120 provided herein is a device that provides voice and/or data connectivity to a user. The terminal device may be referred to as a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment, etc.
Illustratively, the terminal device may be a handheld device, a vehicle-mounted device, or the like having a wireless connection function. Currently, some examples of terminal devices are: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote operation (remote local supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation safety), a wireless terminal in city (city), a wireless terminal in smart home (smart home), a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (wireless local) phone, a personal digital assistant (WLL) station, a handheld personal communication device with wireless communication function, a wireless terminal in industrial control (industrial control), a wireless terminal in transportation security (personal control), a wireless terminal in city (smart home), a wireless terminal in smart home (smart home), a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (personal digital assistant (PDA) phone, a wireless local communication device with wireless communication function, a wireless communication device, a, A computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, and the like, which are not limited in this embodiment of the present application.
By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.
The network device 110 in this embodiment may also be referred to as an access network device or a radio access network device, and may be a Transmission Reception Point (TRP), an evolved Node B (eNB or eNodeB) in an LTE system, a home base station (e.g., home evolved Node B, home Node B, HNB), a baseband unit (BBU), a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or the network device may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G network, or a network device in a PLMN network that is evolved in the future, may be an Access Point (AP) in a WLAN, may be a gbb in a New Radio (NR) system, may be a satellite base station in a satellite communication system, or the like, the embodiments of the present application are not limited.
In one network configuration, a network device may include a Centralized Unit (CU) node, or a Distributed Unit (DU) node, or a RAN device including a CU node and a DU node, or a control plane CU node (CU-CP node) and a user plane CU node (CU-UP node), and a RAN device of a DU node.
The network device provides a service for a cell, and a terminal device communicates with the cell through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) allocated by the network device, where the cell may belong to a macro base station (e.g., a macro eNB or a macro gNB), or may belong to a base station corresponding to a small cell (small cell), where the small cell may include: urban cell (metro cell), micro cell (microcell), pico cell (pico cell), femto cell (femto cell), etc., and these small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission service.
It should be understood that fig. 1 is a simplified schematic diagram that is shown only for ease of understanding, and that other devices, not shown in fig. 1, may also be included in the communication system 100.
The terminal equipment supporting voice service and/or data service initiates an attachment request to request for registering a network when being started, wherein the attachment request carries configuration parameters of the terminal equipment and adopts specific parameter values to indicate whether the terminal equipment is centered on data or voice. For a network configured with a voice-centric terminal device requiring registration, the network must support a voice service, and if the registered network does not support the voice service, the terminal device may generate a Circuit Switched Fallback (CSFB). For the terminal device configured with data as the center, the terminal device can be ensured to put the priority of the data service at the highest level, even if the registered network does not support the voice service, the terminal device configured with data as the center can reside in the network, and the CSFB does not occur.
Currently, the default configuration of most terminal devices is voice-centric. On one hand, for a terminal device inserted with a data card, if the default configuration is voice-centric and the registered target network does not support voice service, the terminal device will fall back to a third generation mobile communication technology (3 rd-generation, 3G) or a second generation mobile communication technology (2 rd-generation, 2G) network, which seriously affects the data service experience of the user. On the other hand, when the network of the operator in some countries configures only the data service (for example, the signaling of the network configuration is ps _ only), the terminal device can stay on the network only if the configuration is data-centric.
The configuration of the network described above is PS _ only, which means that the network only supports data services, where Packet Switch (PS) is sometimes also called packet service (packet service), and provides data services for users, that is, what is often called internet access: and accessing the internet information through a mobile phone or other mobile terminals. For most data services (such as web browsing, mail sending, BBS, etc.), an exclusive circuit path is not required, and physical communication resources can be fully shared by different users. Therefore, the service can be implemented without circuit switching, and only packet switching is needed, so that the service is called as PS.
The network residence generally refers to a ground residence network, and refers to a machine line device (usually in a building) included in a terminal device to network interface, and the machine line device is composed of a user residence wiring system which completes communication and control functions, so that the terminal device can flexibly and conveniently enter an access network. The above-mentioned network-resident process is described by taking a mobile phone as an example. Illustratively, after a mobile phone is powered on, a SIM card is initialized, a Public Land Mobile Network (PLMN) is selected, after the PLMN is determined, a cell search is started, a suitable cell is selected and camped on the cell, and then a network registration is started (mainly including processes of random access, attach request, authentication, encryption, etc., to complete the network registration). The above process can be roughly divided into the following stages: a frequency sweeping stage, a PLMN stage, an attach stage and the like. The attachment method of the terminal device provided by the embodiment of the application is an important stage in the network residence process.
The existing terminal equipment loads configuration parameters of the terminal equipment according to a user identity identification SIM card inserted when the terminal equipment is started before an attachment request is initiated, so that different operators load different configurations to register a network, and the aim of flexible configuration is fulfilled.
However, when the terminal device inserts the card configured to be centered on voice, and when the registered network does not support voice service, the data-centered parameter may be reconfigured to implement registration of the data service of the terminal device, but when the currently registered network supports voice service, the terminal device may not normally perform voice call.
In view of this, the present application provides an attachment method of a terminal device and a terminal device, where the terminal device sends an attachment request carrying data as a center to a target network device when it is determined that the target network device does not support a voice service, and the attachment is successful, so that the terminal device is successfully resided in a target network, and after the voice service is restored in the target network, the terminal device can implement a voice service. The method provided by the application can flexibly adjust the registered service according to the actual situation so as to recover the language conversation capacity in time and improve the user experience.
It should be understood that the target network device in the embodiment of the present application may be a network device corresponding to an LTE network and a new generation network developed on the LTE network.
Before describing the terminal device attaching method and the terminal device provided in the embodiments of the present application, the following description is made.
First, the first, second and various numerical numbers in the embodiments shown below are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application. E.g., to distinguish between different attach requests, to distinguish between different attach success messages, etc.
Second, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, and c, may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, wherein a, b and c can be single or multiple.
Third, words such as "exemplary" or "e.g.," mean an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
It should be understood that the embodiments of the present application may be applied to a number of different scenarios, including, but not limited to, the scenario illustrated in fig. 1.
Exemplarily, the mobile phone card is a data card, so that a situation that the mobile phone stays in a 3G/2G network due to the failure of voice service registration and the data service rate is reduced is avoided; for an operator only renting a PS network, the situation that the terminal equipment cannot search other networks (for example, 3G/2G) again for network registration because of registering voice service to cause network residence failure is avoided; under the condition that the 3G/2G network exits, when the terminal equipment which is configured to take voice as a center fails to register the LTE network, a scene that the network cannot be resident occurs; in a fifth generation mobile communication technology (5 rd-generation, 5G) scenario of a non-independent Network (NSA), if the network does not support voice service, the network residence rate of 5G is also reduced while the terminal device cannot reside in the LTE network; in a situation when frequent call drops, silence, etc. occur during a call.
The following describes in detail an attaching method 200 of a terminal device according to an embodiment of the present application with reference to fig. 2.
Fig. 2 illustrates an attachment method 200 of a terminal device according to an embodiment of the present application. The method 200 may be applied to the communication system 100 shown in fig. 1, and may also be applied to other communication systems, which is not limited in this embodiment. As shown in fig. 2, the method 200 may include the steps of:
s201, the terminal device determines whether the target network device supports the voice service.
It should be understood that the terminal device may determine whether the target network device supports the voice service according to the information obtained from the big data platform, and may also determine whether the target network device supports the voice service according to an attach success message or an attach failure message received by the terminal device from the target network device (it should be understood that the terminal device needs to send an attach request to the target network device before receiving the attach success message or the attach failure message sent by the target network device).
S202, when the target network device does not support the voice service, the terminal device sends a first attach request to the target network device, where the first attach request message carries configuration parameters with data as a center. Accordingly, the target network device receives the first attach request.
It should be understood that the first attach request includes a manner in which the terminal device initiates registration, and the registration manner is joint registration, that is, the terminal device registers the voice service and the data service simultaneously.
Illustratively, the signaling of the first Attach Request is EMM _ Attach _ Request, and the signaling of the configuration information is ue _ use _ setting: the registration mode signaling is Attach type = "EMM _ Attach _ type _ Combined Attach".
S203, the target network device sends a first attach success message to the terminal device. Accordingly, the terminal device receives the first attach success message.
It should be understood that, after receiving the attach success message, the terminal device may perform a subsequent registration procedure to complete network registration.
It should also be understood that, in general, the configuration of the terminal device is data-centric, and there is no requirement that the network device side must have voice services. However, if the terminal device does not re-register the voice service after the network device side recovers the voice service, the terminal device may not perform the voice call. That is, in S202 to S203, the first attach request message initiated by the terminal device carries the configuration parameters of the terminal device with data as the center, and receives the attach success message. In order to avoid the problem that the terminal device still cannot normally talk after the voice service of the network successfully registered in S203 is recovered, the recovery policy may be started, that is, the configuration of the terminal device is switched again to be centered on the voice, and the attach request is retransmitted.
And S204, when the terminal equipment executes any operation of restarting, card preparation or TAU, the terminal equipment sends a second attachment request to the target network equipment, wherein the second attachment request message carries the configuration parameters taking voice as the center. Accordingly, the target network device receives the second attach request.
It should be understood that the second attach request includes a manner in which the terminal device initiates registration, and the registration manner is joint registration, that is, the terminal device registers the voice service and the data service simultaneously.
In this embodiment of the present application, when performing any one of the operations of restart, card preparation, or TAU, the terminal device may switch its data-centric configuration to a voice-centric configuration, and re-initiate an attach request, which is referred to as a second attach request.
For example, the restart operation refers to a process of re-entering after a system of the terminal device is turned off, and in general, a user may press a power-off key of the terminal device for a long time, and the terminal device may have a restart prompt box from which the user may select the restart operation, or the terminal device may automatically execute a power-on and power-off operation after a jam occurs due to insufficient running memory of the terminal device, or the user may perform the power-on operation on the terminal device in a power-off state.
Card preparation may refer to a process of inserting a SIM card into the terminal device or a process of turning off the airplane mode of the terminal device by the user, for example.
Exemplarily, the TAU may be understood as a change in the location of the terminal device, i.e. the terminal device is no longer in the coverage of the currently registered network.
S205, when the voice service of the target network device is recovered, the target network device sends the information that the second attachment is successful to the terminal device. Accordingly, the terminal equipment receives the second attachment success information
According to the method and the device, the terminal device sends the first attachment request carrying the configuration parameters with data as the center to the target network device under the condition that the target network device is determined not to support the voice service, the attachment is successful, when the terminal device executes any one of startup, card preparation, restart or TAU, the configuration with data as the center is switched to be centered on voice, the second attachment request is restarted, and under the condition that the voice service of the target network device is recovered, the terminal device can flexibly adjust the registered service according to the actual condition, so that the voice conversation capability can be recovered in time, and the user experience is improved.
As an optional embodiment, after the terminal device sends the second attach request message to the target network device (i.e., S204), the method 200 further includes: and under the condition that the target network equipment still does not support the voice service, the target network equipment sends a second attachment failure message to the terminal equipment. Accordingly, the terminal device receives a second attach failure message from the target network device.
It should be understood that, after the terminal device receives the second attach failure message from the target network device, the terminal device may directly switch the voice-centric configuration to the data-centric configuration, so as to continue to perform the corresponding steps of S202 to S205.
Illustratively, the above signaling of the Attach failure is EMM _ Attach _ Reject.
As an optional embodiment, the determining, by the terminal device, whether the target network device supports the voice service includes: the terminal equipment acquires indication information from the big data platform, wherein the indication information is used for indicating whether the target network equipment supports voice service; the terminal device determines whether the target network device supports the voice service based on the indication information.
The big data platform can be used for counting the abnormal network-resident state of the terminal equipment under the current network. When the terminal equipment fails to stay in the network, the abnormal information before the network is recovered can be uploaded to the cloud big data platform, the cloud big data platform can analyze the received data, the condition of the network equipment which fails to stay in the network of the terminal equipment is obtained, other terminal equipment which needs to stay in the cell is informed, and the cell is abnormal and the network-staying failure can be caused.
For example, for the same cell, multiple terminal devices may reside, and when one terminal device sends an attach request and the network device side fails to reply to the voice registration, the abnormal data of the cell is reported to the big data platform through the mobile network. When the terminal equipment searches the network, the information of the cell which can be resided at present is reported, the state of the current cell of the cloud big data platform is obtained, and if the indication information of the big data platform is received, the current cell does not support voice service, configuration parameters with data as the center are switched. When a terminal device in the cell sends an attachment request centering on voice and the attachment is successful, the message can be reported to the big data platform, and at the moment, the big data platform can instruct the cell to recover the voice service by sending the message, so that voice registration can be carried out.
It should also be understood that, when the terminal device obtains the indication information that the target network device supports the voice service through the big data platform, the terminal device may directly send an attach request message carrying voice as a center to the target network device.
According to the embodiment of the application, before the terminal equipment sends the attachment request to the target network equipment, the indication information of whether the target network equipment supports the voice service is obtained in advance through the big data platform, the condition that the target network equipment does not support the voice service can be effectively avoided, the terminal equipment sends the attachment request which takes the voice as the center to the target network equipment, and the signaling interaction between the terminal equipment and the network equipment is effectively reduced.
As an optional embodiment, the determining, by the terminal device, whether the target network device supports the voice service includes: and the terminal equipment sends a third attachment request message to the target network equipment, wherein the third attachment request message carries the configuration parameters taking voice as the center. Accordingly, the target network device receives the third attach request message.
The target network device sends the third attach request message or the third attach failure message to the terminal device. Accordingly, the terminal device receives a third attach successful message or a third attach failed message from the target network device.
And the terminal equipment determines whether the target network equipment supports the voice service or not based on the third attachment success message or the third attachment failure message.
It should be understood that the attach success message indicates that the target network device supports the voice service, and when the attach failure message carries indication information that the voice service is not supported (for example, a Circuit Switched (CS) domain is not available), it indicates that the target network device does not support the voice service.
If the terminal device receives the third successful attach message from the target network device, the terminal device may perform a subsequent registration procedure to complete network registration. If the terminal device receives the third attach failure message from the target network device, the terminal device may directly switch the voice-centric configuration to the data-centric configuration, so as to continue to perform the corresponding steps of S202 to S205.
The CS is a network for providing a call service to the terminal device. When a user calls through the CS network, the CS network allocates a fixed channel to both parties of the call. During the whole conversation process, the user can always occupy the special channel, and other users have no way to occupy the channel. When the call is over, the CS network releases the channel for the next call assigned to another user. In short, the circuit is connected when a call is established and disconnected when the call is ended, which is circuit switching.
According to the embodiment of the application, after the terminal device receives the third attachment failure message, the voice-centered configuration is directly switched to the data-centered configuration, so that the problem that the terminal device cannot reside in the target network because the target network device does not support the voice service is avoided. The method can keep the terminal equipment residing on the target network and further improve the network residing rate of the target network.
As an alternative embodiment, the method 200 further comprises: and under the condition that the target network equipment supports the voice service, the terminal equipment sends a fourth attachment request message to the target network equipment, wherein the fourth attachment request message carries the configuration parameters taking the voice as the center. Accordingly, the target network device receives the fourth attach request message.
The target network device sends the fourth attach request message to the terminal device. Accordingly, the terminal device receives the fourth attach success message from the target network device.
As an optional embodiment, before the terminal device sends the first attach request message to the target network device, the method 200 further includes: and under the condition that the target network equipment does not support the voice service, the terminal equipment sends a fifth attachment request message to other network equipment, wherein the fifth attachment request message carries the configuration parameters taking the voice as the center. Accordingly, the other network device receives the fifth attach request message.
And the other network equipment sends a fifth attachment failure message to the terminal equipment. Accordingly, the terminal device receives a fifth attach failure message from the other network device.
It should be understood that the other network described above may be a 3G/2G network. The target network device does not support voice service, and indicates that the terminal device will receive the attachment failure message when carrying the configuration parameters with voice as the center to send the attachment request. Therefore, after the terminal device receives the attach failure message from the network device, the terminal device may reinitiate the attach request for registering the 3G/2G network, and if the network in which the terminal device is registered does not have the 3G/2G service, the terminal device may have a network-resident failure, resulting in no service for the terminal device, and at this time, the configuration of the terminal device with voice as a center may be switched to the configuration with data as a center, and the attach request may be reinitiated to the target network device.
In the embodiment of the application, when the target network device does not support the voice service (i.e., when the terminal device sends the attachment request message with voice as the center to the target network device, the terminal device receives the attachment failure message, at this time, the terminal device cannot successfully reside in the target network), the terminal device sends the attachment request message with voice as the center to other network devices again, after the attachment failure message is received, the terminal device switches the configuration with voice as the center into the configuration with data as the center, and re-registers the target network, so that the terminal device can use the data service of the network device, thereby ensuring that the user can normally surf the internet.
The process of initiating an attach request in the method 200 described above is described in detail below with reference to fig. 3.
Fig. 3 illustrates another terminal device attaching method 300 according to an embodiment of the present disclosure. As shown in fig. 3, a non-access stratum (NAS) layer, a Radio Resource Control (RRC) layer, and a physical layer/data link layer (L1/L2) belong to the terminal device, and the method 300 may include the following steps:
s301, the NAS layer of the terminal device sends a request for searching the network device to the RRC layer, and accordingly, the RRC layer of the terminal device receives the search request.
It should be understood that the RRC layer of the terminal device, upon receiving the search request, automatically searches for a plurality of network devices within the coverage of the terminal device and selects a target network device where the terminal device can currently reside.
Illustratively, the request signaling for searching the network device is PLMN _ SEARCH _ REQ, where PLMN represents operator identity.
S302, after the RRC layer of the terminal device determines the target network device where the terminal device can reside, a cell search request is sent to the L1/L2 layer. Accordingly, the L1/L2 layer receives the request for the cell search.
It should be appreciated that layer L1/L2, upon receiving the request for the cell search, determines the cells in which the terminal device may camp.
S303, the RRC layer of the terminal device sends the information of the cell to be camped to the NAS layer. Accordingly, the NAS layer receives information of the camping cell.
It should be understood that the information of the camping cell may include system information of the selected camping cell, and the like.
Illustratively, the information of the camping cell may be transmitted between the RRC layer and the NAS layer by using the following signaling: RRC → NAS: PLMN _ SEARCH _ CNF, RRC → NAS: SYS _ INFO _ IND.
S304, the RRC layer of the terminal device sends an attach request to the target network device. Accordingly, the target network device receives the attach request.
It should be understood that the attach request may include configuration information of the terminal device.
S305, the target network device sends the attach request to a Mobility Management Entity (MME). Accordingly, the MME receives the attach request.
S306, the MME sends the information of successful attachment to the target network equipment. Accordingly, the target network device receives the information that the attachment was successful. Or, the MME sends attach failure information to the target network device. Accordingly, the target network device receives the attachment failure information.
It should be understood that the reason for the attachment failure may be included in the above-mentioned information of the attachment failure. Exemplarily, when the reason for the attachment failure is that the CS domain is not available, the corresponding steps of S203 to S207 in the method 200 may be continuously performed.
S307, after receiving the information of successful attach, the target network sends RRC connection reconfiguration to the RRC layer. Accordingly, the RRC layer receives the RRC connection reconfiguration.
It should be understood that the specific procedures of the first attach request and the second attach request sent in the method 200 may refer to the specific procedures provided in the method 300, and are not described herein again.
The following describes in detail the attachment method provided in the embodiment of the present application with reference to fig. 4 and using a terminal device as an execution main body.
Fig. 4 illustrates a further method 400 for attaching a terminal device according to an embodiment of the present application. The method 400 determines whether the network device supports voice services by determining the type of the message received by the terminal device after the terminal device sends the first attach request message to the network device. As shown in fig. 4, the method 400 may include the following steps:
s401, the terminal device sends a first attach request message, and the first attach request message carries the configuration parameters of the terminal device and the manner of initiating the attach request.
It should be understood that the configuration parameters of the terminal device carried above are voice-centric, and the manner of initiating the attach request is joint registration.
S402, if the terminal device receives the attach failure message and the attach failure message carries indication information that the voice service is not supported (for example, the CS domain is unavailable), the terminal device executes S403.
If the terminal device receives the attach success message, the terminal device executes S409.
S403, the terminal device sends a second attach request message, and the second attach request message carries the configuration information of the terminal device and the manner of initiating the attach request.
It should be understood that what is different from the first attach request in the information carried in the second attach request is: the configuration parameters of the terminal device carried in the second attach request are centered on the data.
S404, whether the message received by the terminal device is the information of successful attachment.
If the terminal device receives the attach success message, the terminal device executes S405.
If the terminal device receives the attach failure message, the terminal device executes S403 to resend the second attach request.
In the embodiment of the present application, taking the terminal device presence TAU, card preparation, and restart operation as examples, the determination process of S405 to S407 is executed.
S405, the terminal equipment judges whether the TAU operation exists.
If the TAU operation exists, the terminal device executes S408.
If no TAU operation exists, the terminal device executes S406.
S406, the terminal device determines whether there is a card preparation operation.
If there is a card preparation operation, the terminal device executes S408.
If there is no card preparation operation, the terminal device executes S407.
S407, the terminal equipment judges whether a restarting operation exists.
If the restart operation exists, the terminal device executes S408.
If the restart operation does not exist, the terminal device continues to execute step S405 to start the next determination process.
S408, the terminal device sends a third attach request message.
It should be understood that, the information carried in the third attach request message may refer to the description related to the first attach request message in S401, and is not described herein again.
It should be further understood that, after the terminal device sends the third attach request message, if the attach success message is received, indicating that the target network device currently registered by the terminal device supports the voice service, the subsequent registration process may be continued. If the attach failure message is received and the message carries the indication information that the target network device does not support the voice service, the terminal device may continue to perform the relevant steps from S402 to S408.
And S409, the terminal equipment successfully resides in the network.
And after receiving the information of successful attachment, the terminal equipment continues to execute the subsequent registration process to realize successful network residence of the terminal equipment.
It should be understood that the above determination processes of S405 to S407 are not sequential, for example, the above determination process may also be performed according to card preparation, TAU, and restart operations or according to restart, TAU, and card preparation operations, which is not limited in this application.
In the embodiment of the application, the terminal device sends a first attach request message carrying voice as a center to the target network device, after receiving a first attach failure message, the voice-centered configuration can be switched to data-centered configuration, the second attach request is resent, and an attach success message is received, indicating that the terminal device successfully resides in the target network. The method provided by the embodiment of the application enables the terminal equipment to flexibly adjust the registered service according to the actual situation so as to recover the language conversation capability in time and improve the user experience.
It should be understood that the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
The method for attaching the terminal device according to the embodiment of the present application is described in detail above with reference to fig. 2 to 4, and the terminal device according to the embodiment of the present application is described in detail below with reference to fig. 5 and 6.
Fig. 5 shows a terminal device 500 provided in an embodiment of the present application, where the terminal device 500 includes: a determination module 510 and a transceiver module 520.
Wherein the determining module 510 is configured to: it is determined whether the target network device supports voice services. The transceiver module 520 is configured to: sending a first attach request message to the target network device under the condition that the target network device does not support voice service, wherein the first attach request message carries configuration parameters taking data as a center; receiving a first attach success message from the target network device; when the terminal equipment executes any one operation of starting up, card preparation, restarting or Tracking Area Update (TAU), sending a second attachment request message to the target network equipment, wherein the second attachment request message carries configuration parameters taking voice as a center; and receiving a second attach success message from the target network device in case of voice service restoration of the target network device.
Optionally, the transceiver module 520 is further configured to: receiving a second attach failure message from the target network device if the target network device still does not support voice services.
Optionally, the determining module 510 is specifically configured to: acquiring indication information from a big data platform, wherein the indication information is used for indicating whether the target network equipment supports voice service; and determining whether the target network equipment supports voice service or not based on the indication information.
Optionally, the transceiver module 520 is further configured to: sending a third attach request message to the target network device, wherein the third attach request message carries configuration parameters taking voice as a center; receiving a third attach successful message or a third attach failed message from the target network device; the determination module 510 is further configured to: determining whether the target network device supports voice services based on the third attach success message or the third attach failure message.
Optionally, the transceiver module 520 is further configured to: sending a fourth attach request message to the target network device under the condition that the target network device supports voice service, wherein the fourth attach request message carries configuration parameters taking voice as a center; receiving a fourth attach success message from the target network device.
Optionally, the transceiver module 520 is further configured to: sending a fifth attach request message to other network devices under the condition that the target network device does not support voice service, wherein the fifth attach request message carries configuration parameters taking voice as a center; receiving a fifth attach failure message from the other network device.
It should be appreciated that the terminal device 500 herein is embodied in the form of functional modules. The term module herein may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. The terminal device 500 may be configured to execute each flow and/or step corresponding to the terminal device in the foregoing method embodiments, and details are not described herein for avoiding repetition.
The terminal device 500 has a function of implementing corresponding steps executed by the terminal device in the method; the above functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. For example, the transceiver module 520 may be a communication interface, such as a transceiver interface.
In an embodiment of the present application, the terminal device 500 in fig. 5 may also be a chip or a chip system, for example: system on chip (SoC). Correspondingly, the transceiver module 520 may be a transceiver circuit of the chip, and is not limited herein.
Fig. 6 shows another terminal device 600 provided in the embodiment of the present application. The terminal device 600 includes a processor 610, a transceiver 620, and a memory 630. Wherein the processor 610, the transceiver 620 and the memory 630 are in communication with each other through an internal connection path, the memory 630 is used for storing instructions, and the processor 610 is used for executing the instructions stored in the memory 630 to control the transceiver 620 to transmit and/or receive signals.
Wherein the processor 610 is configured to: determining whether the target network device supports voice services; the transceiver 620 is configured to: sending a first attach request message to the target network device under the condition that the target network device does not support voice service, wherein the first attach request message carries configuration parameters taking data as a center; receiving a first attach success message from the target network device; when the terminal equipment executes any one operation of starting up, card preparation, restarting or Tracking Area Update (TAU), sending a second attachment request message to the target network equipment, wherein the second attachment request message carries configuration parameters taking voice as a center; and receiving a second attach success message from the target network device in case of voice service restoration of the target network device.
Optionally, the transceiver 620 is further configured to: receiving a second attach failure message from the target network if the target network device still does not support voice services.
Optionally, the processor 610 is specifically configured to: acquiring indication information from a big data platform, wherein the indication information is used for indicating whether the target network equipment supports voice service; and determining whether the target network equipment supports voice service or not based on the indication information.
Optionally, the transceiver 620 is further configured to: sending a third attach request message to the target network device, wherein the third attach request message carries configuration parameters taking voice as a center; receiving a third attach successful message or a third attach failed message from the target network device; the processor 610 is specifically configured to: determining whether the target network device supports voice services based on the third attach success message or the third attach failure message.
Optionally, the transceiver 620 is further configured to: sending a fourth attach request message to the target network device under the condition that the target network device supports voice service, wherein the fourth attach request message carries configuration parameters taking voice as a center; receiving a fourth attach success message from the target network device.
Optionally, the transceiver 620 is further configured to: sending a fifth attach request message to other network devices under the condition that the target network device does not support voice service, wherein the fifth attach request message carries configuration parameters taking voice as a center; receiving a fifth attach failure message from the other network device.
It should be understood that the functions of the terminal device in the foregoing embodiments may be integrated in the terminal device 600, and the terminal device 600 may be configured to execute each step and/or flow corresponding to the terminal device in the foregoing method embodiments. Alternatively, the memory 630 may include both read-only memory and random access memory, and provides instructions and data to the processor. The portion of memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 610 may be configured to execute the instructions stored in the memory, and when the processor executes the instructions, the processor may perform the steps and/or processes corresponding to the terminal device in the foregoing method embodiments.
It should be understood that, in the embodiments of the present application, the processor may be a Central Processing Unit (CPU), and the processor may also be other general processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor executes instructions in the memory, in combination with hardware thereof, to perform the steps of the above-described method. To avoid repetition, it is not described in detail here.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (14)

1. An attachment method of a terminal device, comprising:
the terminal equipment determines whether the target network equipment supports voice service;
under the condition that the target network equipment does not support voice service, the terminal equipment sends a first attachment request message to the target network equipment, wherein the first attachment request message carries configuration parameters taking data as a center;
the terminal equipment receives a first attachment success message from the target network equipment;
when the terminal equipment executes any one operation of starting up, card preparation, restarting or Tracking Area Update (TAU), the terminal equipment sends a second attachment request message to the target network equipment, wherein the second attachment request message carries configuration parameters taking voice as a center;
and under the condition that the voice service of the target network equipment is recovered, the terminal equipment receives a second attachment success message from the target network equipment.
2. The method of claim 1, wherein after the terminal device sends a second attach request message to the target network device, the method further comprises:
and under the condition that the target network equipment still does not support the voice service, the terminal equipment receives a second attachment failure message from the target network.
3. The method of claim 1 or 2, wherein the terminal device determining whether the target network device supports voice services comprises:
the terminal equipment acquires indication information from a big data platform, wherein the indication information is used for indicating whether the target network equipment supports voice service;
and the terminal equipment determines whether the target network equipment supports voice service or not based on the indication information.
4. The method of claim 1 or 2, wherein the terminal device determining whether the target network device supports voice services comprises:
the terminal equipment sends a third attachment request message to the target network equipment, wherein the third attachment request message carries configuration parameters taking voice as a center;
the terminal equipment receives a third attachment success message or a third attachment failure message from the target network equipment;
and the terminal equipment determines whether the target network equipment supports voice service or not based on the third attachment success message or the third attachment failure message.
5. The method of claim 4, further comprising:
under the condition that the target network equipment supports voice service, the terminal equipment sends a fourth attachment request message to the target network equipment, wherein the fourth attachment request message carries configuration parameters taking voice as a center;
and the terminal equipment receives a fourth attachment success message from the target network equipment.
6. The method of claim 5, wherein before the terminal device sends the first attach request message to the target network device, the method further comprises:
under the condition that the target network equipment does not support voice service, the terminal equipment sends a fifth attachment request message to other network equipment, wherein the fifth attachment request message carries configuration parameters taking voice as a center;
and the terminal equipment receives a fifth attachment failure message from the other network equipment.
7. A terminal device, comprising:
a determining module for determining whether the target network device supports voice service;
a transceiver module, configured to send a first attach request message to the target network device when the target network device does not support a voice service, where the first attach request message carries a configuration parameter that takes data as a center; receiving a first attach success message from the target network device; when the terminal equipment executes any one operation of starting up, card preparation, restarting or Tracking Area Update (TAU), sending a second attachment request message to the target network equipment, wherein the second attachment request message carries configuration parameters taking voice as a center; and receiving a second attach success message from the target network device in case of voice service restoration of the target network device.
8. The terminal device of claim 7, wherein the transceiver module is further configured to:
receiving a second attach failure message from the target network if the target network device still does not support voice services.
9. The terminal device according to claim 7 or 8, wherein the determining module is specifically configured to:
acquiring indication information from a big data platform, wherein the indication information is used for indicating whether the target network equipment supports voice service;
and determining whether the target network equipment supports voice service or not based on the indication information.
10. The terminal device according to claim 7 or 8, wherein the transceiver module is further configured to:
sending a third attach request message to the target network device, wherein the third attach request message carries configuration parameters taking voice as a center;
receiving a third attach successful message or a third attach failed message from the target network device;
the determination module is further to: determining whether the target network device supports voice services based on the third attach success message or the third attach failure message.
11. The terminal device of claim 10, wherein the transceiver module is further configured to:
sending a fourth attach request message to the target network device under the condition that the target network device supports voice service, wherein the fourth attach request message carries configuration parameters taking voice as a center;
receiving a fourth attach success message from the target network device.
12. The terminal device of claim 11, wherein the transceiver module is further configured to:
sending a fifth attach request message to other network devices under the condition that the target network device does not support voice service, wherein the fifth attach request message carries configuration parameters taking voice as a center;
receiving a fifth attach failure message from the other network device.
13. A terminal device, comprising: a processor coupled to a memory for storing a computer program that, when invoked by the processor, causes the terminal device to perform the method of any of claims 1 to 6.
14. A computer-readable storage medium, in which a computer program is stored which, when run on one or more processors, implements the method of any one of claims 1 to 6.
CN202110604806.1A 2021-05-31 2021-05-31 Terminal equipment attachment method and terminal equipment Pending CN113260042A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110604806.1A CN113260042A (en) 2021-05-31 2021-05-31 Terminal equipment attachment method and terminal equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110604806.1A CN113260042A (en) 2021-05-31 2021-05-31 Terminal equipment attachment method and terminal equipment

Publications (1)

Publication Number Publication Date
CN113260042A true CN113260042A (en) 2021-08-13

Family

ID=77185656

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110604806.1A Pending CN113260042A (en) 2021-05-31 2021-05-31 Terminal equipment attachment method and terminal equipment

Country Status (1)

Country Link
CN (1) CN113260042A (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810990A (en) * 2021-09-23 2021-12-17 上海移远通信技术股份有限公司 Communication method and device
CN116737289A (en) * 2022-09-15 2023-09-12 荣耀终端有限公司 Display method, terminal device and storage medium
CN117880794A (en) * 2024-03-07 2024-04-12 荣耀终端有限公司 Communication method and device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374258A (en) * 2007-08-20 2009-02-25 华为技术有限公司 System for implementing network backward compatibility, and adherence, de-adherence method
CN103634855A (en) * 2013-10-30 2014-03-12 酷派软件技术（深圳）有限公司 Method of accessing terminal into LTE (Long Term Evolution) network and terminal
CN105657790A (en) * 2016-03-23 2016-06-08 深圳优克云联科技有限公司 Network connecting method, device and system
CN112004264A (en) * 2020-09-21 2020-11-27 深圳市锐尔觅移动通信有限公司 Network registration method, network registration device, storage medium and terminal equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374258A (en) * 2007-08-20 2009-02-25 华为技术有限公司 System for implementing network backward compatibility, and adherence, de-adherence method
CN103634855A (en) * 2013-10-30 2014-03-12 酷派软件技术（深圳）有限公司 Method of accessing terminal into LTE (Long Term Evolution) network and terminal
CN105657790A (en) * 2016-03-23 2016-06-08 深圳优克云联科技有限公司 Network connecting method, device and system
CN112004264A (en) * 2020-09-21 2020-11-27 深圳市锐尔觅移动通信有限公司 Network registration method, network registration device, storage medium and terminal equipment

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810990A (en) * 2021-09-23 2021-12-17 上海移远通信技术股份有限公司 Communication method and device
CN113810990B (en) * 2021-09-23 2024-06-18 上海移远通信技术股份有限公司 Communication method and device
CN116737289A (en) * 2022-09-15 2023-09-12 荣耀终端有限公司 Display method, terminal device and storage medium
CN117880794A (en) * 2024-03-07 2024-04-12 荣耀终端有限公司 Communication method and device

Similar Documents

Publication Publication Date Title
US11197346B2 (en) User equipment having multiple subscriber identity modules with improved suspend / resume operation
CN111869264B (en) Method for returning to high-standard network from low-standard network and communication device
CN109819392B (en) Method and device for reporting position information
CN113260042A (en) Terminal equipment attachment method and terminal equipment
CN111788848B (en) Network exception handling method and device
CN111726862B (en) Paging monitoring method, device, system and storage medium
CN111770517A (en) Method for configuring frequency priority, terminal equipment, base station and core network equipment
JP2020505889A (en) Communication method and communication device
CN105050144A (en) Performing handover from a second generation RAT to a fourth generation RAT
CN114401537B (en) Network redirection method, device and user equipment
CN115804172A (en) Information processing method, terminal equipment and network equipment
CN113179512B (en) Communication method and communication device
CN115348642A (en) Cell selection method and device
CN114830731A (en) Method, apparatus, storage medium, and chip system for wireless communication apparatus
CN115776738A (en) Method for establishing Radio Resource Control (RRC) connection, terminal equipment and network equipment
US20230276332A1 (en) Methods for Enhanced Radio Link Failure Recovery
EP3972326A1 (en) Measurement method and apparatus
CN115066917A (en) Communication method, device, readable storage medium and chip system
CN113613232A (en) Emergency call method and device
CN115942431A (en) Relay communication method, communication device and communication system
CN116530198A (en) Data transmission method, terminal equipment and network equipment
CN116250290A (en) Wireless communication method, terminal equipment, first access network equipment and network element
KR20100024632A (en) Apparatus and method for service registration in multi mode portable terminal
CN110602800A (en) Communication method and device
US12028728B2 (en) Measurement method and apparatus

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20210813