WO2018129728A1 - 非连续接收的管理方法和装置 - Google Patents

非连续接收的管理方法和装置 Download PDF

Info

Publication number
WO2018129728A1
WO2018129728A1 PCT/CN2017/071193 CN2017071193W WO2018129728A1 WO 2018129728 A1 WO2018129728 A1 WO 2018129728A1 CN 2017071193 W CN2017071193 W CN 2017071193W WO 2018129728 A1 WO2018129728 A1 WO 2018129728A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
base station
voice
voice service
drx
Prior art date
Application number
PCT/CN2017/071193
Other languages
English (en)
French (fr)
Inventor
王振东
吴联芳
黄颖华
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201780083268.8A priority Critical patent/CN110169146B/zh
Priority to KR1020197023994A priority patent/KR102221413B1/ko
Priority to JP2019538125A priority patent/JP6868110B2/ja
Priority to EP17891224.2A priority patent/EP3562218B1/en
Priority to PCT/CN2017/071193 priority patent/WO2018129728A1/zh
Publication of WO2018129728A1 publication Critical patent/WO2018129728A1/zh
Priority to US16/510,540 priority patent/US11259357B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/005—Routing actions in the presence of nodes in sleep or doze mode
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/04—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0254—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity detecting a user operation or a tactile contact or a motion of the device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments of the present application relate to the field of communication technologies, and, more particularly, to a management method and apparatus for discontinuous reception.
  • the voice service is carried in a Circuit Switched (CS) domain.
  • CS Circuit Switched
  • PS Packet Switched
  • IP Internet Protocol
  • the traffic data flow is usually bursty, with data transmission for a period of time, but no data transmission for the next period of time.
  • a discontinuous reception (DRX) mechanism is introduced to reduce the energy consumption of the terminal.
  • the mechanism is that the terminal stops listening to the physical downlink control channel (PDCCH) in a period of time (which may be called a dormant period), and monitors the PDCCH when entering the active state, so that the terminal monitors the PDCCH when not in use, thereby reducing the PDCCH.
  • PDCCH physical downlink control channel
  • the embodiment of the present application provides a DRX management method and apparatus, so as to reduce the delay of voice call connection.
  • a DRX management method including:
  • the base station determines that the terminal has a voice service; the base station establishes a voice bearer for the terminal, and when the voice bearer is established for the terminal, the DRX function of the terminal is effective.
  • the DRX function is not valid before the voice bearer is established.
  • the DRX function is enabled again, thereby reducing the delay of the voice call.
  • the above takes effect.
  • the DRX function of the terminal is not enabled before the voice bearer is established. For example, when the default bearer is set, the base station does not take effect of the terminal DRX function.
  • the voice bearer is established, the DRX parameter is sent and the DRX function of the terminal is validated. Or, before the establishment of the voice bearer, when the DRX function of the terminal is enabled, the base station configures the DRX function of the terminal to disable the DRX function of the terminal.
  • the DRX parameter is sent to implement the DRX function of the terminal. The above takes effect. Before the voice bearer is established, when the DRX function of the terminal is enabled, the base station configures the DRX function of the terminal to disable the DRX function of the terminal.
  • the base station before the base station establishes the voice bearer for the terminal, the base station further includes: the base station establishes a default bearer for the terminal, and when the default bearer is established for the terminal, the base station does not validate the DRX function of the terminal.
  • the method further includes: the base station sending, to the terminal, a message for deactivating the DRX function of the terminal.
  • the DRX function of the base station effective terminal can be implemented by carrying the DRX parameter in the RRC connection reconfiguration message sent to the terminal in the RRC connection reconfiguration process. Since the DRX function of the terminal does not take effect when the RRC connection reconfiguration message is sent, the sending and receiving of the RRC connection reconfiguration message are not affected by the DRX, ensuring low delay establishment of the voice bearer and reducing voice. The delay in which the call is connected.
  • the DRX function of the terminal does not take effect.
  • the RRC connection reconfiguration message sent to the terminal does not carry the DRX parameter in the RRC connection reconfiguration process.
  • the message that the base station sends the DRX function for deactivating the terminal to the terminal may be implemented by carrying the cell that releases the DRX parameter in the RRC connection reconfiguration message sent to the terminal in the RRC connection reconfiguration process.
  • the method for determining, by the base station, the voice service of the terminal may include the following methods:
  • the first base station receives the RRC connection request message sent by the terminal, where the RRC connection request message includes a cause value, where the cause value is used to indicate the reason for initiating the RRC connection request, and the base station determines, according to the cause value, that the terminal has the voice service. Further, when the cause value is a voice call mobile initiator, such as mo-VoiceCall, the base station determines, according to the cause value, that the terminal has a voice service, and can determine that the terminal is a calling terminal. When the cause value is a voice call mobile receiver, such as mt-VoiceCall, the base station determines, according to the cause value, that the terminal has a voice service, and can determine that the terminal is the called terminal.
  • the cause value is a voice call mobile initiator, such as mo-VoiceCall
  • the base station determines, according to the cause value, that the terminal has a voice service, and can determine that the terminal is the called terminal.
  • the base station determines, according to the paging message, that the terminal has a voice service, and specifically includes:
  • the base station receives the paging message of the terminal from the core network, and the paging message includes indication information, where the indication information is used to indicate that the terminal has a voice service, and the base station determines, according to the indication information, that the terminal has a voice service.
  • the indication information may be a paging priority
  • the process of determining, by the indication information, that the terminal has the voice service includes: when the base station determines that the paging priority is the first paging priority, determining that the terminal has a voice service, where the first page
  • the priority is set to indicate the paging priority of the terminal with voice service.
  • the indication information may be a cell dedicated to indicating that the terminal has a voice service, for example, a voice terminal indication cell.
  • the base station determines, according to the indication information, a process in which the terminal has a voice service, including: when the base station determines that the paging message includes a voice terminal indication At the time of the cell, the base station determines that the terminal has a voice service.
  • the base station determines, according to the initial context setup request message, that the terminal has a voice service, and specifically includes:
  • the base station receives an initial context setup request message, where the initial context setup request message includes an indication cell, where the indication cell is used to indicate that the terminal has a voice service, and the base station determines, according to the indication cell, that the terminal has a voice service.
  • Manner 4 The base station parses the information on the default bearer. When it is determined that the information carried on the default bearer is SIP signaling, it is determined that the terminal has a voice service.
  • the terminal can be determined to have a voice service before or after the default bearer is established. Therefore, when the default bearer is established, the DRX function of the terminal is not valid, and the DRX function of the terminal is effective when the voice bearer is established.
  • the foregoing method 4 can be used in any voice call scenario, and has a better effect on a scenario in which a terminal initiates a voice service when the terminal is in an RRC connected state or is called as a voice call.
  • the terminal establishes the RRC connection and the default bearer.
  • the DRX of the terminal is valid.
  • the base station can perform the DRX function of the terminal.
  • the voice bearer is established, the DRX function is effective. , the DRX parameter is issued.
  • the default bearer is a bearer with a QCI of 5 when the terminal has a voice service
  • the voice bearer is a dedicated bearer, including a bearer with a QCI of 1.
  • a DRX management apparatus for a base station comprising means or means for performing the various steps of any of the methods of the above first aspect.
  • a DRX management apparatus comprising a processor and a memory, the memory is for storing a program, and the processor calls a program stored in the memory to perform any of the methods of the above first aspect.
  • a DRX management apparatus comprising at least one processing element or chip for performing any of the methods of the above first aspect.
  • a program for performing any of the methods of the above first aspect when executed by a processor.
  • a computer readable storage medium comprising the program of the fifth aspect.
  • the seventh aspect provides a DRX management method, which is executed by a terminal, and includes:
  • the terminal starts the DRX function according to the DRX parameter.
  • the terminal before receiving the first configuration message sent by the base station, the terminal further receives a second configuration message sent by the base station, where the second configuration message is used to configure a default bearer of the terminal, and the second configuration message does not include the DRX parameter, The terminal does not start the DRX function when the default bearer is established.
  • the foregoing method before the receiving, by the terminal, the first configuration message sent by the base station, the foregoing method further includes:
  • the terminal starts the DRX function according to the DRX parameter in the second configuration message.
  • the terminal configures the DRX function according to the third configuration message.
  • the terminal turns on the DRX function when the default bearer is established, but when the base station recognizes that the terminal has the voice service, the DRX function is turned off, thereby reducing the impact of the DRX function on the paging connection.
  • the terminal when the terminal sends an RRC connection request to the base station in an idle state, the terminal carries a cause value, where the cause value is used to indicate a reason for initiating an RRC connection request, so that the base station determines, according to the cause value, that the terminal has a voice service.
  • the cause value when the terminal is the calling terminal, the cause value is a voice call mobile initiator, such as mo-VoiceCall; when the terminal is the called terminal, the cause value is a voice call mobile receiver, such as mt-VoiceCall.
  • a DRX management apparatus for a terminal, comprising means or means for performing the steps of any of the methods of the above seventh aspect.
  • a DRX management apparatus comprising a processor and a memory, the memory is for storing a program, and the processor calls a program stored in the memory to perform any of the methods of the above seventh aspect.
  • a DRX management apparatus comprising at least one processing element or chip for performing any of the methods of the above seventh aspect.
  • a program for performing any of the methods of the above seventh aspect when executed by a processor.
  • a computer readable storage medium comprising the program of the eleventh aspect.
  • the DRX management method and device provided by the embodiment of the present invention can enable the terminal to not implement the DRX function before the voice bearer is established; the DRX function is effective only when the voice bearer is established. Therefore, the delay takes effect on the DRX function of the terminal, thereby effectively reducing the delay of voice paging.
  • FIG. 1 is a schematic diagram of a voice call scenario provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a voice call process according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a DRX cycle provided by an embodiment of the present application.
  • FIG. 5 is a flowchart of a DRX management method according to an embodiment of the present application.
  • FIG. 6 is a flowchart of another DRX management method according to an embodiment of the present application.
  • FIG. 7 is a flowchart of still another DRX management method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of a DRX management apparatus according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of another DRX management apparatus according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • a terminal also called a User Equipment (UE) is a device that provides voice and/or data connectivity to a user, for example, a handheld device with a wireless connection function, an in-vehicle device, and the like.
  • UE User Equipment
  • Common terminals include, for example, mobile phones, tablets, notebook computers, PDAs, mobile internet devices (MIDs), wearable devices such as smart watches, smart bracelets, pedometers, and the like.
  • MIDs mobile internet devices
  • wearable devices such as smart watches, smart bracelets, pedometers, and the like.
  • a base station also known as a radio access network (RAN) device, is a device that accesses a terminal to a wireless network, including but not limited to: a Transmission Reception Point (TRP), Evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver (Base Transceiver) Station, BTS), home base station (for example, Home evolved NodeB, or Home Node B, HNB), BaseBand Unit (BBU).
  • TRP Transmission Reception Point
  • eNB Evolved Node B
  • RNC Radio Network Controller
  • NB Node B
  • BSC Base Station Controller
  • Multiple means two or more, and other quantifiers are similar. "and/or”, describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately.
  • the character "/" generally indicates that the contextual object is an "or" relationship.
  • FIG. 1 is a schematic diagram of a voice call scenario according to an embodiment of the present application.
  • the terminal 110 and the terminal 120 access the wireless network through the base station 130 and the base station 140, respectively.
  • the wireless network includes an access network and a core network (CN) to acquire an external network (such as the Internet) through the CN.
  • the service is communicated with other terminals.
  • the base station 130 and the base station 140 are access network devices.
  • the terminal 110 and the terminal 120 access the wireless network through different base stations. They can also access the wireless network through the same base station.
  • the procedure of the voice call is described below by taking the terminal 110 as the calling terminal and the terminal 120 as the called terminal as an example.
  • FIG. 2 is a schematic diagram of a voice call flow according to an embodiment of the present application.
  • the terminal 110 and the terminal 120 are in an idle state, and the terminal 110 needs to call the terminal 120 as an example for description.
  • the terminal 110 is in an idle state.
  • a radio resource control (RRC) connection establishment procedure is first initiated to the serving base station 130 to establish an RRC connection with the base station 130.
  • RRC radio resource control
  • the terminal 110 sends an RRC connection request (RRC connection request) message to the base station 130.
  • the base station 130 receives the RRC Connection Request message transmitted by the terminal 110 and performs the following step S202.
  • the base station 130 sends an RRC connection setup message to the terminal 110 in response to the RRC connection request message.
  • the terminal 110 receives the RRC Connection Setup message and performs the following step S203.
  • the terminal 110 sends an RRC connection setup complete message to the base station 130. After receiving the RRC Connection Setup Complete message sent by the terminal 110, the base station 130 successfully establishes the RRC connection.
  • the RRC connection request message is used by the terminal to request the establishment of an RRC connection to the base station, where the identifier of the terminal and the reason for the establishment are carried.
  • the base station 130 can know that the terminal 110 is to establish an RRC connection with the RRC connection request message, and then configure a signaling radio bearer (SRB) 1 for the terminal 110, and send the configuration information of the SRB1 to the RRC connection setup message to the terminal.
  • Terminal 110 After receiving the RRC connection setup message, the terminal 110 sends an uplink RRC connection setup complete message through the SRB1, which may carry an uplink non-access stratum (NAS) message, for example, in this embodiment, because the voice service is initiated.
  • NAS uplink non-access stratum
  • the RRC connection can therefore carry a voice service request message.
  • the base station 130 finds that there is no context of the terminal 110, and then sends an initial terminal message (also referred to as an initial UE message) to the CN, after the CN receives the initial terminal message.
  • An initial context setup request message is sent to the base station 130 to establish the context of the terminal 110. Steps S204 and S205 in the figure:
  • the base station 130 sends an initial UE message to the CN.
  • the CN receives the initial terminal message transmitted by the base station 130 and performs the following step S205.
  • S205 The CN sends an initial context setup request message to the base station 130.
  • the CN can inform the base station 130 to establish a default bearer.
  • the evolved packet system (EPS) bearer includes a default bearer (default bearer) and a dedicated bearer (dedicated bearer).
  • the default bearer is a bearer that satisfies the default quality of service (QoS) requirements. It is established as the terminal accesses the network. When the terminal leaves the network, it is released, providing an online IP transport service for the incoming terminal.
  • QoS quality of service
  • the base station 130 can notify the terminal 110 to establish a default bearer through an RRC connection reconfiguration message.
  • the DRX parameter can be configured for the terminal 110, and the DRX function of the terminal 110 is valid, including the following steps:
  • the base station 130 sends an RRC connection reconfiguration message to the terminal 110.
  • the RRC connection reconfiguration message includes a DRX configuration message, and the DRX configuration message is used to configure a DRX parameter of the terminal, where the DRX parameter is used to configure the DRX function of the terminal 110.
  • the terminal 110 receives the RRC connection reconfiguration message, and performs the DRX parameter of the configuration terminal 110 according to the DRX configuration message in the RRC connection reconfiguration message, and then performs the following step S207.
  • the terminal 110 feeds back the RRC connection reconfiguration complete (RRC connection reconfiguration complete) message to the base station 130.
  • the terminal 110 validates the DRX function of the terminal 110 according to the DRX parameter described above.
  • the base station 130 receives the RRC Connection Reconfiguration Complete message and performs the following step S208.
  • the base station 130 feeds back an initial context setup response message to the CN.
  • the CN receives the initial context setup response message, indicating that the context setup is complete.
  • the terminal 110 may initiate a Session Initiation Protocol (SIP) to initiate a voice call.
  • SIP Session Initiation Protocol
  • the terminal 110 sends an invite signaling for calling the terminal 120 to the CN via the base station 130, thereby initiating a SIP call procedure.
  • the CN receives the invitation signaling to learn that the terminal 110 is to call the terminal 120, but is not connected to the terminal 120. Therefore, the terminal 120 initiates paging, and performs the following step S210.
  • the CN sends a paging message to the called side base station 140.
  • the base station 140 receives the paging message and performs the following step S211.
  • the base station 140 forwards the paging message to the terminal 120.
  • the terminal 120 receives the paging message and initiates an RRC connection establishment process.
  • the RRC connection establishment process is the same as the above steps S201 to S203, and includes S211 to S214. after that,
  • the initial context and the establishment process of the default bearer include steps S215 to S219, which are the same as steps S204 to S208, and are not described herein again.
  • the base station 140 configures the DRX parameter for the terminal 120, so that the terminal 120 activates the DRX function. That is, the configuration message is included in the RRC connection reconfiguration message in step S217 to configure the DRX parameters of the terminal 120.
  • step S220 is performed.
  • S220 The CN forwards the invitation signaling to the terminal 120 via the base station 140.
  • the terminal 120 receives the invitation signaling, and sends a response message to the CN (S221).
  • the response message is a try signaling indicating that the terminal 120 has received the invitation signaling.
  • the CN After receiving the invitation signaling sent by the terminal 110, the CN sends a response message to the terminal 110 (S222), where the response message is an attempt signaling, indicating that the CN has received the invitation signaling.
  • This application does not limit the order in which the two trying signalings are sent.
  • the CN may initiate a voice bearer establishment process, including the following steps S223 to S226.
  • the CN sends an E-UTRAN radio access bearer (RAB setup request) message to the base station 130, that is, an E-UTB setup request (E-RAB setup request) message.
  • the E-RAB establishes a request message.
  • the E-RAB setup request message is used to trigger establishment of a voice bearer between the CN and the terminal 110.
  • the base station 130 After receiving the E-RAB setup request message, the base station 130 performs the following step S224.
  • the E-RAB established at this time is a dedicated bearer, where is a voice bearer carrying a voice service, for example, a bearer with a QoS Class Identifier (QCI) of 1.
  • QCI QoS Class Identifier
  • the base station 130 sends an RRC connection reconfiguration message to the terminal 110.
  • the terminal 110 receives the RRC connection reconfiguration message, and performs DRX parameter configuration on the terminal 110 according to the DRX configuration message in the RRC connection reconfiguration message, and then the terminal sends an RRC connection reconfiguration complete message to the base station 130 (S225), and the base station 130 receives the RRC.
  • an E-RAB setup response message is sent to the CN (S226).
  • the CN also triggers the establishment of a voice bearer with the terminal 120.
  • the specific steps S227 to S230 are the same as those of S223 to S226, and are not described again.
  • the sequence of establishing voice bearers of the terminal 110 and the terminal 120 is not limited.
  • the terminal 110 and the terminal 120 continue the SIP process, and the terminal 120 notifies the terminal 110 by SIP signaling in the states of ringing and turning on (signaling is called 200 OK), and after the terminal 110 performs an acknowledgment (ACK), the terminal A voice call can be made between the 110 and the terminal 120.
  • SIP and voice call flow as shown in Figure 2.
  • the terminal 110 and the terminal 120 are effective when the default bearer is established, and the downlink signaling received by the subsequent terminal 110 and the terminal 120 before the voice is connected may be affected by the DRX.
  • the DRX parameters configured by the base station include a DRX cycle.
  • time is divided into consecutive DRX cycles.
  • the DRX cycle includes an On Duration and a dormant period (also known as Opportunity for DRX).
  • the terminal monitors the PDCCH, so that downlink data of the downlink channel can be received.
  • the terminal does not monitor the PDCCH and does not receive downlink data of the downlink channel to save power consumption.
  • the DRX function is activated after the step 110 of the terminal 110, and the DRX function of the terminal 120 is effective after the step S217, and the DRX function of the terminal 110 or the terminal 120 is always in the working state.
  • the base station finds that the terminal 110 or the terminal 120 is in the dormant period and cannot be scheduled, and waits until the activation period is scheduled, thereby causing the voice call to be connected. The delay of the passage increases.
  • PDCP Packet Data Convergence Protocol
  • the downlink signaling may include SIP signaling and RRC signaling, for example, trying signaling in S222; for example, the RRC connection reconfiguration message in step S224 above.
  • the downlink signaling may include SIP signaling and RRC signaling, for example, invoke signaling in S220; for example, the RRC connection reconfiguration message in step S228 above.
  • the terminal 110 and the terminal 120 are in an idle state to perform a voice call.
  • the terminal 110 When the terminal 110 is in the RRC connected state, the above RRC connection establishment process and the default bearer establishment process may be omitted.
  • the terminal 110 also implements the DRX function when establishing an RRC connection and a default bearer for other services. Therefore, the voice call connection process is still affected by the DRX.
  • the RRC connection reconfiguration message of step S224 above may be affected by DRX.
  • the terminal 120 faces the same problem if it is in the RRC connected state.
  • a precondition can also be prepared in the voice communication, in which more SIP signaling is affected.
  • the Precondition scheme reserves resources for the current call before the call is established to prevent ghost ringing and voice interruption.
  • ghost ringing means that the phone is hung up due to insufficient network resources, etc., at the moment the called terminal just starts ringing.
  • Voice drop refers to the situation where the called terminal is disconnected and dropped when it is just started to be answered.
  • FIG. 4 is a SIP signaling flow diagram provided by an embodiment of the present application.
  • the calling terminal sends Invite signaling to the called terminal through the CN.
  • the CN receives the Invite signaling sent by the calling terminal, and feeds back the Trying signaling, indicating that it has been received;
  • the called terminal receives the Invite signaling sent by the CN, and feeds back the Trying signaling, indicating that it has received.
  • the called terminal sends 183 Session signaling to the CN, and the CN forwards it to the calling terminal.
  • the signaling Used to indicate progress information for establishing a session.
  • the dedicated bearer of the called terminal at this time is established here for the voice bearer.
  • the calling terminal sends a temporary response message through the CN, and the PRACK signaling indicates that the 183 Session signaling is received.
  • the calling terminal establishes a dedicated bearer.
  • the called terminal sends 200 OK signaling to the calling terminal through the CN, indicating that the 183Session signaling request has been processed successfully.
  • the calling terminal sends Update (Update) signaling to the called terminal through the CN, and is used to negotiate Session Description Protocol (SDP) information with the called terminal.
  • the called terminal feeds back 200 OK signaling through the CN, indicating that the Update request has been processed successfully.
  • the called terminal rings and sends ringing signaling to the calling terminal through the CN, indicating that the called terminal is ringing.
  • the called terminal sends 200 OK signaling to the calling terminal through the CN, indicating that the original Invite request has been processed successfully.
  • the calling terminal feeds back the acknowledgement (ACK) signaling to the called terminal through the CN, and is used to notify the called terminal.
  • the calling terminal has learned that the called terminal processes the Invite request successfully. At this point, you can start a voice call.
  • the SIP signaling after the 183Session (which may include the 183Session signaling may also not include the 183Session signaling) is performed after the calling terminal and the called terminal voice bearer are established, that is, in the step in FIG.
  • the SIP signaling procedure includes SIP signaling after the 183 Session in Figure 4.
  • these SIP flows are performed before the voice bearer is established, so that resources are reserved for the call, and thus more downlink SIP signaling receives the DRX impact.
  • the information that may be affected includes: Invite signaling, PRACK signaling, etc.
  • the negotiation further includes Update signaling
  • the Update signaling may not be included, and non-SIP signaling may be included.
  • the messages that may be affected include: Trying signaling, 183Session signaling, Ringing signaling, 200 OK signaling, PRACK signaling, etc., and non-SIP signaling to establish a voice bearer RRC connection reconfiguration message. .
  • the DRX management method provided by the embodiment of the present application.
  • the effect is that the DRX function of the terminal is not enabled before the voice bearer is established, and is not enabled when the voice bearer is set up.
  • the base station does not take effect of the terminal DRX function.
  • the voice bearer is established, the DRX is sent.
  • the parameter which is the DRX function of the terminal.
  • the base station configures the DRX function of the terminal to disable the DRX function of the terminal.
  • the DRX parameter is sent to implement the DRX function of the terminal.
  • FIG. 5 is a flowchart of a DRX management method according to an embodiment of the present application:
  • S510 The base station determines that the terminal has a voice service.
  • the base station establishes a voice bearer for the terminal, and when the voice bearer is established for the terminal, the DRX function of the terminal is valid. Specifically, the base station may send a configuration message to the terminal when determining that the terminal has a voice service, where the configuration message is used. The voice bearer of the terminal is configured, and the DRX parameter is carried in the configuration message to validate the DRX function of the terminal.
  • the configuration message is, for example, an RRC Connection Reconfiguration message.
  • the terminal receives the configuration message and performs the following operations:
  • S530 The terminal starts the DRX function, and starts the DRX function according to the DRX parameter in the configuration message.
  • the terminal does not take effect of the DRX function until the voice bearer is established; when the voice bearer is established, the DRX function is re-enabled, thereby reducing the delay of the voice call connection.
  • the base station may not implement the DRX function of the terminal when establishing a default bearer for the terminal. It is especially applicable to the scenario in which the base station determines that the terminal has a voice service before the default bearer is established. In this case, when the RRC connection and the default bearer are established due to the non-voice service, the function of the terminal DRX is effective, which is beneficial to the power saving of the terminal. Of course, it is also possible to confirm whether the terminal has a voice service when the default bearer is established, and the DRX function of the terminal is not valid. At this time, the management complexity of the base station can be reduced, and the DRX does not take effect only before the dedicated bearer is established, and the power saving effect on the terminal is not large.
  • the foregoing method further includes:
  • the base station establishes a default bearer for the terminal, and when the default bearer is established for the terminal, the base station does not perform the DRX function of the terminal. Specifically, the base station may send a configuration message to the terminal when determining that the terminal has the voice service.
  • the configuration message is the first configuration message
  • the configuration message in the step S540 is the first configuration message.
  • the second configuration message is used to configure the default bearer of the terminal, and the DRX parameter is not carried in the second configuration message, so that the DRX function of the terminal is not valid.
  • the configuration message is, for example, an RRC Connection Reconfiguration message.
  • the terminal After the default bearer is established, it is determined that the terminal has a voice service, and the terminal may be determined to have a voice service before the default bearer is established.
  • the terminal before receiving the first configuration message sent by the base station, the terminal further receives a second configuration message sent by the base station (for example, the configuration message in step S206 in FIG. 2), where the second configuration message is used to configure the default bearer of the terminal.
  • the second configuration message does not include the DRX parameter. Therefore, the terminal does not start the DRX function when the default bearer is established.
  • the foregoing method further includes:
  • the base station sends a message to the terminal for deactivating the DRX function of the terminal. Specifically, the configuration message is sent to the terminal (in order to distinguish from the above configuration message, referred to as a third configuration message), and the configuration message is used to configure the DRX function of the terminal.
  • the terminal performs the following steps before receiving the first configuration message sent by the base station:
  • the terminal receives a second configuration message sent by the base station (the configuration message in step S206 in FIG. 2), where the second configuration message is used to configure a default bearer of the terminal, and the second configuration message includes a DRX parameter.
  • S570 The terminal starts the DRX function according to the DRX parameter in the second configuration message.
  • S550 The terminal receives a third configuration message, where the third configuration message is used to configure the DRX function of the terminal.
  • S580 The terminal configures the DRX function according to the third configuration message.
  • the terminal turns on the DRX function when the default bearer is established, but when the base station recognizes that the terminal has the voice service, the DRX function is turned off, thereby reducing the impact of the DRX function on the paging connection.
  • the base station can take effect when determining that the terminal has voice service.
  • the DRX function uses the above method to reduce the delay of voice call connection.
  • the DRX function of the base station effective terminal may be implemented by carrying the DRX parameter in the RRC connection reconfiguration message sent to the terminal in the RRC connection reconfiguration process. Since the DRX function of the terminal does not take effect when the RRC connection reconfiguration message is sent, the sending and receiving of the RRC connection reconfiguration message are not affected by the DRX, ensuring low delay establishment of the voice bearer and reducing voice. The delay in which the call is connected.
  • step S540 when the base station establishes a default bearer for the terminal, the DRX function of the terminal does not take effect, and the DRX parameter is not carried in the RRC connection reconfiguration message sent to the terminal in the RRC connection reconfiguration process.
  • the base station sends a message for deactivating the DRX function of the terminal to the terminal, which may be implemented by carrying the cell that releases the DRX parameter in the RRC connection reconfiguration message sent to the terminal in the RRC connection reconfiguration process. .
  • the above DRX parameters or the cells that release the DRX parameters are carried in the RRC connection reconfiguration message.
  • the present application is not limited thereto, and may also be carried in other messages, that is, the DRX parameters herein.
  • the message carrier is not limited.
  • the base station can determine that the terminal has a voice service by using various methods.
  • the base station may determine whether the terminal has a voice service according to the cause value carried in the RRC connection request message when receiving the RRC connection request message sent by the terminal.
  • the above step S510 may include the following steps:
  • the base station receives the RRC connection request message sent by the terminal, where the RRC connection request message includes a cause value, where the cause value is used to indicate the reason for initiating the RRC connection request.
  • S520 The base station determines, according to the cause value, that the terminal has a voice service.
  • the cause value carried in the RRC connection setup request is a voice call mobile initiator, such as mo-VoiceCall, where mo is mobile original abbreviation of.
  • the base station may determine, according to the cause value, that the terminal is the calling terminal, that is, the terminal determines that the terminal has a voice service.
  • the cause value carried in the RRC connection setup request is a voice call mobile called party, such as mt-VoiceCall, where mt is an abbreviation of mobile terminated.
  • the base station determines, according to the cause value, that the terminal is the called terminal, that is, determines that the terminal has a voice service.
  • the reason value here is only an example, and the specific form of the reason value is not limited.
  • the base station can determine whether the terminal has a voice service according to the cause value when the terminal initiates an RRC connection, and then the DRX function of the terminal is not valid when the default bearer is established.
  • the DRX function of the terminal is effective only when the voice bearer is established. This reduces the impact of the terminal's DRX function on voice calls and reduces the delay of voice call connection.
  • the paging information may be added to the paging message to indicate that the terminal has a voice service, or is used to indicate that the terminal is a called terminal.
  • the indication information may be a specially set cell; or may be a paging priority, the base station and the CN have previously agreed that the paging priority is used to indicate that the terminal has a voice service, or that the terminal is a voice terminal.
  • a paging priority may be agreed to indicate that the terminal has a voice service or the terminal is a called terminal.
  • the configuration may be agreed that the paging priority that is consistent between the configuration of the base station and the CN is used to indicate that the terminal has a voice service, or the terminal is a called terminal.
  • the terminal is considered to have a voice service or a called terminal.
  • the base station may save the identifier of the terminal, such as a SAE-temporary mobile subscriber identity (S-TMSI), where the SAE is a system, when the paging priority is included in the paging message.
  • S-TMSI SAE-temporary mobile subscriber identity
  • the terminal obtains the identifier of the terminal in the RRC connection request message, and the terminal that is consistent with the identifier of the locally saved terminal is regarded as the called terminal or the terminal having the voice service, so that the terminal can be identified as having For the voice service, the DRX function does not take effect when the default bearer is established for the terminal. When the voice bearer is established, the DRX function is valid.
  • the cell When the terminal is identified by a specially configured cell, the cell may be a voice terminal indication letter.
  • the element such as LTE, can be VOLTEUSER INDICATION.
  • the name and form of the cell are not limited only by way of example.
  • the CN when the CN pages the called terminal 120, the CN carries the voice terminal indication cell in the paging message, and the base station 140 receives the paging message and finds the voice terminal indication cell carried therein.
  • the terminal is considered to have a voice service or a called terminal.
  • the base station may save the identifier of the terminal, for example, S-TMSI.
  • the terminal obtains the identifier of the terminal in the RRC connection request message, and the terminal that is consistent with the identifier of the locally saved terminal is regarded as the called terminal or the terminal having the voice service, so that the terminal can be identified as having For the voice service, the DRX function does not take effect when the default bearer is established for the terminal. When the voice bearer is established, the DRX function is valid.
  • the base station determines a method for the terminal to have a voice service, including: the base station parses the paging message of the terminal, and saves the identifier of the terminal when the paging message includes the indication information; the base station receives the RRC connection request message sent by the terminal, and the RRC connection request The message includes the identifier of the terminal.
  • the base station determines that the terminal has a voice service or determines that the terminal is the called terminal.
  • an indication cell is added in the initial context setup request message, and the indication cell is used to indicate that the terminal has a voice service.
  • the indication cell may also be used to indicate that the terminal is the calling terminal.
  • the indicating cell may also be used to indicate that the terminal is called. terminal.
  • the indication cell may be added to the initial context setup request message in step S205 on the calling side.
  • the indication cell may be added to the initial context setup request message in step S216 on the called side.
  • the terminal can be determined to have a voice service before or during the establishment of the default bearer. Therefore, when the default bearer is established, the DRX function of the terminal is not valid, but the voice bearer is established. The DRX function of the terminal is effective.
  • the terminal when the base station 130 determines that the terminal 110 has a voice service, the terminal does not configure the DRX parameter of the terminal 110 in step S206, but configures the DRX parameter of the terminal 110 in step S224.
  • the base station 140 determines that the terminal 120 has a voice service, it does not configure the DRX parameter of the terminal 120 in step S217, and configures the DRX parameter of the terminal 120 in step S228.
  • the base station delays the DRX function of the effective terminal, thereby reducing the delay of the voice paging connection.
  • the base station can also identify whether the terminal has a message by parsing the message on the default bearer.
  • There is a voice service For example, after the default bearer is established, the base station parses the data packet on the default bearer, and finds that the SIP signaling is carried on the base station, and determines that the terminal has the voice service.
  • the method can be used in any voice call scenario, and has a better effect on a scenario in which a terminal initiates a voice service in an RRC connected state or as a voice called. For example, the terminal establishes an RRC connection and a default bearer for the non-voice service. At this time, the DRX of the terminal has been validated.
  • the base station can use the method shown in FIG. 7 to perform the DRX function of the terminal, for example, sending the RRC. Connect the reconfiguration message to release the DRX configuration. When the voice bearer is set up, the DRX function takes effect and the DRX parameters are delivered.
  • the default bearer in the foregoing embodiment includes a bearer with a QCI of 5 when the terminal has a voice service
  • the voice bearer is a dedicated bearer, including a bearer with a QCI of 1.
  • the DRX parameters used in the DRX function that takes effect when the voice bearer is established are consistent with the characteristics of voice communication, and therefore have little effect on subsequent voice communications.
  • the implementation of the method performed by the base station in any of the above embodiments may be implemented by the DRX management apparatus 800 shown in FIG. 8.
  • the apparatus includes a determining unit 810 and an establishing unit 820, where:
  • the determining unit 810 is configured to determine that the terminal has a voice service.
  • the establishing unit 820 is configured to establish a voice bearer for the terminal, and when the voice bearer is established for the terminal, the DRX function of the terminal is valid.
  • the DRX function of the active terminal can be delayed, thereby reducing the delay of the voice call connection.
  • the establishing unit 820 is further configured to establish a default bearer for the terminal before establishing a voice bearer for the terminal, and when the default bearer is established for the terminal, the DRX function of the terminal is not valid.
  • the apparatus when the establishing unit 820 has already activated the DRX function of the terminal before establishing the voice bearer, the apparatus further includes a de-effectiveing unit 830, configured to send a message for deactivating the DRX function of the terminal to the terminal.
  • a de-effectiveing unit 830 configured to send a message for deactivating the DRX function of the terminal to the terminal.
  • the establishing unit 820 can validate the DRX function of the terminal by sending a configuration message to the terminal.
  • the configuration message is used to configure the voice bearer of the terminal, and includes the DRX parameter.
  • configuration message may be an RRC connection reconfiguration message or other messages.
  • the format of the configuration message is not limited here.
  • the determining unit 810 determines whether the terminal has the voice service in the same manner as the foregoing method embodiment, and details are not described herein again.
  • each unit of the above device is only a division of a logical function, and the actual implementation may be integrated into one physical entity in whole or in part, or may be physically separated.
  • these units may all be implemented in the form of software by means of processing component calls; or may be implemented entirely in hardware; some units may be implemented by software in the form of processing component calls, and some units may be implemented in the form of hardware.
  • the determining unit 810 may be a separately set processing element, or may be integrated in a certain chip of the base station, or may be stored in a memory of the base station in the form of program code, and is called and executed by a processing element of the base station. Determine the function of the unit.
  • the implementation of other units is similar.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or by a processing element calling an instruction in the form of software.
  • the above units may be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (digital) Singnal processor (DSP), or one or more Field Programmable Gate Array (FPGA).
  • ASICs Application Specific Integrated Circuits
  • DSP digital Singnal processor
  • FPGA Field Programmable Gate Array
  • the processing element can be a general purpose processor, such as a Central Processing Unit (CPU) or other processor that can invoke program code.
  • CPU Central Processing Unit
  • these units can be integrated and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • FIG. 9 is a schematic structural diagram of a base station according to an embodiment of the present application.
  • the base station includes a processor 910, a memory 920, and a transceiver 930.
  • the transceiver 930 can be coupled to an antenna.
  • the memory 920 is configured to store program code for implementing various units of the above method embodiment or device embodiment, and the processor 910 calls the program code to perform the operation of the base station in the implementation of the above method.
  • the implementation of the method performed by the terminal in any of the foregoing embodiments may be implemented by the DRX management apparatus 1000 shown in FIG. 10, where the apparatus includes a transceiver unit 1010 and a processing unit 1020, where the transceiver unit 1010 is configured to receive the first sent by the base station.
  • the configuration message is used to configure the voice bearer of the terminal, and the first configuration message includes a DRX parameter.
  • the processing unit 1020 is configured to start the DRX function according to the DRX parameter.
  • the transceiver unit 1010 is further configured to receive a second configuration message sent by the base station, where the second configuration message is used to configure a default bearer of the terminal, where the second configuration message does not include The DRX parameter, in this way, the terminal does not start the DRX function when the default bearer is established.
  • the transceiver unit 1010 is further configured to receive a second configuration message sent by the base station, where the second configuration message is used to configure a default bearer of the terminal, where the second configuration message includes the DRX.
  • the processing unit 1020 starts the DRX function according to the DRX parameter in the second configuration message.
  • the transceiver unit 1010 is further configured to receive a third configuration message, where the third configuration message is used to configure the DRX function of the terminal, and the processing unit 1020 is configured to:
  • the DRX function is configured according to the third configuration message.
  • the terminal turns on the DRX function when the default bearer is established, but when the base station recognizes that the terminal has the voice service, the DRX function is turned off, thereby reducing the impact of the DRX function on the paging connection.
  • the transceiver unit 1010 is further configured to: when the RRC connection request is sent to the base station in the idle state, carry the cause value, where the cause value is used to indicate the reason for initiating the RRC connection request, so that the base station determines, according to the cause value, that the terminal has the voice service.
  • the cause value is a voice call mobile initiator, such as mo-VoiceCall; when the terminal is the called terminal, the cause value is a voice call mobile receiver, such as mt-VoiceCall.
  • the transceiver unit may be a transceiver of the terminal, and the processing unit may be a processor of the terminal.
  • FIG. 11 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • the base station includes a processor 1110, a memory 1120, and a transceiver 1130.
  • the transceiver 1130 can be connected to an antenna.
  • the memory 1120 is configured to store program code for implementing various units of the above method embodiment or device embodiment, and the processor 1110 calls the program code to perform the operation of the terminal in the above method implementation.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used for carrying or storing in the form of an instruction or data structure.
  • connection may suitably be a computer readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the fixing of the associated media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供的非连续接收DRX的管理方法，包括：基站确定终端具有语音业务，基站为终端建立语音承载，且在为终端建立语音承载时，生效终端的DRX功能。可见，以上方法中，终端在语音承载建立之前，不生效DRX功能；直至语音承载建立时，再生效DRX功能，以有效地减少语音寻呼接通的时延。

Description

非连续接收的管理方法和装置 技术领域
本申请实施例涉及通信技术领域，并且更具体地，涉及非连续接收的管理方法和装置。
背景技术
不同的通信网络，语音业务的承载机制不同。如，在第二代移动通信技术或者第三代移动通信技术网络中，语音业务承载于电路交换(Circuit Switched，CS)域。再如，在长期演进(Long Term Evolution，LTE)系统中，语音业务承载于分组交换(Packet Switched，PS)域，通过把语音业务和其它业务数据一样，打包成互联网协议(Internet Protocol，IP)数据包进行传输，实现端到端的语音通信。相对于CS域网络，PS域网络能够为用户提供更快更高质量的语音业务服务。
业务数据流通常是突发性的，在一段时间内有数据传输，但在接下来的一段时间内没有数据传输。基于此，引入了非连续接收(Discontinuous reception，DRX)机制，以降低终端的能量消耗。该机制是使终端在一段时间(可以称为休眠期)内停止监听物理下行控制信道(physical downlink control channel，PDCCH)，在进入激活状态时才监听PDCCH，如此，终端不用时时监听PDCCH，从而降低终端的能量消耗。
然而，在语音呼叫过程中，DRX技术的引入会增加语音呼叫接通时延，从而导致用户体验下降。
发明内容
有鉴于此，本申请实施例提供了DRX的管理方法和装置，以期减少语音呼叫接通的时延。
第一方面，提供了一种DRX的管理方法，包括：
基站确定终端具有语音业务；基站为终端建立语音承载，且在为终端建立语音承载时，生效终端的DRX功能。
可见，终端在语音承载建立之前，不生效DRX功能；直至语音承载建立时，再生效DRX功能，从而减少语音呼叫接通的时延。
以上生效是指在建立语音承载之前，终端的DRX功能未开启，在建立语音承载时才 开启，例如，在建立默认承载时，基站不生效终端DRX功能，等到语音承载建立时，才发送DRX参数，生效终端的DRX功能。或者，在建立语音承载之前，当终端的DRX功能已经开启，基站去配置终端的DRX功能，以关闭终端的DRX功能，等到语音承载建立时，才发送DRX参数，生效终端的DRX功能。以上去生效是指在建立语音承载之前，当终端的DRX功能已经开启，基站去配置终端的DRX功能，以关闭终端的DRX功能。
可选的，基站为终端建立语音承载之前，还包括：基站为终端建立默认承载，且在为终端建立默认承载时，基站不生效终端的DRX功能。
可选的，当在基站为终端建立语音承载之前，基站已经生效了终端的DRX功能时，以上方法还包括：基站向终端发送用于去生效终端的DRX功能的消息。基站生效终端的DRX功能可以通过在RRC连接重配置过程，在向终端发送的RRC连接重配置消息中携带DRX参数来实现。由于在该RRC连接重配置消息发送时，终端的DRX功能并未生效，因此该RRC连接重配置消息的发送和接收并不受DRX的影响，保证了语音承载的低时延建立，减少了语音呼叫接通的时延。
基站为终端建立默认承载时，不生效终端的DRX功能，可以通过在在RRC连接重配置过程，在向终端发送的RRC连接重配置消息中不携带DRX参数来实现。
基站向终端发送用于去生效终端的DRX功能的消息，可以通过在RRC连接重配置过程，在向终端发送的RRC连接重配置消息中携带释放DRX参数的信元来实现。
在以上方法中，基站确定终端具有语音业务的方法，可以包括以下几种方式：
方式一、基站接收终端发送的RRC连接请求消息，该RRC连接请求消息包括原因值，该原因值用于指示发起RRC连接请求的原因；基站根据该原因值确定终端具有语音业务。进一步的，当原因值为语音呼叫移动发起方时，如mo-VoiceCall，则基站根据该原因值确定终端具有语音业务，且可以确定该终端为主叫终端。当原因值为语音呼叫移动接收方时，如mt-VoiceCall，则基站根据该原因值确定终端具有语音业务，且可以确定该终端为被叫终端。
方式二、基站根据寻呼消息确定终端具有语音业务，具体包括：
基站从核心网接收终端的寻呼消息，寻呼消息包括指示信息，该指示信息用于指示终端具有语音业务；基站根据指示信息确定终端具有语音业务。
该指示信息可以为寻呼优先级，则根据指示信息确定终端具有语音业务的过程包括：当基站确定寻呼优先级为第一寻呼优先级时，确定终端具有语音业务，其中第一寻呼优先级为设定的用于指示终端具有语音业务的寻呼优先级。该方法可以与现有协议兼 容，具有较好的兼容性。
该指示信息可以为专用于指示终端具有语音业务的信元，例如语音终端指示信元，此时，基站根据指示信息确定终端具有语音业务的过程，包括：当基站确定寻呼消息包括语音终端指示信元时，基站确定终端具有语音业务。
方式三、基站根据初始上下文建立请求消息确定终端具有语音业务，具体包括：
基站接收初始上下文建立请求消息，初始上下文建立请求消息中包括指示信元，指示信元用于指示终端具有语音业务；基站根据该指示信元确定终端具有语音业务。
方式四、基站解析默认承载上的信息，当确定默认承载上承载的信息为SIP信令时，确定终端具有语音业务。
以上方式一至三中，可以在默认承载建立之前或建立时就确定出终端具有语音业务，因此可以在默认承载建立时，不生效终端的DRX功能，而在语音承载建立时生效终端的DRX功能。
以上方式四可以用于任何语音呼叫场景，对于终端处于RRC连接态时发起语音业务或者作为语音被叫的场景，具有更好的效果。例如终端因为非语音业务建立RRC连接和默认承载，此时终端的DRX已经被生效，当判断出终端具有语音业务时，基站可以去生效终端的DRX功能；当语音承载建立时，再生效DRX功能，下发DRX参数。
以上默认承载在终端具有语音业务时包括QCI为5的承载，语音承载为专用承载，包括QCI为1的承载。
第二方面，提供了一种DRX的管理装置，用于基站，包括用于执行以上第一方面的任一方法各个步骤的单元或者手段(means)。
第三方面，提供了一种DRX的管理装置，包括处理器和存储器，存储器用于存储程序，处理器调用存储器存储的程序，以执行以上第一方面的任一方法。
第四方面，提供了一种DRX的管理装置，包括用于执行以上第一方面的任一方法的至少一个处理元件或芯片。
第五方面，提供了一种程序，该程序在被处理器执行时用于执行以上第一方面的任一方法。
第六方面，提供了一种计算机可读存储介质，包括第五方面的程序。
第七方面，提供一种DRX的管理方法，由终端执行，包括：
终端接收基站发送的第一配置消息，所述第一配置消息用于配置终端的语音承载，所述第一配置消息包括DRX参数；
终端根据所述DRX参数，启动DRX功能。
可选的，终端在接收基站发送的第一配置消息之前，还接收基站发送的第二配置消息，该第二配置消息用于配置终端的默认承载，该第二配置消息不包括DRX参数，如此，终端在默认承载建立时，不启动DRX功能。
可选的，终端在接收基站发送的第一配置消息之前，以上方法还包括：
终端接收基站发送的第二配置消息，该第二配置消息用于配置终端的默认承载，该第二配置消息包括DRX参数；
终端根据第二配置消息中的DRX参数，启动DRX功能；
终端接收第三配置消息，该第三配置消息用于去配置终端的DRX功能；
终端根据该第三配置消息去配置DRX功能。
如此，终端在虽然在默认承载建立时开启了DRX功能，但是在基站识别出该终端具有语音业务时，关闭了该DRX功能，因此降低了DRX功能对寻呼接通的影响。
可选的，所述终端在空闲态向基站发送RRC连接请求时，携带原因值，该原因值用于指示发起RRC连接请求的原因，以便基站根据该原因值确定终端具有语音业务。进一步的，当终端为主叫终端时，原因值为语音呼叫移动发起方，如mo-VoiceCall；当终端为被叫终端时，原因值为语音呼叫移动接收方，如mt-VoiceCall。
第八方面，提供了一种DRX的管理装置，用于终端，包括用于执行以上第七方面的任一方法各个步骤的单元或者手段(means)。
第九方面，提供了一种DRX的管理装置，包括处理器和存储器，存储器用于存储程序，处理器调用存储器存储的程序，以执行以上第七方面的任一方法。
第十方面，提供了一种DRX的管理装置，包括用于执行以上第七方面的任一方法的至少一个处理元件或芯片。
第十一方面，提供了一种程序，该程序在被处理器执行时用于执行以上第七方面的任一方法。
第十二方面，提供了一种计算机可读存储介质，包括第十一方面的程序。
可见，本申请实施例提供的DRX的管理方法和装置，可以使终端在语音承载建立之前，不生效DRX功能；语音承载建立时，才生效DRX功能。因此，延迟生效了终端的DRX功能，从而有效地减少语音寻呼接通的时延。
附图说明
图1是本申请实施例提供的一种语音呼叫场景示意图；
图2是本申请实施例提供的一种语音呼叫流程的示意图；
图3是本申请实施例提供的一种DRX周期示意图；
图4是本申请实施例提供的一种SIP信令流图；
图5是本申请实施例提供的一种DRX的管理方法的流程图；
图6是本申请实施例提供的另一种DRX的管理方法的流程图；
图7是本申请实施例提供的又一种DRX的管理方法的流程图；
图8是本申请实施例提供的一种DRX的管理装置的示意图；
图9是本申请实施例提供的一种基站的结构示意图；
图10是本申请实施例提供的另一种DRX的管理装置的示意图；
图11是本申请实施例提供的一种终端的结构示意图。
具体实施方式
以下对本申请实施例中的部分用语进行解释，便于本领域技术人员理解。
1)、终端，又称之为用户设备(User Equipment，UE)，是一种向用户提供语音和/或数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。常见的终端例如包括：手机、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，例如智能手表、智能手环、计步器等。
2)、基站，又称为无线接入网(Radio Access Network，RAN)设备，是一种将终端接入到无线网络的设备，包括但不限于：传输接收点(Transmission Reception Point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(Base Station Controller，BSC)、基站收发台(Base Transceiver Station,BTS)、家庭基站(例如，Home evolved NodeB，或Home Node B，HNB)、基带单元(BaseBand Unit，BBU)。此外，还可以包括Wifi接入点(Access Point，AP)等。
3)、“多个”是指两个或两个以上，其它量词与之类似。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
下面结合附图对本申请实施例进行描述。
请参考图1，其为本申请实施例提供的一种语音呼叫场景示意图。如图1所示，终端110和终端120分别通过基站130和基站140接入到无线网络，无线网络包括接入网和核心网(core network，CN)，以通过CN获取外网(例如因特网)的服务或者与其它终端通信，其中基站130和基站140为接入网设备，以终端110和终端120通过不同基站接入无线网络为例，它们也可以通过相同的基站接入无线网络。
以下以终端110为主叫终端，终端120为被叫终端为例，描述语音呼叫的流程。
请参见图2，其为本申请实施例提供的一种语音呼叫流程的示意图。在此，终端110和终端120处于空闲(idle)态，且终端110需要呼叫终端120为例进行描述。
终端110处于空闲态，当需要呼叫终端120时，首先向其服务基站130发起无线资源控制(radio resource control，RRC)连接建立流程，以与基站130建立RRC连接。该RRC连接建立流程如下，其为本领域技术人员所知道，不再详述：
S201：终端110向基站130发送RRC连接请求(RRC connection request)消息。基站130接收终端110发送的RRC连接请求消息并执行以下步骤S202。
S202：基站130响应于RRC连接请求消息向终端110发送RRC连接建立(RRC connection setup)消息。终端110接收RRC连接建立消息并执行以下步骤S203。
S203：终端110向基站130发送RRC连接建立完成(RRC connection setup complete)消息。基站130接收终端110发送的RRC连接建立完成消息后，RRC连接建立成功。
RRC连接请求消息用于终端向基站请求建立RRC连接，其中携带终端的标识和建立原因。基站130根据该RRC连接请求消息可以知道终端110要与之建立RRC连接，则为终端110配置信令无线承载(signaling radio bearer，SRB)1，并将SRB1的配置信息通过RRC连接建立消息发送给终端110。终端110接收到RRC连接建立消息之后，通过SRB1发送上行RRC连接建立完成消息，其中可以携带上行非接入层(non-access stratum，NAS)消息，例如在本实施例中是因为语音业务发起的RRC连接，因此可以携带语音业务请求(service request)消息。
在终端110与基站130之间的RRC连接建立之后，基站130发现没有终端110的上下文，于是向CN发送初始终端消息(又称为初始UE消息，initial UE message)，CN接收到初始终端消息之后，向基站130发送初始上下文建立请求(initial context setup request)消息，以建立终端110的上下文。如图中步骤S204和S205：
S204：基站130向CN发送初始UE消息。CN接收基站130发送的初始终端消息并执行以下步骤S205。
S205：CN向基站130发送初始上下文建立请求(initial context setup request)消息。
在此过程中，CN可以通知基站130建立默认承载。演进分组系统(evolved packet system，EPS)承载包括默认承载(default bearer)和专用承载(dedicated bearer)。默认承载是一种满足默认服务质量(quality of service，QoS)要求的承载，会随着终端接入网络而建立，当终端离开网络时会释放，为入网终端提供在线的IP传输服务。专有承载在默认承载建立的基础上为了提供特定的QoS传输需求而建立的承载。例如，原有的默认承载无法满足语音呼叫的QoS要求，就需要创建专用承载。
基站130可以通过RRC连接重配置消息通知终端110建立默认承载。此时可以为终端110配置DRX参数，生效终端110的DRX功能，包括如下步骤：
S206：基站130向终端110发送RRC连接重配置(RRC connection reconfiguration)消息。
其中，RRC连接重配置消息包括DRX配置消息，DRX配置消息用于配置终端的DRX参数，该DRX参数用于配置终端110的DRX功能。终端110接收RRC连接重配置消息，并根据该RRC连接重配置消息中的DRX配置消息进行配置终端110的DRX参数，而后执行以下步骤S207。
S207：终端110向基站130反馈RRC连接重配置完成(RRC connection reconfiguration complete)消息。其中终端110会根据上述的DRX参数生效终端110的DRX功能。基站130接收RRC连接重配置完成消息并执行以下步骤S208。
S208：基站130向CN反馈初始上下文建立响应(initial context setup response)消息。CN接收初始上下文建立响应消息，表明上下文建立完成，此时，默认承载建立完成，终端110可以发起会话发起协议(Session Initiation Protocol，SIP)，以发起语音呼叫，图中虚线所示的步骤均为SIP信令流程，执行以下步骤S209。
S209：终端110经过基站130向CN发送用于呼叫终端120的邀请(invite)信令，从而发起SIP呼叫流程。CN接收邀请信令获知终端110要呼叫终端120，但与终端120之间并没有连接，因此向终端120发起寻呼，执行以下步骤S210。
S210：CN向被叫侧基站140发送寻呼(paging)消息。基站140接收寻呼消息并执行以下步骤S211。
S211：基站140将寻呼消息转发给终端120。终端120接收寻呼消息并发起RRC连接建立过程，该RRC连接建立过程同以上步骤S201至S203，包括S211至S214。之后， 初始上下文及默认承载的建立过程包括步骤S215至S219，同步骤S204至S208，此处不再赘述。
需要说明的是，终端120与基站140之间的RRC连接重配置过程中，基站140为终端120配置DRX参数，使得终端120生效DRX功能。即在步骤S217中的RRC连接重配置消息中包括配置消息，以配置终端120的DRX参数。
被叫侧上下文及默认承载建立完成后，执行以下步骤S220。
S220：CN经过基站140向终端120转发上述邀请信令。
终端120收到邀请信令，向CN发送响应消息(S221)，该响应消息为尝试(trying)信令，表明终端120已经收到邀请信令。CN收到终端110发送的邀请信令后，向终端110发送响应消息(S222)，该响应消息为尝试信令，表明CN已经收到邀请信令。本申请不限制这两个trying信令发送的先后顺序。
此时，CN可以发起语音承载的建立过程，包括以下步骤S223至S226。
S223：CN向基站130发送演进型通用陆地无线接入网(evolved universal terrestrial radio access network，E-UTRAN)无线接入承载(radio access bearer，RAB)建立请求(E-RAB setup request)消息，即E-RAB建立请求消息。其中，E-RAB建立请求消息用于触发CN和终端110之间建立语音承载。基站130收到E-RAB建立请求消息后执行以下步骤S224。
需要说明的是，此时建立的E-RAB是专用承载，在此为承载语音业务的语音承载，例如QoS分类识别码(QoS Class Identifier，QCI)为1的承载。
S224：基站130向终端110发送RRC连接重配置消息。终端110接收RRC连接重配置消息，并根据该RRC连接重配置消息中的DRX配置消息对终端110进行DRX参数配置，而后终端发送RRC连接重配置完成消息给基站130(S225)，基站130接收RRC连接重配置完成消息后向CN发送E-RAB建立响应消息(S226)。
同样的，CN也会触发与终端120之间建立语音承载，具体步骤S227至S230同S223至S226一样，不再赘述。
需要说明的是，本实施例对终端110和终端120的语音承载建立的先后顺序不做限制。
此后，终端110和终端120继续进行SIP流程，终端120就响铃(ringing)、接通(信令称为200OK)等状态通过SIP信令通知终端110，终端110进行确认(ACK)后，终端110和终端120之间可以进行语音通话。如图2所示的SIP及语音通话流程。
在以上实施例中，终端110和终端120在默认承载建立的时候就生效了，后续终端110和终端120在语音接通之前收到的下行信令都可能会受到DRX的影响。
下面结合图3所示的DRX周期说明DRX功能对语音呼叫过程的影响。基站配置的DRX参数包括DRX周期(DRX Cycle)。在时域上，时间被划分成连续的DRX周期。DRX周期包括激活期(On Duration)和休眠期(又称为Opportunity for DRX)。在激活期内，终端监听PDCCH，从而可以接收该下行信道的下行数据。在休眠期内，终端不监听PDCCH，不接收该下行信道的下行数据以节省功耗。
请结合图2，在终端110上述步骤S206之后就开始生效DRX功能，终端120的DRX功能在步骤S217之后就开始生效，则终端110或者终端120的DRX功能一直处于工作状态。如果下行信令在休眠期到达基站的分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)缓存，基站发现终端110或者终端120处于休眠期不能调度，要等到激活期才能调度，从而导致语音呼叫接通的时延增大。对于主叫终端，下行信令可以包括SIP信令和RRC信令，例如，S222中的trying信令；再如，以上步骤S224的RRC连接重配置消息。对于被叫终端，下行信令可以包括SIP信令和RRC信令，例如，S220中的invite信令；再如，以上步骤S228的RRC连接重配置消息。
以上仅以终端110和终端120处于空闲态进行语音呼叫为例进行说明，当终端110处于RRC连接态时，可以省略以上RRC连接建立过程及默认承载的建立过程。但终端110因其他业务建立RRC连接及默认承载时也生效了DRX功能，因此，语音呼叫接通过程仍然受到DRX的影响。例如，以上步骤S224的RRC连接重配置消息会受到DRX的影响。同理，终端120如果处于RRC连接态也面临相同的问题。
此外，为减少鬼振铃和应答瞬间的语音掉字，语音通信中还可以预先准备(Precondition)方案，在该Precondition方案会有更多的SIP信令受到影响。Precondition方案是在通话建立之前，给当前的通话预留好资源，以防止鬼振铃和语音断续。鬼振铃指在被叫终端刚开始响铃的瞬间，由于网络资源不足等情况电话被挂断。语音掉字指被叫终端刚开始被接听的时候，出现语音断续、掉字的情况。
请参考图4，其为本申请实施例提供的一种SIP信令流图。如图4所示，主叫终端通过CN向被叫终端发送Invite信令。CN接收主叫终端发送的Invite信令，反馈Trying信令，表示已经收到；被叫终端接收CN发送的Invite信令，反馈Trying信令，表示已经收到。
被叫终端向CN发送183会话(Session)信令，CN将其转发给主叫终端，该信令 用于指示建立会话的进度信息。在非Precondition方案中，此时被叫终端的专用承载，在这里为语音承载建立。主叫终端通过CN反馈临时应答消息，PRACK信令，表示收到183 Session信令，在非Precondition方案中，此时主叫终端建立专用承载。
被叫终端通过CN向主叫终端发送200OK信令，表示183Session信令请求已经处理成功。主叫终端通过CN向被叫终端发送更新(Update)信令，用于与被叫终端协商会话描述协议(Session Description Protocol，SDP)信息。被叫终端通过CN反馈200OK信令，表示Update请求已经处理成功。被叫终端振铃，通过CN向主叫终端发送振铃(Ringing)信令，表明被叫终端振铃。被叫终端通过CN向主叫终端发送200OK信令，表明最初的Invite请求已经处理成功。主叫终端通过CN向被叫终端反馈确认(ACK)信令，用于通知被叫终端，主叫终端已经了解被叫终端处理Invite请求成功。此时，可以开始语音通话。
在非Precondition的方案中，183Session之后的SIP信令(可以包括该183Session信令也可以不包括该183Session信令)在主叫终端和被叫终端语音承载建立之后执行，即图2中步骤中的SIP信令流程包括图4中183Session之后的SIP信令。在Precondition的方案中，这些SIP流程在语音承载建立之前执行，以为通话预留好资源，因而更多的下行SIP信令收到DRX影响。例如对于被叫终端，可能会受影响的消息包括：Invite信令，PRACK信令等，此时，如果协商还包括Update信令，当然也可以不包括该Update信令，还有非SIP信令的建立语音承载的RRC连接重配置消息。对于主叫终端，可能会受影响的消息包括：Trying信令，183Session信令，Ringing信令，200OK信令，PRACK信令等，还有非SIP信令的建立语音承载的RRC连接重配置消息。有鉴于此，本申请实施例提供的DRX的管理方法，。
所述生效是指在建立语音承载之前，终端的DRX功能未开启，在建立语音承载时才开启，例如，在建立默认承载时，基站不生效终端DRX功能，等到语音承载建立时，才发送DRX参数，生效终端的DRX功能。或者，在建立语音承载之前，当终端的DRX功能已经开启，基站去配置终端的DRX功能，以关闭终端的DRX功能，等到语音承载建立时，才发送DRX参数，生效终端的DRX功能。
请参考图5，其为本申请实施例提供的一种DRX的管理方法的流程图：
S510：基站确定终端具有语音业务。
S520：基站为终端建立语音承载，且在为终端建立语音承载时，生效终端的DRX功能。具体，基站可以在确定终端具有语音业务时，向终端发送配置消息，该配置消息用 于配置终端的语音承载，且在该配置消息中携带DRX参数，以生效终端的DRX功能。该配置消息例如为RRC连接重配置消息。终端接收该配置消息，执行以下操作：
S530：终端启动DRX功能，具体根据配置消息中的DRX参数启动DRX功能。
可见，采用本申请实施例的方法，终端在语音承载建立之前，不生效DRX功能；直至语音承载建立时，再生效DRX功能，从而减少语音呼叫接通的时延。
可选的，基站可以在为终端建立默认承载时，不生效终端的DRX功能。尤其适用于于在建立默认承载之前基站就确定终端具有语音业务的场景，此时不影响因非语音业务建立RRC连接和默认承载时，对终端DRX功能的生效，有利于终端的省电。当然，也可以不论在建立默认承载时，是否确认了终端具有语音业务，都不生效终端的DRX功能。此时，可以降低基站的管理复杂度，且DRX仅在专用承载建立之前不生效，对终端的省电影响并不大。
此时，请参考图6，在以上步骤S520之前，即基站为终端建立语音承载之前，以上方法还包括：
S540：基站为终端建立默认承载，且在为终端建立默认承载时，基站不生效终端的DRX功能。具体，基站可以在确定终端具有语音业务时，向终端发送配置消息(为了和步骤S520中的配置消息区别，称步骤S520中的配置消息为第一配置消息，该步骤S540中的配置消息为第二配置消息)，该第二配置消息用于配置终端的默认承载，且在该第二配置消息中不携带DRX参数，以不生效终端的DRX功能。该配置消息例如为RRC连接重配置消息。
需要说明的是，步骤S530和S510之间没有顺序要求，可以先建立默认承载之后，才确定终端具有语音业务，也可以先确定终端具有语音业务，才建立默认承载。
此时，终端在接收基站发送的第一配置消息之前，还接收基站发送的第二配置消息(例如，图2中步骤S206中的配置消息)，该第二配置消息用于配置终端的默认承载，该第二配置消息不包括DRX参数，如此，终端在默认承载建立时，不启动DRX功能。
可选的，请参考图7，如果在建立语音承载之前，基站已经生效了终端的DRX功能时，以上方法还包括：
S550：基站向终端发送用于去生效终端的DRX功能的消息。具体向终端发送配置消息(为了和上面的配置消息区别，称为第三配置消息)，该配置消息用于去配置终端的DRX功能。
此时，终端在接收基站发送的第一配置消息之前，还执行以下步骤：
S560：终端接收基站发送的第二配置消息(图2中步骤S206中的配置消息)，该第二配置消息用于配置终端的默认承载，该第二配置消息包括DRX参数；
S570：终端根据第二配置消息中的DRX参数，启动DRX功能；
S550：终端接收第三配置消息，该第三配置消息用于去配置终端的DRX功能；
S580：终端根据该第三配置消息去配置DRX功能。
如此，终端在虽然在默认承载建立时开启了DRX功能，但是在基站识别出该终端具有语音业务时，关闭了该DRX功能，因此降低了DRX功能对寻呼接通的影响。
可见，即使在语音承载建立之前已经生效终端的DRX功能的场景下，例如终端因为非语音业务发起RRC连接且默认承载建立时，已经生效了DRX功能，基站可以在确定终端有语音业务时去生效DRX功能，进而采用以上方法，减少语音呼叫接通的时延。
在以上步骤S520中，基站生效终端的DRX功能可以在RRC连接重配置过程，在向终端发送的RRC连接重配置消息中携带DRX参数来实现。由于在该RRC连接重配置消息发送时，终端的DRX功能并未生效，因此该RRC连接重配置消息的发送和接收并不受DRX的影响，保证了语音承载的低时延建立，减少了语音呼叫接通的时延。
类似的，在以上步骤S540中，基站为终端建立默认承载时，不生效终端的DRX功能，可以通过在在RRC连接重配置过程，在向终端发送的RRC连接重配置消息中不携带DRX参数来实现。
在以上步骤S550中，基站向终端发送用于去生效终端的DRX功能的消息，可以通过在RRC连接重配置过程，在向终端发送的RRC连接重配置消息中携带释放DRX参数的信元来实现。
需要说明的是，以上DRX参数或释放DRX参数的信元承载于RRC连接重配置消息中，然而本申请不以此为限，也可以将其承载在其他消息中，即此处对DRX参数的消息载体不做限制。
在以上步骤S510中，基站可以利用多种方法确定终端具有语音业务。
在一种方法中，请结合参考图2，基站可以在接收终端发送的RRC连接请求消息时，根据RRC连接请求消息中携带的原因值，来确定终端是否具有语音业务。此时，以上步骤S510可以包括以下步骤：
基站接收终端发送的RRC连接请求消息，其中该RRC连接请求消息中包括原因值，该原因值用于指示发起RRC连接请求的原因。
S520：基站根据原因值确定终端具有语音业务。
例如，如图2所示，当空闲态的主叫终端110发起RRC连接建立请求时，在RRC连接建立请求中携带的原因值为语音呼叫移动发起方，如mo-VoiceCall，其中mo为mobile original的缩写。则基站根据该原因值可以确定终端为主叫终端，即确定终端具有语音业务。
再如，当空闲态的被叫终端120发起RRC连接建立请求时，在RRC连接建立请求中携带的原因值为语音呼叫移动被叫方，如mt-VoiceCall，其中mt为mobile terminated的缩写。则基站根据该原因值确定该终端为被叫终端，即确定终端具有语音业务。需要说明的是，此处原因值只是示例，对原因值的具体形式不做限制。
可见，采用图5所示的方法，请结合图2，基站可以在终端发起RRC连接时，即根据原因值确定终端是否具有语音业务，进而在默认承载建立时就可以不生效终端的DRX功能，而在建立语音承载时才开始生效终端的DRX功能。如此减少了终端的DRX功能对语音呼叫的影响，减少了语音呼叫接通的时延。
在另一种方法中，可以在寻呼被叫终端时，在寻呼消息中增加指示信息，用于指示所述终端具有语音业务，或者用于指示所述终端为被叫终端。该指示信息可以为专门设置的信元；也可以为寻呼优先级，基站和CN事先已经约定好了该寻呼优先级用于表示该终端具有语音业务，或者表示该终端为语音终端。
当通过寻呼优先级来识别终端具有语音业务时，可以约定好某个寻呼优先级(paging priority)用于表示终端具有语音业务或者该终端为被叫终端。具体可以通过配置来约定，即在基站和CN的配置一致的寻呼优先级用来表示终端具有语音业务，或者终端为被叫终端。此时，请结合参考图2，当CN寻呼被叫终端120时，CN在寻呼消息中携带该寻呼优先级，基站140接收到该寻呼消息，发现其中携带的寻呼优先级和配置在基站的用于表示终端具有语音业务(或终端为被叫终端)的寻呼优先级一致，则认为该终端具有语音业务或为被叫终端。具体的，基站可以在解析出寻呼消息中包括该寻呼优先级时，保存该终端的标识，例如SAE临时移动用户标识(SAE-temporary mobile subscriber identity，S-TMSI)，其中，SAE为系统架构演进(System Architecture Evolution)的缩写。并在终端发起RRC连接请求时，在RRC连接请求消息中获取终端的标识，和本地保存的终端的标识一致的终端则认为是被叫终端或具有语音业务的终端，如此可以识别出该终端具有语音业务，在对该终端建立默认承载时，不生效DRX功能。在语音承载建立时，再生效DRX功能。
当通过专门设置的信元识别终端具有语音业务时，该信元可以为语音终端指示信 元，例如LTE中，可以为VOLTEUSER INDICATION。此处，仅为举例对该信元的名称和形式不做限制。请结合参考图2，当CN寻呼被叫终端120时，CN在寻呼消息中携带该语音终端指示信元，基站140接收到该寻呼消息，发现其中携带的语音终端指示信元，则认为该终端具有语音业务或为被叫终端。具体的，基站可以在解析出寻呼消息中包括语音终端指示信元时，保存该终端的标识，例如S-TMSI。并在终端发起RRC连接请求时，在RRC连接请求消息中获取终端的标识，和本地保存的终端的标识一致的终端则认为是被叫终端或具有语音业务的终端，如此可以识别出该终端具有语音业务，在对该终端建立默认承载时，不生效DRX功能。在语音承载建立时，再生效DRX功能。
此时，基站确定终端具有语音业务的方法，包括：基站解析终端的寻呼消息，在寻呼消息包括指示信息时，保存该终端的标识；基站接收终端发送的RRC连接请求消息，RRC连接请求消息中包括终端的标识；当基站保存的标识和RRC连接请求消息中的标识一致时，基站确定终端具有语音业务或确定终端为被叫终端。
在又一种方法中，可以在初始上下文建立过程中识别终端是否具有语音业务。例如在初始上下文建立请求消息中增加指示信元，该指示信元用于指示所述终端具有语音业务。在主叫侧的初始上下文建立过程中，该指示信元还可以用于指示终端为主叫终端，在被叫侧的初始上下文建立过程中，该指示信元还可以用于指示终端为被叫终端。请结合参考图2，在主叫侧的步骤S205中的初始上下文建立请求消息中可以增加指示信元。在被叫侧的步骤S216中的初始上下文建立请求消息中可以增加指示信元。如此，基站在接收到初始上下文建立请求消息时，根据其中的指示信元确定终端具有语音业务。
可见，在以上确定终端具有语音业务的方法中，可以在默认承载建立之前或建立时就确定出终端具有语音业务，因此可以在默认承载建立时，不生效终端的DRX功能，而在语音承载建立时生效终端的DRX功能。
请在结合图2，基站130确定终端110具有语音业务时，不在步骤S206配置终端110的DRX参数，而是在步骤S224配置终端110的DRX参数。基站140确定终端120具有语音业务时，不在步骤S217配置终端120的DRX参数，而在步骤S228配置终端120的DRX参数。通过延迟生效终端的DRX功能，可以降低终端的DRX功能对语音呼叫接通的影响，减少了语音呼叫接通的时延。
综上，通过以上任一种确定终端具有语音业务的方法，在确定终端具有语音业务后，基站延迟生效终端的DRX功能，从而减少了语音寻呼接通的时延。
在又一种方法中，基站还可以通过解析默认承载上的消息的方式来识别终端是否具 有语音业务。例如基站在默认承载建立之后，解析默认承载上的数据包，解析发现其上承载的是SIP信令，则确定终端具有语音业务。该种方法可以用于任何语音呼叫场景，对于终端处于RRC连接态时发起语音业务或者作为语音被叫的场景，具有更好的效果。例如终端因为非语音业务建立RRC连接和默认承载，此时终端的DRX已经被生效，当判断出终端具有语音业务时，基站可以采用图7所示的方法去生效终端的DRX功能，例如发送RRC连接重配置消息，以释放DRX配置。当语音承载建立时，再生效DRX功能，下发DRX参数。
需要说明的是，以上实施例中的默认承载在终端具有语音业务时包括QCI为5的承载，语音承载为专用承载，包括QCI为1的承载。
且在语音承载建立时生效的DRX功能所使用的DRX参数符合语音通信的特点，因此对后续语音通信的影响不大。
以上任一实施例中基站所执行的方法实现，可以通过图8所示DRX的管理装置800实现，该装置包括确定单元810和建立单元820，其中：
确定单元810，用于确定终端具有语音业务。
建立单元820，用于为终端建立语音承载，且在为终端建立语音承载时，生效终端的DRX功能。
可见，通过采用以上装置800，可以延迟生效终端的DRX功能，从而减少了语音呼叫接通的时延。
可选的，建立单元820还用于在为终端建立语音承载之前为终端建立默认承载，且在为终端建立默认承载时，不生效终端的DRX功能。
可选的，当在建立语音承载之前，建立单元820已经生效了终端的DRX功能时，所述装置还包括去生效单元830，用于向终端发送用于去生效终端的DRX功能的消息。
可见，即使在语音承载建立之前已经生效终端的DRX功能的场景下，通过采用以上装置800，也能减少语音呼叫接通的时延。
在以上装置800中，建立单元820可以通过向终端发送配置消息的方式生效终端的DRX功能。其中，配置消息用于配置终端的语音承载，且其中包括DRX参数。
需要说明的是，配置消息可以为RRC连接重配置消息，也可以为其他消息中，此处对配置消息的形式不做限制。
在以上所述的装置800中，确定单元810确定终端是否具有语音业务的方式同以上方法实施例的描述，在此不再赘述。
应理解以上装置的各个单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且这些单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元通过软件通过处理元件调用的形式实现，部分单元通过硬件的形式实现。例如，确定单元810可以为单独设立的处理元件，也可以集成在基站的某一个芯片中实现，此外，也可以以程序代码的形式存储于基站的存储器中，由基站某一个处理元件调用并执行确定单元的功能。其它单元的实现与之类似。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件可以是一种集成电路，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者通过处理元件调用软件形式的指令实现。
例如，以上这些单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)等。再如，当以上某个单元通过处理元件调度程序代码的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)或其它可以调用程序代码的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
请参见图9，其为本申请实施例提供的一种基站的结构示意图。如图9所示，该基站包括：处理器910、存储器920、收发装置930。收发装置930可以与天线连接。该存储器920用于存储实现以上方法实施例或者装置实施例各个单元的程序代码，处理器910调用该程序代码，执行以上方法实施中基站的操作。
以上任一实施例中终端所执行的方法实现，可以通过图10所示DRX的管理装置1000实现，该装置包括收发单元1010和处理单元1020，其中：收发单元1010用于接收基站发送的第一配置消息，该第一配置消息用于配置终端的语音承载，且第一配置消息包括DRX参数；处理单元1020用于根据该DRX参数，启动DRX功能。
可选的，收发单元1010在接收基站发送的第一配置消息之前，还用于接收基站发送的第二配置消息，该第二配置消息用于配置终端的默认承载，该第二配置消息不包括DRX参数，如此，终端在默认承载建立时，不启动DRX功能。
可选的，收发单元1010在接收基站发送的第一配置消息之前，还用于接收基站发送的第二配置消息，该第二配置消息用于配置终端的默认承载，该第二配置消息包括DRX 参数；处理单元1020根据第二配置消息中的DRX参数，启动DRX功能；收发单元1010还用于接收第三配置消息，该第三配置消息用于去配置终端的DRX功能；处理单元1020用于根据该第三配置消息去配置DRX功能。
如此，终端在虽然在默认承载建立时开启了DRX功能，但是在基站识别出该终端具有语音业务时，关闭了该DRX功能，因此降低了DRX功能对寻呼接通的影响。
可选的，收发单元1010还用于在空闲态向基站发送RRC连接请求时，携带原因值，该原因值用于指示发起RRC连接请求的原因，以便基站根据该原因值确定终端具有语音业务。进一步的，当终端为主叫终端时，原因值为语音呼叫移动发起方，如mo-VoiceCall；当终端为被叫终端时，原因值为语音呼叫移动接收方，如mt-VoiceCall。
以上收发单元可以为终端的收发装置，处理单元可以为终端的处理器。
请参见图11，其为本申请实施例提供的一种终端的结构示意图。如图11所示，该基站包括：处理器1110、存储器1120、收发装置1130。收发装置1130可以与天线连接。该存储器1120用于存储实现以上方法实施例或者装置实施例各个单元的程序代码，处理器1110调用该程序代码，执行以上方法实施中终端的操作。
通过以上的实施例的描述，所属领域的技术人员可以清楚地了解到本申请可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (22)

  1. 一种非连续接收DRX的管理方法，其特征在于，所述方法包括：
    基站确定终端具有语音业务；
    所述基站为所述终端建立语音承载，且在为所述终端建立语音承载时，生效所述终端的DRX功能。
  2. 根据权利要求1所述的方法，其特征在于，所述基站为所述终端建立语音承载之前，还包括：
    所述基站为所述终端建立默认承载，且在为所述终端建立默认承载时，所述基站不生效所述终端的DRX功能。
  3. 根据权利要求1所述的方法，其特征在于，当在所述基站为所述终端建立语音承载之前，所述基站已经生效了所述终端的DRX功能时，所述方法还包括：
    所述基站向所述终端发送用于去生效所述终端的DRX功能的消息。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述基站确定终端具有语音业务，包括：
    所述基站接收所述终端发送的无线资源控制RRC连接请求消息，所述RRC连接请求消息包括原因值，该原因值用于指示发起RRC连接请求的原因；
    所述基站根据所述原因值确定所述终端具有语音业务。
  5. 根据权利要求4所述的方法，其特征在于，所述基站根据所述原因值确定所述终端具有语音业务，包括：
    当所述原因值为语音呼叫移动发起方时，所述基站确定所述终端具有语音业务；
    当所述原因值为语音呼叫移动接收方时，所述基站确定所述终端具有语音业务。
  6. 根据权利要求1至3任一项所述的方法，其特征在于，所述基站确定终端具有语音业务，包括：
    所述基站从核心网接收所述终端的寻呼消息，所述寻呼消息包括指示信息，所述指示信息用于指示所述终端具有语音业务；
    所述基站根据所述指示信息确定所述终端具有语音业务。
  7. 根据权利要求6所述的方法，其特征在于，所述指示信息为寻呼优先级，所述根据所述指示信息确定所述终端具有语音业务，包括：
    当所述基站确定所述寻呼优先级为第一寻呼优先级时，确定所述终端具有语音业 务，其中所述第一寻呼优先级为设定的用于指示所述终端具有语音业务的寻呼优先级。
  8. 根据权利要求6所述的方法，其特征在于，所述指示信息为语音终端指示信元，所述基站根据所述指示信息确定所述终端具有语音业务，包括：
    当所述基站确定所述寻呼消息包括所述语音终端指示信元时，所述基站确定所述终端具有语音业务。
  9. 根据权利要求1至3任一项所述的方法，其特征在于，所述基站确定终端具有语音业务，包括：
    所述基站接收初始上下文建立请求消息，所述初始上下文建立请求消息中包括指示信元，所述指示信元用于指示所述终端具有语音业务；
    所述基站根据所述指示信元确定所述终端具有语音业务。
  10. 根据权利要求1至3任一项所述的方法，其特征在于，所述基站确定终端具有语音业务，包括：
    所述基站确定默认承载上承载的信息为会话发起协议SIP信令时，确定所述终端具有语音业务。
  11. 一种非连续接收DRX的管理装置，其特征在于，所述装置包括：
    确定单元，用于确定终端具有语音业务；
    建立单元，用于为所述终端建立语音承载，且在为所述终端建立语音承载时，生效所述终端的DRX功能。
  12. 根据权利要求11所述的装置，其特征在于，所述建立单元还用于在为所述终端建立语音承载之前：
    为所述终端建立默认承载，且在为所述终端建立默认承载时，不生效所述终端的DRX功能。
  13. 根据权利要求11所述的装置，其特征在于，当在所述建立单元为所述终端建立语音承载之前，已经生效了所述终端的DRX功能时，所述装置还包括：
    去生效单元，用于向所述终端发送用于去生效所述终端的DRX功能的消息。
  14. 根据权利要求11至13任一项所述的装置，其特征在于，所述确定单元用于：
    接收所述终端发送的无线资源控制RRC连接请求消息，所述RRC连接请求消息包括原因值，该原因值用于指示发起RRC连接请求的原因；
    根据所述原因值确定所述终端具有语音业务。
  15. 根据权利要求14所述的装置，其特征在于，所述确定单元用于：
    当所述原因值为语音呼叫移动发起方时，确定所述终端具有语音业务；
    当所述原因值为语音呼叫移动接收方时，确定所述终端具有语音业务。
  16. 根据权利要求11至13任一项所述的装置，其特征在于，所述确定单元用于：
    从核心网接收所述终端的寻呼消息，所述寻呼消息包括指示信息，所述指示信息用于指示所述终端具有语音业务；
    根据所述指示信息确定所述终端具有语音业务。
  17. 根据权利要求16所述的装置，其特征在于，所述指示信息为寻呼优先级，所述确定单元用于：
    当确定所述寻呼优先级为第一寻呼优先级时，确定所述终端具有语音业务，其中所述第一寻呼优先级为设定的用于指示所述终端具有语音业务的寻呼优先级。
  18. 根据权利要求16所述的装置，其特征在于，所述指示信息为语音业务指示信元，所述确定单元用于：
    当确定所述寻呼消息包括所述语音终端指示信元时，确定所述终端具有语音业务。
  19. 根据权利要求11至13任一项所述的装置，其特征在于，所述确定单元用于：
    接收初始上下文建立请求消息，所述初始上下文建立请求消息中包括指示信元，所述指示信元用于指示所述终端具有语音业务；
    根据所述指示信元确定所述终端具有语音业务。
  20. 根据权利要求11至13任一项所述的装置，其特征在于，所述确定单元用于：
    确定默认承载上承载的信息为会话发起协议SIP信令时，确定所述终端具有语音业务。
  21. 一种非连续接收DRX的管理系统，其特征在于，所述系统包括权利要求11至20任一项所述的DRX的管理装置。
  22. 一种计算机程序，其中，该程序在被处理器执行时用于执行以上权利要求1至10任一项所述的方法。
PCT/CN2017/071193 2017-01-14 2017-01-14 非连续接收的管理方法和装置 WO2018129728A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN201780083268.8A CN110169146B (zh) 2017-01-14 2017-01-14 非连续接收的管理方法和装置
KR1020197023994A KR102221413B1 (ko) 2017-01-14 2017-01-14 비연속 수신 관리 방법 및 장치
JP2019538125A JP6868110B2 (ja) 2017-01-14 2017-01-14 不連続受信管理方法および装置
EP17891224.2A EP3562218B1 (en) 2017-01-14 2017-01-14 Management method and device for discontinuous reception
PCT/CN2017/071193 WO2018129728A1 (zh) 2017-01-14 2017-01-14 非连续接收的管理方法和装置
US16/510,540 US11259357B2 (en) 2017-01-14 2019-07-12 Management of discontinuous reception (DRX) for a terminal having a voice service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/071193 WO2018129728A1 (zh) 2017-01-14 2017-01-14 非连续接收的管理方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/510,540 Continuation US11259357B2 (en) 2017-01-14 2019-07-12 Management of discontinuous reception (DRX) for a terminal having a voice service

Publications (1)

Publication Number Publication Date
WO2018129728A1 true WO2018129728A1 (zh) 2018-07-19

Family

ID=62839610

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/071193 WO2018129728A1 (zh) 2017-01-14 2017-01-14 非连续接收的管理方法和装置

Country Status (6)

Country Link
US (1) US11259357B2 (zh)
EP (1) EP3562218B1 (zh)
JP (1) JP6868110B2 (zh)
KR (1) KR102221413B1 (zh)
CN (1) CN110169146B (zh)
WO (1) WO2018129728A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11057904B2 (en) * 2017-12-06 2021-07-06 T-Mobile Usa, Inc. Prioritization of mobile terminating radio resource control connections
KR102304200B1 (ko) * 2020-02-19 2021-09-17 에스케이텔레콤 주식회사 기지국장치 및 단말장치
EP4371371A1 (en) * 2021-08-05 2024-05-22 Google LLC Managing paging for different services

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120046030A1 (en) * 2010-08-20 2012-02-23 Telefonaktiebolaget L M Ericsson (Publ) Method and Node for Reduced Transmission Activity Pattern Configuration
CN103314633A (zh) * 2010-11-15 2013-09-18 捷讯研究有限公司 管理无线通信
CN104039027A (zh) * 2014-06-30 2014-09-10 华为技术有限公司 资源释放的处理方法及装置
CN105813177A (zh) * 2014-12-27 2016-07-27 华为技术有限公司 非连续接收周期管理方法和装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101682004B1 (ko) 2010-03-16 2016-12-05 삼성전자주식회사 무선통신시스템에서 불연속 패킷 수신 운용 장치 및 방법
EP4213537A1 (en) * 2010-09-28 2023-07-19 BlackBerry Limited Method in a core network, mobility management entity and non-transitory storage medium
KR20150018531A (ko) * 2012-05-09 2015-02-23 삼성전자주식회사 이동통신 시스템에서 불연속 수신을 제어하는 방법 및 장치
JP5412566B1 (ja) * 2012-09-26 2014-02-12 株式会社Ｎｔｔドコモ ハンドオーバ元無線基地局、ハンドオーバ先無線基地局、無線通信システムおよび無線通信方法
KR20140041305A (ko) * 2012-09-27 2014-04-04 삼성전자주식회사 사용자 단말에서 데이터 송수신 장치 및 방법
US9179404B2 (en) 2013-03-25 2015-11-03 Qualcomm Incorporated Method and apparatus for UE-only discontinuous-TX smart blanking
JP2016527822A (ja) * 2013-07-29 2016-09-08 エルジー エレクトロニクス インコーポレイティド Ｉｍｓサービスのためのページング方法及び装置
KR20150014834A (ko) * 2013-07-30 2015-02-09 삼성전자주식회사 특정 서비스를 지속적으로 제공하는 방법 및 장치
CN110536485B (zh) * 2013-09-27 2022-12-23 Sk电信有限公司 支持双连接的用户设备
US20150341858A1 (en) * 2014-05-21 2015-11-26 Qualcomm Incorporated Apparatus, methods, and computer program products providing power savings in sps-configured volte with c-drx
US10736153B2 (en) * 2015-09-16 2020-08-04 Lg Electronics Inc. Bearer setting method and device supporting same for transmitting/receiving data in wireless communication system
KR102105053B1 (ko) * 2015-11-17 2020-04-27 엘지전자 주식회사 무선 통신 시스템에서 확장된 아이들 모드 불연속 수신 활성화 지원 방법 및 이를 위한 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120046030A1 (en) * 2010-08-20 2012-02-23 Telefonaktiebolaget L M Ericsson (Publ) Method and Node for Reduced Transmission Activity Pattern Configuration
CN103314633A (zh) * 2010-11-15 2013-09-18 捷讯研究有限公司 管理无线通信
CN104039027A (zh) * 2014-06-30 2014-09-10 华为技术有限公司 资源释放的处理方法及装置
CN105813177A (zh) * 2014-12-27 2016-07-27 华为技术有限公司 非连续接收周期管理方法和装置

Also Published As

Publication number Publication date
EP3562218A1 (en) 2019-10-30
CN110169146B (zh) 2021-02-23
US11259357B2 (en) 2022-02-22
EP3562218B1 (en) 2021-03-10
JP2020504575A (ja) 2020-02-06
KR102221413B1 (ko) 2021-02-26
CN110169146A (zh) 2019-08-23
EP3562218A4 (en) 2019-11-20
KR20190103399A (ko) 2019-09-04
US20190335531A1 (en) 2019-10-31
JP6868110B2 (ja) 2021-05-12

Similar Documents

Publication Publication Date Title
USRE49636E1 (en) Method and apparatus of improving quality of calls in mobile communication system
CA2774368C (en) Method and apparatus for providing peer-to-peer communication with network connection
JP6068648B2 (ja) トランキングサービスを迅速に確立するための方法、関連する装置及びシステム
TWI697247B (zh) 處理無線通訊系統中的連結的裝置及方法
EP3777298A1 (en) Suspending/resuming measurements in rrc inactive state
WO2021031022A1 (zh) 链路切换的方法和通信设备
CN112514528A (zh) 用于5g蜂窝物联网的用户平面优化
US10313941B2 (en) Apparatus, systems and methods for improved mobility between networks
US11259357B2 (en) Management of discontinuous reception (DRX) for a terminal having a voice service
WO2022083484A1 (zh) 数据传输控制方法、装置及存储介质
CN109474987B (zh) 与长期演进网络及新无线网络通信的装置及方法
WO2018112850A1 (zh) 通信方法、终端设备和网络设备
WO2018126365A1 (zh) 信息传输的方法、终端设备和网络设备
WO2022042440A1 (zh) 用户面数据的传输方法和网络节点
WO2021037130A1 (zh) 寻呼方法和设备
TW201844046A (zh) 處理雙連結的裝置及方法
CN112368976A (zh) 用于执行组通信的终端和方法
WO2017177440A1 (zh) 状态指示的传输装置、方法以及通信系统
TWI693855B (zh) 處理系統重新定向程序的裝置及方法
US10735145B2 (en) Enhancement on reception of standalone service accept
US20120014301A1 (en) System and method for triggering dormant state in a mobile station in a umts/lte network
WO2023280014A1 (zh) 单播侧链路通信方法、装置及终端
WO2023169362A1 (zh) 一种寻呼方法及其装置
WO2022067807A1 (zh) 通信方法和通信装置
WO2023066009A1 (zh) 内生业务的传输方法、装置及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17891224

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019538125

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017891224

Country of ref document: EP

Effective date: 20190722

ENP Entry into the national phase

Ref document number: 20197023994

Country of ref document: KR

Kind code of ref document: A