[go: up one dir, main page]

WO2018214708A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication Download PDF

Info

Publication number
WO2018214708A1
WO2018214708A1 PCT/CN2018/085178 CN2018085178W WO2018214708A1 WO 2018214708 A1 WO2018214708 A1 WO 2018214708A1 CN 2018085178 W CN2018085178 W CN 2018085178W WO 2018214708 A1 WO2018214708 A1 WO 2018214708A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
identifier
inactive state
base station
state
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.)
Ceased
Application number
PCT/CN2018/085178
Other languages
English (en)
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2018214708A1 publication Critical patent/WO2018214708A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the embodiments of the present application relate to the field of communications technologies, and in particular, to a communication method and apparatus.
  • the concept of inactive state is introduced in 5G communication systems.
  • the inactive state is a state between a connected state and an idle state. After the terminal transitions from the inactive state to the idle state, there may be a case where the current state of the terminal recorded by the base station is inactive. In this case, the prior art has not proposed a technical solution for how to establish a connection between a terminal and a base station.
  • the present application provides a communication method and apparatus, and in particular, provides a technical solution for establishing a connection between a base station and a terminal, which can be applied to, but not limited to, a state out-of-synchronization scenario.
  • the present application provides a communication method and apparatus.
  • the method may include: determining, by the terminal in an idle state, an identifier of the terminal in an inactive state; the terminal initiating a connection procedure according to the identifier of the terminal in an inactive state.
  • the last state before the terminal is in the idle state is the inactive state
  • the identifier of the terminal in the inactive state determined by the terminal is the identifier of the terminal in the latest state (ie, the inactive state).
  • the connection process may be initiated by the terminal in an inactive state, so that the base station can establish an air interface connection and reuse the established RAN associated with the inactive state identifier.
  • the RAN is an abbreviation of a radio access network.
  • CN is the English abbreviation of core network (CN).
  • the identifier of the terminal in the inactive state may be a resume ID in a long term evolution (LTE) system, or an access stratum (AS) context ID in a new radio (NR) system.
  • LTE long term evolution
  • AS access stratum
  • NR new radio
  • the terminal initiates the connection process according to the identifier of the terminal in the inactive state
  • the method may include: the terminal sends a connection establishment request, where the connection establishment request includes information indicating the identifier of the terminal in an inactive state.
  • This possible design can be thought of as a connection request multiplexing connection setup request. Of course, this application is not limited to this.
  • the terminal initiates a connection process according to the identifier of the terminal in an inactive state, which may include: the terminal sends a connection recovery request, where the connection recovery request includes information indicating the identity of the terminal in an inactive state.
  • This possible design can be thought of as a connection request multiplexing connection recovery request.
  • this application is not limited to this.
  • the connection setup request/connection recovery request includes the identity of the terminal in the idle state and the identity of the terminal in the inactive state.
  • the connection establishment request/connection recovery request includes the identifier and indication information of the terminal.
  • the identifier of the terminal includes an identifier of the terminal in an idle state or an identifier of the terminal in an inactive state or other information that can be used to indicate the identifier of the terminal.
  • the indication information is used to indicate the type of connection establishment request/connection recovery request or the type indicating the identity of the terminal.
  • this application is not limited to this.
  • the processing mode of the base station may be different. For details, refer to the following.
  • the method may further include: when the terminal transitions from the inactive state to the idle state, storing information indicating the identity of the terminal in an inactive state. In this way, the terminal can be supported in the idle state, and the connection process is initiated according to the identifier of the terminal in the inactive state.
  • the information indicating the identifier of the terminal in the inactive state may be an identifier of the terminal in an inactive state, or an index of the identifier of the terminal in an inactive state.
  • the type of the identifier of the terminal is defined in the application, and the type may include an identifier of the terminal in an inactive state and an identifier of the terminal in an idle state.
  • the index of any type of identification of the terminal can be expressed in binary. For example, "1" can be used as an index of the identifier of the terminal in the inactive state, and "0" is used as the index of the identifier of the terminal in the idle state. Of course, this application is not limited to this.
  • the saving of the identifier of the terminal in the inactive state may include: when the terminal does not send a state transition notification to the base station, and saves the identifier of the terminal in an inactive state.
  • the terminal transitions from the inactive state to the idle state, and does not send a state transition notification to the base station, indicating that the state is out of synchronization at this time.
  • This optional design can be considered as an implementation scenario in which the state is out of step, although the application is not limited thereto.
  • the saving of the identifier of the terminal in the inactive state may include: when the terminal fails to send the state transition notification to the base station, the identifier of the terminal in the inactive state is saved.
  • the terminal transitions from the inactive state to the idle state, and fails to successfully send a state transition notification to the base station, indicating that the state is out of synchronization at this time.
  • This optional design can be considered as an implementation scenario in which the state is out of step, although the application is not limited thereto.
  • the method may further include: the terminal receiving the RAN paging message sent by the base station.
  • the possible design may be that the terminal initiates a connection procedure triggered by the RAN paging message sent by the base station.
  • this application is not limited to this.
  • the terminal may also initiate a connection process when there is uplink data to be sent.
  • the method may further include: the terminal saves the discontinuous reception (DRX) configuration information of the terminal in an inactive state; the terminal according to the DRX The configuration information determines the time at which the RAN paging message is received. In this way, the terminal can be supported to receive the RAN paging message in the idle state.
  • DRX discontinuous reception
  • the saving of the identifier of the terminal in the inactive state may include: when the identifier of the terminal in the inactive state is within the valid time, the identifier of the terminal in the inactive state is saved.
  • the identity of the terminal in the inactive state is deleted. In this way, the storage resources of the terminal can be saved.
  • the method may further include: deleting the terminal inactive when the terminal moves out of the RN-based notification area (RNA) related to the identifier of the terminal in the inactive state. State of the logo.
  • RNA is the RNA in which the terminal is switched to the idle state. In this way, the storage resources of the terminal can be saved.
  • the method may further include: the terminal saves the cell information corresponding to the RNA associated with the identifier of the terminal in the inactive state.
  • the cell information corresponding to the RNA is used to determine whether the terminal removes the RNA. In this way, the terminal can be supported to determine whether to remove the RNA in the idle state.
  • the present application also provides a communication device that can implement the communication method of the first aspect.
  • the device may be a terminal, which may implement the above method by software, hardware, or by executing corresponding software by hardware.
  • the apparatus can include a processor and a memory.
  • the processor is configured to support the apparatus to perform the corresponding functions of the first aspect method described above.
  • the memory is for coupling to a processor that holds the programs (instructions) and data necessary for the device.
  • the apparatus can also include a communication interface for supporting communication between the apparatus and other network elements.
  • the communication interface can be a transceiver.
  • the apparatus can include a processing unit and a transceiver unit.
  • the processing unit may be configured to determine, when the terminal is in an idle state, an identifier of the terminal in an inactive state.
  • the sending unit may be configured to initiate a connection process according to the identifier of the terminal in an inactive state.
  • the transceiver unit may be specifically configured to send a connection establishment request, where the connection establishment request includes information indicating the identity of the terminal in an inactive state.
  • the transceiver unit may be specifically configured to send a connection recovery request, where the connection recovery request includes information indicating the identity of the terminal in an inactive state.
  • the terminal may further include: a storage unit, configured to save the identifier of the terminal in an inactive state when the terminal transitions from an inactive state to an idle state.
  • the storage unit may be specifically configured to: when the terminal does not send a state transition notification to the base station, save the identifier of the terminal in an inactive state.
  • the storage unit may be specifically configured to: when the terminal transitions from an inactive state to an idle state, and the terminal fails to successfully send a state transition notification to the base station, and saves the identifier of the terminal in an inactive state.
  • the transceiver unit can also be configured to receive a RAN paging message sent by the base station.
  • the storage unit is further configured to save the DRX configuration information of the terminal in an inactive state.
  • the processing unit may be further configured to: determine, according to the DRX configuration information, a reception time of the RAN paging message.
  • the storage unit may be specifically configured to save the identifier of the terminal in an inactive state when the identifier of the terminal in the inactive state is within a valid time.
  • the processing unit may be further configured to delete the identifier of the terminal in an inactive state when the terminal ends in the inactive state of the identifier of the inactive state.
  • the processing unit may be further configured to: when the terminal moves out of the identification-related RNA of the terminal in an inactive state, delete the identifier of the terminal in an inactive state.
  • the storage unit may be further configured to: save cell information corresponding to the RNA associated with the identifier of the terminal in the inactive state; wherein the cell information corresponding to the RNA is used to determine whether the terminal removes the RNA.
  • the present application provides another communication method and apparatus.
  • the method may include the base station receiving a connection establishment request, the connection establishment request including an identifier of the terminal in an inactive state. Then, the base station establishes an air interface connection between the base station and the terminal according to the identifier of the terminal in an inactive state, and reuses the connection between the base station and the core network device.
  • the base station may establish an air interface connection according to the identifier of the terminal in the inactive state in the connection establishment request, and reuse the established RAN-CN related to the identifier of the inactive state. connection.
  • the method may further include: the base station sending a RAN paging message to the terminal, where the RAN paging message is used to indicate that the terminal sends a connection establishment request.
  • the present application also provides a communication device, which can implement the communication method described in the second aspect.
  • the apparatus may be a base station, which may implement the above method by software, hardware, or by executing corresponding software by hardware.
  • the apparatus can include a processor and a memory.
  • the processor is configured to support the apparatus to perform the corresponding functions of the second aspect method described above.
  • the memory is for coupling to a processor that holds the programs (instructions) and data necessary for the device.
  • the apparatus can also include a communication interface for supporting communication between the apparatus and other network elements.
  • the communication interface can be a transceiver.
  • the apparatus can include a processing unit and a transceiver unit.
  • the transceiver unit is configured to receive a connection establishment request, where the connection establishment request includes an identifier of the terminal in an inactive state.
  • the processing unit is configured to establish an air interface connection between the base station and the terminal according to the identifier of the terminal in an inactive state, and multiplex the connection between the base station and the core network device.
  • the transceiver unit may be further configured to send a RAN paging message to the terminal, where the RAN paging message is used to indicate that the terminal sends a connection establishment request.
  • the application also provides a computer storage medium having stored thereon a computer program (instructions) that, when executed on a computer, cause the computer to perform the method of any of the above aspects.
  • the application also provides a computer program product, when run on a computer, causing the computer to perform the method of any of the above aspects.
  • FIG. 1 is a schematic diagram of a system architecture applicable to a technical solution provided by an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a radio access network to which the technical solution provided by the embodiment of the present application is applied;
  • FIG. 3 is a schematic diagram of a connection establishment process in an LTE system according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a connection reactivation process in an NR system according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of interaction of a communication method according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of interaction of another communication method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • the technical solution provided by the present application can be applied to various communication systems in which an inactive state of a terminal is introduced, for example, an inactive state of a terminal, a 5G communication system, a future evolution system, or multiple communications is introduced on the basis of an existing communication system.
  • Converged systems and more. Can include a variety of application scenarios, such as machine to machine (M2M), D2M, macro communication, enhanced mobile broadband (eMBB), ultra high reliability and ultra low latency communication (ultra Reliable & low latency communication (uRLLC) and massive machine type communication (mMTC) scenarios.
  • M2M machine to machine
  • D2M macro communication
  • eMBB enhanced mobile broadband
  • uRLLC ultra high reliability and ultra low latency communication
  • mMTC massive machine type communication
  • These scenarios may include, but are not limited to, a communication scenario between the terminal and the terminal, a communication scenario between the base station and the base station, a communication scenario between the base station and the terminal, and the like.
  • the technical solution provided by the embodiment of the present application can also be applied to a scenario between a terminal and a terminal in a 5G communication system, or a communication between a base station and a base station.
  • FIG. 1 shows a schematic diagram of a communication system, which may include a core network, a radio access network, and a terminal.
  • a device in a radio access network may include one or more base stations.
  • the devices in the core network may include one or more mobility management entities (MMEs) (only one shown), one or more service gateways (serving gateways) connected to the MME. SGW) or PDN gateway (PGW), where PDN is the abbreviation of packet data network.
  • MME mobility management entities
  • SGW service gateways
  • PGW PDN gateway
  • the MME is used to manage the bearer establishment and configuration between the base station and the SGW, and triggers paging of the idle terminal when the downlink data reaches the core network device (such as the SGW).
  • the SGW/PGW is used for routing and forwarding of data, and for performing quality of service (QoS) control of the user plane.
  • QoS quality of service
  • devices in the core network may include access and mobility management function (AMF) entities, and user plane function (UPF) entities.
  • AMF access and mobility management function
  • UPF user plane function
  • the AMF entity is used to manage the bearer establishment and configuration between the base station and the UPF entity, and triggers paging of the idle terminal when the downlink data reaches the core network device (such as the UPF entity).
  • the UPF entity is used for routing and forwarding of data, and for performing QoS control of the user plane.
  • FIG. 2 shows a schematic diagram of a radio access network, which may include at least one RNA (only one RNA is shown).
  • An inactive terminal sends a location update request when moving from one RNA to another.
  • Each RNA may include one or more base stations/cells.
  • the base station in the RNA may include a serving base station, an anchor base station, and other base stations from a different perspective on the role of the terminal.
  • a serving base station refers to a base station or terminal to which a terminal in an inactive state is reselected to move a newly accessed base station within the RNA. Any base station can serve as a serving base station for one or more terminals, and the serving base station of the same terminal can be changed.
  • the serving base station of the terminal can be understood as a base station newly accessed by the terminal (ie, a new base station or a target base station).
  • An anchor base station is a base station that configures a terminal to switch from a connected state to an inactive state, or a base station that stores context information of the terminal.
  • the anchor base station of the terminal can be understood as the base station (ie, the old base station or the source base station) that the terminal accessed the most recently before the handover to the new base station.
  • Other base stations refer to base stations other than the serving base station and the anchor base station.
  • the terminal is within the coverage of base station 1 and transitions from the connected state to the inactive state.
  • the terminal moves into the coverage of the base station 2. Then, it can be considered that when the terminal is in the coverage of the base station 2, the base station 1 is the anchor base station of the terminal, and the base station 2 is the serving base station of the terminal.
  • the base station other than the anchor base station and the serving base station of the terminal in the RNA is the other base station for the terminal.
  • a base station may be a device capable of communicating with the terminal.
  • the base station can be a relay station or an access point or the like.
  • the base station may be a base transceiver station (BTS) in a global system for mobile communication (GSM) or a code division multiple access (CDMA) network, or may be a broadband code division.
  • the NB (NodeB) in the wideband code division multiple access (WCDMA) may also be an eNB or an eNodeB (evolutional NodeB) in the LTE system.
  • the base station may also be a wireless controller in a cloud radio access network (CRAN) scenario.
  • the base station may also be a network device in a 5G network or a network device in a future evolved network; or may be a wearable device or an in-vehicle device.
  • the terminal may be a user equipment (UE), an access terminal, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a UE terminal, a wireless communication device, a UE proxy, or a UE device.
  • UE user equipment
  • the access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and A wireless communication capable handheld device, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a future 5G network, or a terminal in a future evolved PLMN network, or the like.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • a wireless communication capable handheld device a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a future 5G network, or a terminal in a future evolved PLMN network, or the like.
  • An air interface connection refers to a connection between a terminal and a RAN device (such as a base station).
  • the air interface connection includes a user plane bearer between the terminal and the base station, for example, a data radio bearer (DRB) in the LTE system; and a control plane bearer between the terminal and the base station, for example, a signaling radio bearer in the LTE system ( Signal radio beare, SRB).
  • DRB data radio bearer
  • SRB Signal radio beare
  • RAN-CN connection refers to the connection between a RAN device (such as a base station) and a CN device.
  • the RAN-CN connection includes a user plane bearer between the base station and the CN device, such as an S1 user plane bearer in an LTE system; and a control plane bearer between the base station and the CN device.
  • the CN device may be an SGW/PGW.
  • a CN device may be a UPF entity.
  • the idle state, the inactive state, and the connected state are all used to describe the state of the terminal.
  • the control plane bearer of the air interface needs to be established first, then the user plane bearer between the RAN-CN is established, and the user plane of the air interface is configured while establishing the user plane bearer between the RAN-CN. Hosted.
  • the user plane bearer of the air interface has been suspended (suspend), and the user plane bearer and control plane bearer between the RAN-CN are still maintained.
  • the terminal initiates a call or a service request, the user plane bearer of the air interface needs to be activated, and the user plane bearer and control plane bearer between the existing RAN-CNs are reused.
  • the control plane bearer of the air interface has been established, and the default user plane bearer (including the user plane bearer of the air interface and the user plane bearer between the RAN-CN) has been established. If the default user plane bearer cannot meet the QoS requirements of the service, a dedicated user plane bearer (including the user plane bearer of the air interface and the user plane bearer between the RAN-CN) is established.
  • State synchronization means that the actual current state of the terminal is the same as the current state of the terminal recorded by the base station.
  • the actual current state of the terminal is an inactive state
  • the current state of the terminal recorded by the base station is also an inactive state.
  • the state out of synchronization means that the actual current state of the terminal is different from the current state of the terminal recorded by the base station.
  • the state out-of-synchronization mainly means that the current state of the terminal is an idle state, and is converted from an inactive state to an idle state, and the current state of the terminal recorded by the base station is still in an inactive state.
  • the identifier of the terminal in the idle state refers to the identifier assigned by the device in the CN to the terminal when the terminal is in the idle state.
  • the identifier of the terminal in the idle state may be referred to as the terminal ID of the CN allocation, or the identifier of the terminal maintained by the CN.
  • the identifier of the terminal in the idle state is, for example but not limited to, a serving temporary mobile subscriber identity (S-TMSI), or an international mobile subscriber identification number (IMSI).
  • the identifier of the terminal in the inactive state refers to the identifier assigned by the device in the RNA in which the terminal is located in the inactive state.
  • the identifier of the inactive state of the terminal may be referred to as the terminal ID assigned by the RAN or the identifier of the terminal maintained by the RAN.
  • the identifier of the terminal in the inactive state is, for example but not limited to, the resume ID in the LTE system or the AS context ID in the NR system. Of course, this application is not limited to this.
  • the terminal can move from one RNA to another, and when the terminal is in different RNAs, the identification of the inactive state of the terminal is different.
  • the type of the identifier of the terminal is defined, and the type may include: an identifier of the terminal in an inactive state, an identifier of the terminal in an idle state, and the like.
  • RAN paging ie RAN paging message or RAN triggered paging message, which may also be referred to as RAN-initiated paging or RAN-based notification.
  • CN paging which is a CN paging message or a CN triggered paging message, which may also be referred to as CN-initiated paging.
  • the RAN paging and the CN paging may be, for example but not limited to, a paging message sent in the case where the downlink data needs to be transmitted or the system message is changed on the network side, and is used to find the terminal in a certain area.
  • the triggering entities of RAN paging and CN paging are different.
  • the RAN paging is triggered by the base station.
  • CN paging is triggered by the MME; in the NR system, CN paging is triggered by the AMF entity.
  • the range of regions in which RAN paging and CN paging act is also different.
  • Figure 3 shows a schematic diagram of the connection establishment process in an LTE system. Specifically, a schematic diagram of a process in which a terminal transitions from an idle state to a connected state in an LTE system is given. The process includes:
  • the terminal sends a random access channel (RACH) preamble to the serving base station.
  • the serving base station receives the RACH preamble sent by the terminal, and after receiving the RACH preamble, allocates an uplink resource to the terminal.
  • the uplink resource may include an uplink resource used by the terminal to send uplink data and/or uplink signaling, such as but not limited to an RRC connection setup request.
  • the terminal may execute S102 if there is a demand to send a service request.
  • the serving base station sends a random access response to the terminal, where the random access response includes information indicating the uplink resource.
  • the terminal receives a random access response sent by the serving base station.
  • S102-S104 can be regarded as a random access process, and other steps can be included in the process, which is not detailed in this application.
  • the terminal sends an RRC connection establishment request to the serving base station.
  • the RRC connection establishment request includes an identifier of the terminal in an idle state, and the like.
  • the serving base station receives the RRC connection setup request sent by the terminal, and after receiving the RRC connection setup request, generates SRB1 configuration information of the terminal, and then performs S108.
  • a plurality of SRBs can be established between the base station and the terminal, wherein the base station and the terminal use SRB1 to perform integrity protection and encryption protection on the transmitted RRC signaling.
  • the serving base station sends an RRC connection setup response to the terminal, where the RRC connection setup response includes SRB1 configuration information of the terminal.
  • the terminal receives the connection setup response sent by the serving base station, and configures SRB1 according to the SRB1 configuration information, and then performs S110.
  • the foregoing S106-S108 may be considered as a process of establishing an air interface SRB1 between the terminal and the serving base station, and the process may further include other steps, which are not described in detail in this application. At this point, the terminal can be considered to have entered the connected state.
  • the terminal sends an RRC connection setup complete message to the serving base station, where the RRC connection setup complete message includes a service request.
  • the RRC Connection Setup Complete message is used to notify the serving base station that the terminal has configured SRB1 on the one hand, and the serving base station to establish context information that satisfies the service request.
  • the serving base station receives the RRC connection setup complete message sent by the terminal, and then performs S112.
  • S112 The serving base station sends a context establishment request to the MME, where the context establishment request includes a service request.
  • the MME receives the context establishment request sent by the serving base station, and establishes context information that satisfies the service request included in the context establishment request, and then performs S114.
  • the MME sends a context setup complete message to the serving base station to notify the serving base station that the MME has established context information that satisfies the service request.
  • the serving base station receives a context establishment complete message sent by the MME.
  • S110-S114 may be considered as a process of establishing context information of the terminal on the network side, and the process may further include other steps, which are not described in detail in this application.
  • the serving base station generates configuration information of the DRB and other SRBs, and then sends an RRC connection reconfiguration message including configuration information of the DRB and other SRBs to the terminal.
  • the terminal receives the RRC connection reconfiguration message sent by the serving base station, and configures the DRB and other SRBs according to the configuration information of the DRB and other SRBs.
  • the terminal sends an RRC connection reconfiguration complete message to the serving base station to notify the serving base station that the terminal has configured the DRB and other SRBs.
  • the serving base station receives an RRC connection reconfiguration complete message sent by the terminal.
  • S116-S118 may be considered as a process of establishing an air interface DRB and other SRBs, and the process may further include other steps, which are not detailed in this application.
  • S120 The MME sends a modify bearer request to the SGW/PGW.
  • the SGW/PGW receives the modified bearer request, and establishes a user plane bearer between the RAN-CNs that meets the requirements of the service request, and then executes S122.
  • the SGW/PGW sends a modify bearer response to the MME, and the MME receives the modified bearer response.
  • S120-S122 may be considered as a process of establishing a user plane bearer between the RAN-CN, and the process may further include other steps, which are not detailed in this application.
  • Figure 4 shows a schematic diagram of the process of re-active/resume in the NR system. Specifically, a schematic diagram of the process of the terminal transitioning from the inactive state to the connected state in the NR system is given. The process includes:
  • S202 to S204 Reference may be made to S102 to S104, and the present application is not limited thereto.
  • the terminal sends an RRC connection reactivation request to the serving base station.
  • the RRC Connection Reactivation Request includes an identity of the terminal in an inactive state.
  • the serving base station receives the RRC connection reactivation request sent by the terminal, and reads the locally stored context information of the terminal, and then activates the user plane bearer and the control plane bearer of the air interface.
  • the serving base station returns an RRC connection reactivation response to the terminal, to instruct the terminal to activate the user plane bearer and the control plane bearer of the air interface.
  • the terminal receives the RRC connection reactivation response sent by the serving base station, and then activates the user plane bearer and control plane bearer of the air interface.
  • the terminal sends an RRC connection reactivation complete message to the serving base station to notify the serving base station that the terminal has activated the user plane bearer and the control plane bearer of the air interface.
  • the serving base station receives an RRC connection reconfiguration complete message sent by the terminal.
  • the serving base station may obtain the context information of the terminal from the anchor base station, so as to complete the conversion of the anchor base station, specifically, the following step S207a may be performed before S208 after S206.
  • S207b completes the conversion of the anchor base station.
  • the RAN-CN connection can be switched from the anchor base station to the serving base station by using a path switch. Specifically, the path switching can be completed by performing the following steps S207c to S207f. It can be understood that if the serving base station is the same as the anchor base station, S207a to S207f may not be executed.
  • S207a The serving base station sends a context request to the anchor base station to request context information of the terminal.
  • the anchor base station receives the context request sent by the serving base station, and then performs S207b.
  • S207b The anchor base station sends a context response to the serving base station, where the context response includes context information of the terminal.
  • the serving base station receives the context response sent by the terminal, and saves the context information of the terminal, and then performs S207c.
  • S207c The serving base station sends a path switch request to the AMF entity, where the path switch request is used to request to switch the anchor base station to the serving base station.
  • the AMF entity receives the path switch request sent by the serving base station, and then performs S207d.
  • the AMF entity is used to control the UPF entity to perform path conversion.
  • S207d The AMF entity sends a modify bearer request to the UPF entity.
  • the UPF entity receives the modified bearer request sent by the AMF entity, and switches the RAN-CN connection from between the UPF entity and the anchor base station to the UPF entity and the serving base station. Then S207e is executed.
  • S207e The UPF entity sends a modify bearer response to the AMF entity.
  • S207f The AMF entity sends a path switch response to the serving base station.
  • the base station described hereinafter refers to the serving base station of the terminal.
  • FIG. 5 is a schematic diagram showing the interaction of a communication method provided by the present application. The method includes:
  • S302 The terminal transitions from an inactive state to an idle state, and saves the identifier of the terminal in an inactive state.
  • the terminal can autonomously transition from the inactive state to the idle state, that is, the terminal itself triggers the terminal to transition from the inactive state to the idle state. For example, but not limited to any of the following: the terminal loses cell coverage in an inactive state, for example, if the strength of the cell signal received by the terminal is lower than a certain threshold and continues to be lost for a period of time, the cell is considered to be idle. State; after the terminal fails to send RRC signaling multiple times, it transitions from an inactive state to an idle state. In addition, the terminal can also be switched from an inactive state to an idle state triggered by other network devices (ie, network devices other than the base station) or other terminals. Of course, this application is not limited to this.
  • the LTE protocol stipulates that when the terminal is in the inactive state, it saves the relevant information of the terminal in the inactive state, and deletes the related information of the terminal in the inactive state after the inactive state is converted to the idle state.
  • the base station saves related information of the terminal in an inactive state, and deletes the terminal in the non-active state after the current state of the recorded terminal is changed from the inactive state to the idle state. Information about the active state.
  • the related information of the terminal in the inactive state includes, but is not limited to, at least one of the following: the identifier of the terminal in the inactive state, the DRX configuration information of the terminal in the inactive state, and the cell information corresponding to the RNA of the terminal, such as the cell list.
  • the LTE protocol provides that when the terminal is in the idle state, the terminal may send a connection establishment request to the base station, and after receiving the connection establishment request, the base station triggers establishment of an air interface connection between the base station and the terminal, and the RAN between the base station and the CN device.
  • the CN is connected such that the terminal transitions from an idle state to a connected state. This process requires the establishment of an air interface connection and a RAN-CN connection, which results in a longer waiting time for communication between the base station and the terminal.
  • the base station when the base station receives the connection request sent by the terminal, the base station can multiplex/reuse the established RAN-CN connection, that is, it does not need to re-establish the RAN-CN connection, thereby facilitating the implementation of the base station and Communicate as quickly as possible between terminals.
  • the terminal may save the identifier of the terminal in an inactive state after transitioning from the inactive state to the idle state. For the identification of how to use the terminal in the inactive state, see below, and will not go into details here.
  • the terminal needs to send a state transition notification to the base station to notify the base station of the actual current state of the terminal.
  • the base station replies with a confirmation indication to the terminal to inform the terminal that the status transition notification has been successfully received.
  • the base station modifies the current state of the recorded terminal according to the state transition notification.
  • the actual current state of the terminal is synchronized with the current state of the terminal recorded by the base station, and the present application is directed to the state out-of-synchronization scenario. Based on this, the present application proposes a technical solution for determining the state out-of-synchronization. Limited to this.
  • S302 may include: when the terminal transitions from the inactive state to the idle state, and does not send a state transition notification to the base station, indicating that the state is out of synchronization, the identity of the terminal in the inactive state is saved. .
  • the terminal may not send a state transition notification to the base station after the terminal transitions from the inactive state to the idle state, where the present application knows how the terminal supports the inactive state of the base station.
  • the terminal supports the inactive state but does not send a state transition notification to the terminal after performing the transition from the inactive state to the idle state due to a failure or the like.
  • this application is not limited to this.
  • S302 may include: when the terminal transitions from an inactive state to an idle state, and fails to successfully send a state transition notification to the base station, indicating that the state is out of synchronization, the save terminal is in an inactive state.
  • logo For the terminal, if the acknowledgment indication about the state transition notification replied by the base station is not received, it is considered that the state transition notification is not successfully sent to the base station. It can be understood that the terminal fails to successfully send the state transition notification to the base station, which may include the following situations: First, the terminal has sent a state transition notification to the base station, but the base station does not receive the notification. Second, the base station has received the status transition notification sent by the terminal, but has not sent an acknowledgement indication to the terminal. Third, the base station has received the status transition notification sent by the terminal, and has replied to the terminal with an acknowledgment indication, but the acknowledgment indication has not been received by the terminal.
  • the terminal sends a connection request to the base station according to the identifier of the terminal in the inactive state.
  • the connection request may also be referred to as an RRC connection request.
  • the base station receives a connection request sent by the terminal.
  • the application does not limit the connection request sent by the terminal to the base station under what trigger condition. For example but not limited to the following two ways:
  • the terminal When the terminal needs to transmit uplink data, the terminal sends a connection request to the base station.
  • Mode 2 After receiving the RAN paging sent by the base station, the terminal sends a setup request to the base station.
  • the LTE protocol stipulates that the idle terminal only listens to CN paging, and the inactive terminal can listen to CN paging and RAN paging.
  • the base station can still send RAN paging to the terminal.
  • the terminal is currently in an idle state and cannot listen to RAN paging.
  • the present application provides a technical solution for supporting a terminal to listen to RAN paging in an idle state. This needs to consider the following two factors:
  • the terminal can recognize RAN paging in the idle state. Mainly reflected in the terminal needs to distinguish between CN paging and RAN paging in the idle state. Since the CN paging carries the identifier of the terminal in the inactive state, the CN paging carries the identifier of the terminal in the idle state. Therefore, the terminal can distinguish between the RAN paging and the CN paging according to the saved identifier of the terminal in the inactive state. For example, the identifiers of the same terminal are used in the RAN paging and the CN paging.
  • the information used in the present application is not limited to the identifier of the terminal. However, both of the pagings may carry an indication information to distinguish the two. Paging. Of course, this application is not limited to this.
  • the terminal can know the reception time of the RAN paging in the idle state.
  • the DRX configuration information may also be saved, so that the terminal can calculate the receiving time of the RAN paging according to the DRX configuration information.
  • the DRX configuration information may include, but is not limited to, a RAN configured paging DRX cycle.
  • the implementation process of the terminal calculating the reception time of the RAN paging according to the DRX configuration information may refer to the prior art.
  • the receiving time of the terminal at the RAN paging can be implemented, and the RAN paging is monitored to receive the RAN paging.
  • the method may further include: S303a-S303b, reference may be made to the foregoing S102-S104, and the application is not limited thereto.
  • the format of the connection request can be referred to below.
  • S306 The base station sends a reconfiguration activation response to the terminal, and the terminal receives the reconfiguration activation response.
  • the terminal sends an RRC connection reactivation complete message to the base station, and the base station receives the RRC connection reactivation complete message.
  • S304-S308 can be considered as a process in which the terminal and the base station are configured to be connected to the air interface, and the base station reuses the RAN-CN connection.
  • S306 to S308 reference may be made to the above, and details are not described herein again.
  • the base stations in the above S302 to S308 refer to the serving base station. 4, and the related description above with respect to FIG. 4, if the serving base station is the same as the anchor base station, after executing S304, S306 may be performed. If the serving base station is different from the anchor base station, the method may further include 305 after S304 and before S306, wherein the specific implementation of S305 may refer to S207a to S207f. It should be noted that the terminal may obtain the ID of the serving base station from the system message or obtain the ID of the serving base station from the synchronization message (such as the primary synchronization message or the secondary synchronization message).
  • the terminal may extract the ID of the anchor base station from the ID of the terminal allocated by the RAN device, and then save the ID of the anchor base station. In this way, the terminal can determine whether the serving base station and the anchor base station are the same by comparing whether the ID of the anchor base station is the same as the ID of the serving base station.
  • the terminal saves the information about the inactive state in the idle state to trigger the resume/reactive process in the inactive state.
  • the terminal in the idle state, the terminal initiates a connection process by using the identifier of the terminal in an inactive state, thereby establishing an air interface connection, and reusing the established RAN-CN connection related to the inactive state identifier.
  • the method can be applied to a state out-of-synchronization scenario, and in this scenario, the base station sends a connection establishment request from the idle state to the connected state to the base station in an idle state, so that the base station establishes an air interface connection and a RAN-CN connection.
  • the solution provided by the application helps to realize communication between the base station and the terminal as soon as possible.
  • the format of the connection request can be implemented by one of the following methods:
  • connection request multiplex connection establishment request such as an RRC connection establishment request. specific:
  • the RRC connection establishment request includes an identifier of the terminal in an idle state and an identifier of the terminal in an inactive state. Moreover, the identifier of the terminal in the idle state is valid, and the identifier of the terminal in the inactive state may be valid or invalid.
  • the identifier of the terminal in the inactive state is invalid.
  • the identifier of the terminal in the inactive state may be set to a preset value or an invalid value. If the RAN assigns an identity to the terminal, the identity of the terminal in the inactive state is valid. Of course, this application is not limited to this. In addition, in this manner, it is considered that the CN assigns an identifier to the terminal, that is, the identifier of the terminal in the idle state is valid.
  • the RRC connection setup request message may be used to trigger S306-S308 or S305-S308 in FIG. 5; or, if the execution of S305-S308 fails, if the serving base station fails in S207b In the case, the trigger is similar to S110 to S122 in FIG. 2, as shown in FIG. 6.
  • This embodiment can be understood as: when the terminal transitions from the inactive state to the idle state, the connection process is initiated according to the identifier of the terminal in the inactive state; and in the case of failure, the connection is initiated according to the identifier of the terminal in the idle state.
  • the RRC connection establishment request carries the identifier of the terminal in the idle state and the identifier of the terminal in the inactive state, so that it can ensure that the connection process fails according to the identifier of the terminal in the inactive state.
  • the connection process is initiated according to the identifier of the terminal in the idle state in the RRC connection establishment request, thereby saving signaling overhead and facilitating communication between the base station and the terminal as soon as possible.
  • the RRC connection setup request includes an identifier of the terminal in an idle state and an identifier of the terminal in an inactive state. Moreover, the identifier of the terminal in the idle state is valid and the identifier of the terminal in the inactive state is invalid; or the identifier of the terminal in the idle state is invalid and the identifier of the terminal in the inactive state is valid.
  • An implementation manner in which the identifier of the terminal in the inactive state is invalid is: setting the identifier of the terminal in the inactive state in the RRC connection establishment request to a preset value or an invalid value.
  • the identifier of the terminal in the idle state is invalid.
  • the implementation manner is: setting the identifier of the terminal in the idle state in the RRC connection establishment request to a preset value or an invalid value.
  • the RRC connection setup request message may be used to trigger S110-S122 in FIG. If the identifier of the terminal in the idle state is invalid and the identifier of the terminal in the inactive state is valid, the RRC connection setup request message may be used to trigger S306-S308 or S305-S308 in FIG. 5; or, in the case where the execution of S305-S308 fails. If the serving base station fails in S207b, the triggering is similar to S110-S122 in FIG. 2, as shown in FIG. 6. Different from the mode 1, the terminal needs to carry the identifier of the terminal in the idle state in S110.
  • the RRC connection establishment request includes the identifier and the indication information of the terminal, and the identifier of the terminal is, for example but not limited to, the identifier of the terminal in an idle state or the identifier of the terminal in an inactive state or other information used to identify the terminal.
  • the indication information is used to indicate the type of connection establishment request, and different types have different functions. For example, if the indication information occupies 1 bit, if the indication information is "1", the connection establishment request can be used to trigger S110-S122 in FIG. 3; if the indication information is "0", the connection establishment request can be used to trigger the diagram. S306 to S308 or S305 to S308 in 5.
  • the indication information may also be used to indicate the type of the identifier of the terminal carried by the message. For example, if the indication information occupies 1 bit, if the indication information is "1", it indicates that the RRC connection establishment request carries the identifier of the terminal in the idle state, triggering S110 to S122 in FIG. 3; if the indication information is "0"
  • the RRC connection setup request carries the identifier of the terminal in the inactive state, and triggers S306-S308 or S305-S308 in FIG.
  • connection request is a connection recovery request, such as an RRC connection recovery request in the LTE system and the NR system, or a connection re-establishment request in the LTE system and the NR system, or an RRC connection reactivation request in the NR system or the like.
  • the connection recovery request is an RRC connection reactivation request as an example.
  • RRC connection reactivation request For the role of the RRC connection reactivation request, reference may be made to the above, and details are not described herein again.
  • the connection request is a new RRC message, that is, a new RRC message type is defined in the present application.
  • the new RRC message includes the identity of the terminal in the idle state and the identity of the terminal in the inactive state. For related description, refer to mode 1 or mode 2 in (1) above.
  • the new RRC message includes an identifier and an indication information field of the terminal. For related description, refer to mode 3 in (1) above.
  • the present application provides the following embodiments:
  • an effective time is set for the terminal to maintain the validity of the saved "identity of the terminal in an inactive state" in the idle state.
  • the effective time may be preset in the terminal, or may be notified to the terminal by the base station by using a signaling manner, such as RRC signaling.
  • the present application does not limit the size and determination manner of the duration of the effective time.
  • the terminal may delete the identifier of the terminal in the inactive state when the terminal ends/after the validity time of the identifier of the inactive state.
  • a timer may be set in the terminal, and the timer may start timing from transitioning to the idle state, and discard the identifier of the terminal in the inactive state when the valid time ends/after, thereby saving the storage resource of the terminal.
  • S302 can be implemented as: when the terminal transitions from the inactive state to the idle state, and the identifier of the terminal in the inactive state is within the valid time, the identifier of the terminal in the inactive state is saved. .
  • the base station may configure a periodic RAN-based notification area update (RNAU) or a periodic RAN-based location area update for the inactive terminal ( RAN-based location area update, RLAU).
  • RNAU periodic RAN-based notification area update
  • RLAU periodic RAN-based location area update
  • the validity of the identity of the terminal in the inactive state can be updated when the RNAU is successfully completed, and if it fails, the terminal switches to the idle state; of course, the terminal can also adopt any of the methods provided above. Switch to idle state.
  • the periodic RNAU can be configured for the inactive terminal, and then the current state of the terminal can be recorded as an idle state after the periodic RNAU timeout, thereby achieving state synchronization.
  • the present application provides a way to set the effective time of the identification of the terminal in the inactive state.
  • the period of the RNAU is T1
  • the effective time is T2 as an example
  • the terminal when the terminal removes the identifier-related RNA of the terminal in the inactive state, the terminal may delete the identifier of the terminal in the inactive state, thereby saving the storage resource of the terminal.
  • the RNA if the identifier of the terminal in the inactive state is allocated by the device in the certain RNA, the RNA is the RNA related to the identification of the terminal in the inactive state.
  • the application does not limit how the terminal determines whether to remove a certain RNA in an idle state. For example, the terminal may save the cell information corresponding to the RNA after transitioning from the inactive state to the idle state. In this way, the terminal can determine whether the terminal has removed the RNA according to the cell information corresponding to the RNA.
  • the cell information corresponding to the RNA may include, but is not limited to, a cell list corresponding to the RNA. It can be understood that, after the terminal moves out of the identifier-related RNA of the terminal in the inactive state, the terminal can also delete the cell information corresponding to the RNA, thereby further saving the storage resource of the terminal.
  • each network element such as a base station or a terminal.
  • each network element such as a base station or a terminal.
  • it includes hardware structures and/or software modules corresponding to the execution of the respective functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functionality for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may divide a function module into a base station or a terminal according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner. The following is an example of dividing each functional module by using corresponding functions.
  • the embodiment of the present application further provides an information transmission device, which may be a terminal.
  • the terminal can be used to perform the steps performed by the terminal in FIG. Figure 6 shows a simplified schematic diagram of the terminal structure. It is convenient for understanding and illustration.
  • the terminal uses a mobile phone as an example.
  • the terminal includes a processor, a memory, a radio frequency circuit, an antenna, and an input and output device.
  • the processor is mainly used for processing communication protocols and communication data, and controlling terminals, executing software programs, processing data of software programs, and the like.
  • Memory is primarily used to store software programs and data.
  • the RF circuit is mainly used for the conversion of the baseband signal and the RF signal and the processing of the RF signal.
  • the antenna is mainly used to transmit and receive RF signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, keyboards, etc., are primarily used to receive user input data and output data to the user. It should be noted that some types of terminals may not have input and output devices.
  • the processor When the data needs to be sent, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal, and then sends the radio frequency signal to the outside through the antenna in the form of electromagnetic waves.
  • the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data.
  • the memory may also be referred to as a storage medium or a storage device or the like.
  • the memory may be independent of the processor, or may be integrated with the processor, which is not limited in this embodiment of the present application.
  • the antenna and the radio frequency circuit having the transceiving function can be regarded as the transceiving unit of the terminal, and the processor having the processing function can be regarded as the processing unit of the terminal.
  • the terminal includes a transceiver unit 701 and a processing unit 702.
  • the transceiver unit can also be referred to as a transceiver, a transceiver, a transceiver, and the like.
  • the processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, and the like.
  • the device for implementing the receiving function in the transceiver unit 701 can be regarded as a receiving unit, and the device for implementing the sending function in the transceiver unit 701 is regarded as a sending unit, that is, the transceiver unit 701 includes a receiving unit and a sending unit.
  • the transceiver unit may also be referred to as a transceiver, a transceiver, or a transceiver circuit.
  • the receiving unit may also be referred to as a receiver, a receiver, or a receiving circuit or the like.
  • the transmitting unit may also be referred to as a transmitter, a transmitter, or a transmitting circuit, and the like.
  • the processing unit 702 is configured to determine an identity of the terminal in an inactive state when the terminal is in an idle state, and/or other steps in the application.
  • the transceiver unit 701 is configured to perform the steps performed by the terminal in S304 in FIG. 5, and/or other steps in the present application.
  • the apparatus may further include: the storage unit 703 for performing S302 in FIG. 5, and/or other steps in the application.
  • the embodiment of the present application further provides an information transmission device.
  • the information transmission device can be a base station.
  • Figure 8 shows a schematic diagram of a simplified base station structure.
  • the base station includes a 801 part and an 802 part.
  • the 801 part is mainly used for the transmission and reception of radio frequency signals and the conversion of radio frequency signals and baseband signals; the 802 part is mainly used for baseband processing and control of base stations.
  • Section 801 can be generally referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver.
  • the 802 portion is typically the control center of the base station and may be referred to as a processing unit for controlling the base station to perform the steps performed by the base station (i.e., the serving base station) of FIG. 5 above.
  • a processing unit for controlling the base station to perform the steps performed by the base station (i.e., the serving base station) of FIG. 5 above.
  • the transceiver unit of the 801 part which may also be called a transceiver, or a transceiver, etc., includes an antenna and a radio frequency unit, wherein the radio frequency unit is mainly used for radio frequency processing.
  • the device for implementing the receiving function in the 801 part may be regarded as a receiving unit
  • the device for implementing the transmitting function may be regarded as a transmitting unit, that is, the 801 portion includes a receiving unit and a transmitting unit.
  • the receiving unit may also be referred to as a receiver, a receiver, or a receiving circuit, etc.
  • the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit or the like.
  • the 802 portion may include one or more boards, each of which may include one or more processors and one or more memories for reading and executing programs in the memory to implement baseband processing functions and for base stations control. If multiple boards exist, the boards can be interconnected to increase processing power. As an optional implementation manner, multiple boards share one or more processors, or multiple boards share one or more memories, or multiple boards share one or more processes at the same time. Device.
  • the transceiver unit is operative to perform the steps performed by the serving base station in S304 of FIG. 3, and/or other steps in the application.
  • the processing unit is operative to perform the steps of the processing performed by the serving base station in S305, and/or other steps in the application.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil de communication, appartenant au domaine technique des communications. En particulier, l'invention concerne une solution technique d'établissement d'une connexion entre une station de base et un terminal. Le procédé peut comprendre les étapes suivantes : un terminal dans un état de veille détermine un identifiant du terminal dans un état non actif; et le terminal initie une procédure de connexion en fonction de l'identifiant du terminal dans un état non actif. La solution technique peut être appliquée à un scénario de rétroaction d'état.
PCT/CN2018/085178 2017-05-24 2018-04-28 Procédé et appareil de communication Ceased WO2018214708A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710374520.2A CN109246819B (zh) 2017-05-24 2017-05-24 一种通信方法和装置
CN201710374520.2 2017-05-24

Publications (1)

Publication Number Publication Date
WO2018214708A1 true WO2018214708A1 (fr) 2018-11-29

Family

ID=64395251

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085178 Ceased WO2018214708A1 (fr) 2017-05-24 2018-04-28 Procédé et appareil de communication

Country Status (2)

Country Link
CN (1) CN109246819B (fr)
WO (1) WO2018214708A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220159552A1 (en) * 2019-03-28 2022-05-19 Henry Chang Resume failure report for failed attempt to resume connected state from inactive state

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020172844A1 (fr) * 2019-02-28 2020-09-03 华为技术有限公司 Procédé et appareil de communication
CN111757531A (zh) * 2019-03-27 2020-10-09 普天信息技术有限公司 随机接入的回退方法及装置
CN112188568B (zh) * 2019-07-03 2022-05-24 华为技术有限公司 一种通信的方法
CN112788618B (zh) * 2019-11-06 2023-05-12 大唐移动通信设备有限公司 非连续接收参数的配置、监听寻呼的方法、设备及终端
US12317227B2 (en) 2020-02-13 2025-05-27 Nokia Technologies Oy Paging in wireless systems
CN115226153A (zh) * 2021-04-20 2022-10-21 大唐移动通信设备有限公司 信令发送方法、装置及存储介质
CN119325117A (zh) * 2023-07-17 2025-01-17 华为技术有限公司 一种基于卫星通信的通信方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009020335A1 (fr) * 2007-08-06 2009-02-12 Samsung Electronics Co., Ltd. Procédé de réduction de la consommation d'énergie dans un ue lorsque l'ue est en mode veille
CN102143598A (zh) * 2010-11-11 2011-08-03 华为技术有限公司 信令处理方法和系统以及网络侧设备和终端
CN103338500A (zh) * 2012-12-24 2013-10-02 上海华为技术有限公司 一种数据传输方法、装置、系统及网络侧设备和终端设备
CN103379593A (zh) * 2012-04-26 2013-10-30 中兴通讯股份有限公司 一种终端节电方法及终端节电装置及网络侧节电装置
US20150189480A1 (en) * 2011-04-03 2015-07-02 Lg Electronics Inc. Method of transmitting message at user equipment in wireless communication system and apparatus thereof

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6801619B1 (en) * 2000-09-28 2004-10-05 Helpcaster Technologies Inc. Device and system to facilitate remote customer-service
US7796547B2 (en) * 2004-08-06 2010-09-14 Nextel Communications Inc. Method and apparatus for providing information to mobile stations in inactive states
CN101951635B (zh) * 2010-09-16 2013-10-02 展讯通信（上海）有限公司 多卡多待的通信装置及其非业务卡的增益跟踪方法
CN104039023B (zh) * 2013-03-05 2018-05-22 电信科学技术研究院 一种进行rrc连接重建的方法及用户设备
CN104754767B (zh) * 2013-12-25 2019-03-01 华为技术有限公司 状态更新方法及设备
CN110691429B (zh) * 2016-05-13 2021-02-12 华为技术有限公司 Rrc状态的控制方法和装置
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009020335A1 (fr) * 2007-08-06 2009-02-12 Samsung Electronics Co., Ltd. Procédé de réduction de la consommation d'énergie dans un ue lorsque l'ue est en mode veille
CN102143598A (zh) * 2010-11-11 2011-08-03 华为技术有限公司 信令处理方法和系统以及网络侧设备和终端
US20150189480A1 (en) * 2011-04-03 2015-07-02 Lg Electronics Inc. Method of transmitting message at user equipment in wireless communication system and apparatus thereof
CN103379593A (zh) * 2012-04-26 2013-10-30 中兴通讯股份有限公司 一种终端节电方法及终端节电装置及网络侧节电装置
CN103338500A (zh) * 2012-12-24 2013-10-02 上海华为技术有限公司 一种数据传输方法、装置、系统及网络侧设备和终端设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220159552A1 (en) * 2019-03-28 2022-05-19 Henry Chang Resume failure report for failed attempt to resume connected state from inactive state
US12114388B2 (en) * 2019-03-28 2024-10-08 Kyocera Corporation Resume failure report for failed attempt to resume connected state from inactive state

Also Published As

Publication number Publication date
CN109246819A (zh) 2019-01-18
CN109246819B (zh) 2021-05-11

Similar Documents

Publication Publication Date Title
WO2018214708A1 (fr) Procédé et appareil de communication
CN110366224B (zh) 信令优化方法、设备、计算机可读存储介质和通信系统
CN109479253B (zh) 用于非活动用户设备的无线电接入网络中的ue上下文的存储的方法和设备
CN108924949B (zh) 无线网络中的通信方法、装置和系统
CN109076496B (zh) 用于改变终端连接状态的方法和装置
CN104247553B (zh) 建立连接的方法及设备
JP6123009B1 (ja) ユーザ装置、基地局、及び接続確立方法
CN107708104B (zh) 辅基站变更的方法及装置
CN114630381B (zh) 无线通信系统中的安全性上下文
JP7540502B2 (ja) 端末装置及び基地局
WO2018019001A1 (fr) Procédé et appareil de changement d'état d'un terminal
CN108617033B (zh) 通信的方法、终端和接入网设备
CN110381554B (zh) 通信方法、装置、系统和计算机存储介质
EP3639620A1 (fr) Noeud de réseau radio, dispositif sans fil, et procédés réalisés associés
WO2023065910A1 (fr) Procédé et dispositif d'envoi/réception d'informations de terminal distant
JP2017208794A (ja) ユーザ装置、基地局、及び接続確立方法
WO2015018304A1 (fr) Procédé et dispositif de configuration d'hôte
EP3711321B1 (fr) Procédé de rétablissement de connexion rrc, terminal et support de stockage
JP2024113129A (ja) 端末装置、通信のための方法、基地局及び基地局の方法
JP7647944B2 (ja) ユーザ装置、無線アクセスネットワークノード、及び方法
CN109151800B (zh) 通信方法和设备
JP2025066818A (ja) 端末装置において実行される方法、ネットワーク装置において実行される方法、端末装置及びネットワーク装置
CN116074911B (zh) 用于无线通信的方法及用户设备
CN108353452A (zh) 用户装置、基站、和连接建立方法
EP3506675A1 (fr) Procédé et appareil de mise à jour d'une zone de position côté réseau

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: 18806890

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18806890

Country of ref document: EP

Kind code of ref document: A1