WO2018001151A1 - 寻呼方法、ran-up实体、ran-cp实体及ue - Google Patents

寻呼方法、ran-up实体、ran-cp实体及ue Download PDF

Info

Publication number
WO2018001151A1
WO2018001151A1 PCT/CN2017/089367 CN2017089367W WO2018001151A1 WO 2018001151 A1 WO2018001151 A1 WO 2018001151A1 CN 2017089367 W CN2017089367 W CN 2017089367W WO 2018001151 A1 WO2018001151 A1 WO 2018001151A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran
entity
data packet
message
paging
Prior art date
Application number
PCT/CN2017/089367
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 EP17819148.2A priority Critical patent/EP3477975B1/en
Publication of WO2018001151A1 publication Critical patent/WO2018001151A1/zh
Priority to US16/232,972 priority patent/US10966176B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/12Mobility data transfer between location registers or mobility servers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005Transmission of information for alerting of incoming communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/11Allocation or use of connection identifiers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/25Maintenance of established connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/022Selective call receivers
    • H04W88/023Selective call receivers with message or information receiving capability
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to, but is not limited to, a wireless communication technology, and in particular, a paging method, a RAN-UP (Residential Access Network User Plane) entity, and a RAN-CP (Residential Access Network Control Plane) Network control plane) entity and user equipment (UE, User Equipment).
  • a RAN-UP Residential Access Network User Plane
  • RAN-CP Residential Access Network Control Plane
  • UE User Equipment
  • 5G will conduct further technical research in terms of greater throughput, more user connections, lower latency, higher reliability, and lower power consumption.
  • 5G technology goals by 2020, to achieve 1000 times mobile data traffic growth per region, 10 to 100 times per UE throughput growth, 10 to 100 times the number of connected devices, low-power devices 10 The battery life is doubled and the end-to-end 5x delay is reduced.
  • 5G research puts forward higher performance requirements, one of which is to propose a 10ms index requirement for control plane state transition (from no data to data transmission), and on this basis, the UE can save as much as possible. Electricity. Therefore, a new UE state-sleep state is needed.
  • the UE and the network side do not have dedicated connection state resources, and the UE-level bearer connection is maintained between the network side and the core network. Due to the diversity of 5G terminals, this sleep state can be applied to various terminals and services such as mobile phones and IoT devices. The priority of these services and the characteristics of the data packets will place new demands on the dormant state.
  • the RAN control plane and the RAN user plane also tend to be a separate architecture, so that the RAN control plane
  • the anchor point can be separated from the RAN user plane anchor point to implement an SDN-based flexible deployment architecture.
  • the embodiment of the present invention provides a paging method, a RAN-UP entity, a RAN-CP entity, and a UE, to implement a paging operation in a dormant state.
  • the paging method provided by the embodiment of the present invention is applied to a RAN user plane (RAN-UP) entity; the method includes:
  • the RAN-UP entity receives the data packet sent by the core network
  • the RAN-UP entity transmits the data packet or control message to a RAN Control Plane (RAN-CP) entity.
  • RAN-CP RAN Control Plane
  • the RAN-UP entity receives the data packet sent by the core network, and includes:
  • the RAN-UP entity receives the data packet sent by the core network through the first interface.
  • the first interface is S1 or S1-U.
  • the RAN-UP entity sends the data packet or control message to the RAN control plane RAN-CP entity, including:
  • the RAN-UP entity sends the data packet or control message to the RAN control plane RAN-CP entity through the second interface; wherein the control message is a data arrival indication or a paging indication.
  • the second interface is an Xn port, and n is an integer.
  • the method further includes:
  • the interface information corresponding to the second interface carries the service identifier information; or the data packet and the service identifier are The information is packet encoded into a data stream and sent to the RAN-CP entity.
  • the service identifier information is at least one of a service logical channel identifier ID and a service bearer ID of the data packet.
  • a paging method provided by another embodiment of the present invention is applied to a RAN-CP entity; the method includes:
  • the RAN-CP entity receives the data packet sent by the RAN-UP entity, and the RAN-CP entity
  • the data packet is encapsulated in a paging message and sent to the UE.
  • the paging message carries a first indication message, where the first indication message is used to indicate that the UE remains in the paging message when it receives the paging message. Sleeping state, and extracting the data packet from the paging message; or
  • the RAN-CP entity receives the control message sent by the RAN-UP entity, and the RAN-CP entity encapsulates the paging message and sends the message to the UE.
  • the paging message carries the second indication message, and the second indication message is used by the RAN-CP entity.
  • the UE When the UE is instructed to receive the paging message, it moves out of the dormant state to enter a connected state, and receives a data packet sent by the RAN-UP entity.
  • the RAN-CP entity receives a data packet or a control message sent by the RAN-UP entity, including:
  • the RAN-CP entity receives a data packet or a control message sent by the RAN-UP entity through the second interface; wherein the control message is a data arrival indication or a paging indication.
  • the second interface is an Xn port, and n is an integer.
  • the method further includes:
  • the service identifier information is extracted from the interface message corresponding to the second interface; and the service identifier information is encapsulated in the paging message. Sent to the UE; or,
  • the service identification information is integrated into the data packet in an encoded form, and the data packet is encapsulated in a paging message and sent to the UE; or the encoded data packet sent by the RAN-UP entity and the data of the service identification information The flow encapsulation is sent to the UE in the paging message;
  • the service identification information is at least one of a service logical channel identifier ID and a service bearer ID of the data packet.
  • a paging method according to another embodiment of the present invention is applied to a UE, where the method includes:
  • a paging method according to another embodiment of the present invention is applied to a UE, where the method includes:
  • a first receiving unit configured to receive a data packet sent by the core network
  • the first sending unit is configured to send the data packet or control message to the RAN control plane RAN-CP entity.
  • the first receiving unit is configured to receive a data packet sent by the core network through the first interface.
  • the first sending unit is configured to send the data packet or control message to the RAN control plane RAN-CP entity by using the second interface, where the control message is a data arrival indication or a paging indication.
  • the RAN-UP entity further includes: a first processing unit, configured to: when the data packet is sent to the RAN-CP entity by using the second interface, in the interface message corresponding to the second interface Carrying the service identification information; or encoding the service identification information into a data stream and sending the data to the RAN-CP entity; wherein the service identification information is at least one of a service logical channel identifier ID and a service bearer ID of the data packet.
  • a first processing unit configured to: when the data packet is sent to the RAN-CP entity by using the second interface, in the interface message corresponding to the second interface Carrying the service identification information; or encoding the service identification information into a data stream and sending the data to the RAN-CP entity; wherein the service identification information is at least one of a service logical channel identifier ID and a service bearer ID of the data packet.
  • a second receiving unit configured to receive a data packet or a control message sent by the RAN-UP entity
  • a second sending unit configured to encapsulate the data packet in a paging message and send the message to the UE, where the paging message carries a first indication message, where the first indication message is used to indicate that the UE receives the And the paging message is kept in a dormant state, and the data packet is extracted from the paging message; or is configured to send a paging message to the UE; wherein the paging message carries a second And an indication message, where the second indication message is used to indicate that when receiving the paging message, the UE moves out of the dormant state to enter a connected state, and receives a data packet sent by the RAN-UP entity.
  • the second receiving unit is configured to receive, by using the second interface, a data packet or a control message sent by the RAN-UP entity; where the control message is data arrival Indication or paging indication.
  • the RAN-CP entity further includes: a second processing unit, configured to: when receiving the data packet sent by the RAN-UP entity by using the second interface, extracting from the interface message corresponding to the second interface Business identification information;
  • the second processing unit is further configured to encapsulate the service identification information in the paging message and send the message to the UE; or, the service identification information is integrated into the data packet and sent to the UE in an encoded form; or Encapsulating the data packet of the RAN-UP entity encoded data packet and the service identifier information in the paging message, and sending the data packet to the UE;
  • the service identification information is at least one of a service logical channel identifier ID and a service bearer ID of the data packet.
  • the UE provided by the embodiment of the present invention is in a dormant state, and the UE includes:
  • a third receiving unit configured to receive a paging message sent by the RAN-CP entity
  • a first extracting unit configured to extract a first indication message from the paging message
  • the third processing unit is configured to remain in a dormant state according to the indication of the first indication message, and extract a data packet from the paging message in a dormant state.
  • the UE provided by the embodiment of the present invention is in a dormant state, and the UE includes:
  • a fourth receiving unit configured to receive a paging message sent by the RAN-CP entity
  • a second extracting unit configured to extract a second indication message from the paging message
  • the fourth processing unit is configured to move out of the dormant state to enter the connected state according to the indication of the second indication message, and receive the data packet sent by the RAN-UP entity in the connected state.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the paging method.
  • the RAN-UP entity receives a data packet sent by the core network, and the RAN-UP entity sends the data packet to the RAN-CP entity.
  • the first indication message is used to indicate that the UE keeps when receiving the paging message. In a dormant state, and extracting the data packet from the paging message.
  • the RAN-UP entity receives the data packet transmitted by the core network; the RAN-UP entity sends the data packet arrival indication or paging indication to the RAN-CP entity.
  • the RAN-CP entity receives the data packet arrival indication or the paging indication sent by the RAN-UP entity; the RAN-CP entity encapsulates the paging message and sends the paging message to the UE, where the paging message carries the second indication message,
  • the second indication message is used to indicate that when receiving the paging message, the UE moves out of the dormant state to enter a connected state, and receives a data packet sent by the RAN-UP entity.
  • FIG. 1 is a schematic structural diagram of a RAN-CP entity and a RAN-UP entity according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a paging method according to Embodiment 1 of the present invention.
  • FIG. 3 is a schematic flowchart of a paging method according to Embodiment 2 of the present invention.
  • FIG. 4 is a flowchart of an application scenario 1 according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of application scenario 2 according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of application scenario 3 according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a structure of a RAN-UP entity according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a structure of a RAN-CP entity according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a structure of a UE according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a UE according to another embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a RAN-CP entity and a RAN-UP entity architecture according to an embodiment of the present invention.
  • the core network downlink data
  • the packet arrives at the RAN-UP entity through the S1-U.
  • the RAN-UP entity optionally performs two processes:
  • Procedure 1 The RAN-UP entity forwards the data packet to the RAN-CP entity through the Xn interface message.
  • the Xn interface message may carry, but is not limited to, the service logical channel ID of the data packet or the bearer ID of the service.
  • the RAN-CP entity receives the message sent by the RAN-UP entity through the Xn interface, and extracts the data packet in the message.
  • the service logical channel ID of the data packet or the bearer ID of the service in the message may be extracted in the message;
  • the data packet (in an embodiment, the service logical channel ID of the data packet or the bearer ID of the service) is encapsulated in the paging message and transmitted to the UE, and the paging message indicates that the UE does not migrate out of the sleep state.
  • the UE receives the data packet in the paging message, but the UE does not need to migrate the sleep state.
  • the RAN-UP entity notifies the RAN-CP entity that the data packet arrives through the Xn interface message, and the Xn interface message indicates that the data packet arrives.
  • the RAN-CP entity After receiving the message sent by the RAN-UP entity through the Xn interface, the RAN-CP entity sends a packet paging message to the UE; the paging message indicates that the UE moves out of the sleep state.
  • the UE receives the paging message, and the UE initiates the process to move out of the dormant state and enters the connected state, and the UE receives the downlink data packet sent by the RAN-UP entity in the connected state.
  • the technical solution of the UE supports the data reception in the dormant state of the UE and the data transmission in the state wake-up and outbound according to the service attribute.
  • FIG. 2 is a schematic flowchart of a paging method according to Embodiment 1 of the present invention. As shown in FIG. 2, the method includes the following steps:
  • Step 201 The RAN-UP entity receives the data packet sent by the core network.
  • the RAN-UP entity receives the data packet sent by the core network through the S1-U interface.
  • Step 202 The RAN-UP entity sends the data packet to a RAN-CP entity.
  • the RAN-UP entity sends the data packet to the RAN control plane RAN-CP entity through the Xn interface.
  • the service identifier information is carried in the interface message corresponding to the Xn interface;
  • the service identification information is at least one of a service logical channel identifier ID and a service bearer ID of the data packet.
  • Step 203 The RAN-CP entity receives the data packet sent by the RAN-UP entity.
  • the RAN-CP entity receives the data packet sent by the RAN-UP entity through the Xn interface.
  • Step 204 The RAN-CP entity encapsulates the data packet in a paging message and sends the data packet to the UE.
  • the paging message carries a first indication message.
  • the first indication message is used to indicate that the UE remains in a dormant state when receiving the paging message, and extracts the data packet from the paging message.
  • the service identifier information is extracted from the interface message corresponding to the second interface; Encapsulating is sent to the UE in the paging message; or
  • the service identification information is integrated into the data packet in an encoded form, and the data packet is encapsulated in a paging message and sent to the UE; or
  • the encoded data packet sent by the RAN-UP entity and the data flow of the service identification information are encapsulated in the paging message and sent to the UE.
  • Step 205 Receive a paging message sent by the RAN-CP entity when the UE is in the dormant state.
  • Step 206 The UE extracts the first indication message from the paging message.
  • Step 207 The UE remains in a dormant state according to the indication of the first indication message, and is in a dormant state.
  • the data packet is extracted from the paging message in a sleep state.
  • FIG. 3 is a schematic flowchart of a paging method according to Embodiment 2 of the present invention. As shown in FIG. 3, the method includes the following steps:
  • Step 301 The RAN-UP entity receives the data packet sent by the core network.
  • the RAN-UP entity sends a data packet arrival indication or paging indication to the RAN-CP entity.
  • Step 302 The RAN-UP entity sends a data packet reaching indication or paging indication to the RAN-CP entity.
  • the RAN-UP entity sends a data packet indication or paging indication to the RAN-CP entity through the Xn interface.
  • Step 303 The RAN-CP entity receives the data packet reaching indication or paging indication sent by the RAN-UP entity.
  • the RAN-CP entity receives the data packet arrival indication or paging indication sent by the RAN-UP entity through the Xn interface.
  • Step 304 The RAN-CP entity encapsulates a paging message and sends the paging message to the UE, where the paging message carries a second indication message.
  • the second indication message is used to indicate that when receiving the paging message, the UE moves out of the dormant state to enter a connected state, and receives a data packet sent by the RAN-UP entity.
  • Step 305 Receive a paging message sent by the RAN-CP entity when the UE is in the dormant state.
  • Step 306 The UE extracts a second indication message from the paging message.
  • Step 307 The UE moves out of the dormant state to enter the connected state according to the indication of the second indication message, and receives the data packet sent by the RAN-UP entity in the connected state.
  • the data packet is carried to the UE by using a paging message, where the UE receives the data packet in a dormant state.
  • Step 401 The RAN-UP entity receives the user plane of the core network (CN, Core Network). Line data packet.
  • CN Core Network
  • Step 402 The RAN-UP entity determines that the RAN-UP entity can be sent in the UE sleep state according to the service bearer or the data packet header information of the data packet.
  • the packet header information includes, but is not limited to, a QoS (Quality of Service) level.
  • QoS Quality of Service
  • Step 403 The RAN-UP entity determines that the packet length is less than a certain threshold.
  • Step 404 The RAN-UP entity encapsulates the data packet into an Xn interface message between the RAN-CP entity and the message, and may include, but is not limited to, a service bearer ID or a logical channel ID of the data packet.
  • the RAN-UP entity then sends the message to the RAN-CP entity.
  • Step 405 The RAN-CP entity receives the message sent by the RAN-UP entity through the Xn interface, and extracts the data packet and the message cell in the message.
  • Step 406 The RAN-CP entity encapsulates the data packet into a paging message.
  • the service bearer ID or the logical channel ID of the data packet may be added to the paging message, and the paging message indicates that the UE does not need to move out of the sleep state and receive the data packet in the paging.
  • Step 407 The RAN-CP entity sends a paging message to the UE.
  • Step 408 The UE receives the paging message in the dormant state, maintains the dormant state, and receives the data packet in the paging message, and according to, but not limited to, the service bearer ID encapsulated by the RAN-UP entity in the data packet, the logical channel ID, and the like.
  • the information is delivered to the corresponding business session.
  • the UE is moved out of the sleep state by the paging message to receive the data packet.
  • Step 501 The RAN-UP entity receives the downlink data packet of the CN user plane.
  • Step 502 The RAN-UP entity determines that the eNB may not be sent in the UE sleep state according to the service bearer or the data packet header information of the data packet.
  • the header information includes, but is not limited to, a QoS class.
  • Step 503 The RAN-UP entity encapsulates an Xn interface message between one RAN-CP entity, The message includes, but is not limited to, indicating that the RAN-CP entity has an acceptable packet arrival. The message is then sent to the RAN-CP entity.
  • Step 504 The RAN-CP entity receives the message sent by the RAN-UP entity through the Xn interface, and the encapsulated paging message is sent to the UE, indicating that the UE needs to move out of the sleep state.
  • Step 505 The UE receives the paging message in the dormant state, and initiates the request to move out of the dormant state.
  • Step 506 The UE moves out of the sleep state, and starts the data packet transmission after entering the connection state.
  • the UE is moved out of the sleep state by using a paging message, where the UE receives the data packet under the connection bar.
  • Step 601 The RAN-UP entity receives the downlink data packet of the CN user plane.
  • Step 602 The RAN-UP entity determines, according to the data packet size, that the data packet is greater than a certain length, and may not be sent in the UE sleep state.
  • Step 603 The RAN-UP entity encapsulates an Xn interface message between the RAN-CP entities, where the message includes, but is not limited to, indicating that the RAN-CP entity has a reachable data packet. The message is then sent to the RAN-CP entity.
  • Step 604 The RAN-CP entity receives the message sent by the RAN-UP entity through the Xn interface, and the encapsulated paging message is sent to the UE, indicating that the UE needs to move out of the sleep state.
  • Step 605 The UE receives the paging message in the dormant state, and initiates the request to move out of the dormant state.
  • Step 606 The UE moves out of the sleep state, and starts the data packet transmission after entering the connection state.
  • FIG. 7 is a schematic structural diagram of a RAN-UP entity according to an embodiment of the present invention.
  • the RAN-UP entity includes:
  • the first receiving unit 71 is configured to receive a data packet sent by the core network
  • the first sending unit 72 is configured to send the data packet or control message to the RAN control plane RAN-CP entity.
  • the first receiving unit 71 is configured to receive a data packet sent by the core network through the first interface.
  • the first sending unit 72 is configured to send the data packet or control message to the RAN control plane RAN-CP entity through the second interface; wherein the control message is a data arrival indication or a paging indication.
  • the RAN-UP entity further includes: a first processing unit 73, configured to: when the data packet is sent to the RAN-CP entity by using the second interface, the service identifier information is carried in the interface message corresponding to the second interface; Or the data packet and the service identifier information are encoded into a data stream and sent to the RAN-CP entity, where the service identifier information is at least one of a service logical channel ID and a service bearer ID of the data packet.
  • the implementation functions of the entities in the RAN-UP entity shown in FIG. 7 can be understood by referring to the related description of the foregoing paging method.
  • the functions of the entities in the RAN-UP entity shown in FIG. 7 can be implemented by a program running on a processor, or can be implemented by a logic circuit.
  • FIG. 8 is a schematic structural diagram of a RAN-CP entity according to an embodiment of the present invention.
  • the RAN-CP entity includes:
  • the second receiving unit 81 is configured to receive a data packet or a control message sent by the RAN-UP entity;
  • the second sending unit 82 is configured to send the data packet to the UE in a paging message, where the paging message carries a first indication message, where the first indication message is used to indicate that the UE receives the And the paging message is kept in a dormant state, and the data packet is extracted from the paging message; or is configured to send a paging message to the UE; wherein the paging message carries a second And an indication message, where the second indication message is used to indicate that when receiving the paging message, the UE moves out of the dormant state to enter a connected state, and receives a data packet sent by the RAN-UP entity.
  • the second receiving unit 81 is configured to receive, by using the second interface, a data packet or a control message sent by the RAN-UP entity, where the control message is a data arrival indication or a paging indication.
  • the RAN-CP entity further includes: a second processing unit 83, configured to: when the data packet sent by the RAN-UP entity is received by the second interface, extract the service identifier information from the interface message corresponding to the second interface;
  • the second processing unit 83 is further configured to encapsulate the service identity information in the paging Sending to the UE in the message; or, the service identification information is integrated into the data packet and sent to the UE in an encoded form; or the data packet encoded by the RAN-UP entity and the data flow of the service identification information are encapsulated in the homing Send the message to the UE;
  • the service identification information is at least one of a service logical channel identifier ID and a service bearer ID of the data packet.
  • the implementation functions of the entities in the RAN-CP entity shown in FIG. 8 can be understood by referring to the related description of the foregoing paging method.
  • the functions of the entities in the RAN-CP entity shown in FIG. 8 can be implemented by a program running on a processor, or can be implemented by a logic circuit.
  • FIG. 9 is a schematic structural diagram of a UE according to an embodiment of the present invention.
  • the terminal includes:
  • the third receiving unit 91 is configured to receive a paging message sent by the RAN-CP entity
  • the first extracting unit 92 is configured to extract a first indication message from the paging message
  • the third processing unit 93 is configured to remain in a dormant state according to the indication of the first indication message, and extract a data packet from the paging message in a dormant state.
  • the terminal includes:
  • the fourth receiving unit 101 is configured to receive a paging message sent by the RAN-CP entity
  • the second extracting unit 102 is configured to extract a second indication message from the paging message
  • the fourth processing unit 103 is configured to move out of the dormant state to enter the connected state according to the indication of the second indication message, and receive the data packet sent by the RAN-UP entity in the connected state.
  • FIG. 9 and FIG. 10 can be understood by referring to the related description of the foregoing paging method.
  • the UEs shown in FIG. 9 and FIG. 10 may be the same UE, and the functions of each unit may be implemented by a program running on the processor, or may be implemented by a logic circuit.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the paging method.
  • the application can take the form of a hardware embodiment, a software embodiment, or an embodiment in combination with software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • paging and data transmission in a dormant state are implemented under the framework of separation between the 5G RAN control plane and the user plane.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本文公布一种寻呼方法、RAN-UP实体、RAN-CP实体及UE,包括:RAN-UP实体接收核心网发送的数据包,将数据包发送给RAN-CP实体。所述RAN-CP实体将所述数据包封装在寻呼消息中发送给UE;所述寻呼消息中携有第一指示消息,用于指示UE当接收到所述寻呼消息时,保持处于休眠态,并从所述寻呼消息中提取所述数据包。另一方面,RAN-UP实体接收核心网发送的数据包,将数据包达到指示或寻呼指示发送给RAN-CP实体。RAN-CP实体封装寻呼消息发送给UE;所述寻呼消息中携有第二指示消息,用于指示UE当接收到所述寻呼消息时,迁出休眠态进入连接态,并接收所述RAN-UP实体发送的数据包。

Description

寻呼方法、RAN-UP实体、RAN-CP实体及UE 技术领域
本申请涉及但不限于无线通信技术,尤指一种寻呼方法、RAN-UP(Residential Access Network User Plane,居民接入网用户面)实体、RAN-CP(Residential Access Network Control Plane,居民接入网控制面)实体及用户设备(UE,User Equipment)。
背景技术
蜂窝移动通信技术已经进入4G时代,但为了满足未来更高、更快、更新的通信需求,业界已经着手展开对5G技术的研究。5G将在更大的吞吐量、更多的用户连接、更低时延、更高可靠性、更低功耗方面进行进一步的技术研究。目前,业界提出了5G技术目标:到2020年左右,实现每区域1000倍的移动数据流量增长,每UE 10到100倍的吞吐量增长,连接设备数10到100倍的增长,低功率设备10倍的电池寿命延长,以及端到端5倍延迟的下降。
所以相对4G,5G研究提出了更高的性能要求,其中之一就是对控制面状态转换(从不发数据到可以传输数据)提出了10ms的指标要求,并在此基础上UE可以尽可能省电。因此,需要一种新的UE状态—休眠态。在休眠态下,UE和网络侧没有专用连接态资源,网络侧和核心网之间保持着UE级承载连接。由于5G终端的多样性,这种休眠态可以适用于手机、物联网器件等各类终端和业务,这些业务的优先等级以及数据包特性都会对休眠态提出新的需求。同时,随着居民接入网(RAN,Residential Access Network)软件定义网络(SDN,Software Defined Network)化的趋势,RAN的控制面和RAN的用户面也趋向于一种分离架构,这样RAN控制面锚点可以和RAN用户面锚点分离,从而实现一种SDN化的灵活部署架构。
发明概述
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种寻呼方法、RAN-UP实体、RAN-CP实体及UE,以实现休眠态的寻呼操作。
本发明实施例提供的寻呼方法,应用于RAN用户面(RAN-UP)实体;所述方法包括:
RAN-UP实体接收核心网发送的数据包;
所述RAN-UP实体将所述数据包或控制消息发送给RAN控制面(RAN-CP)实体。
本发明实施例中,所述RAN-UP实体接收核心网发送的数据包,包括:
RAN-UP实体通过第一接口接收核心网发送的数据包。
本发明实施例中,所述第一接口为S1或者S1-U。
本发明实施例中,所述RAN-UP实体将所述数据包或控制消息发送给RAN控制面RAN-CP实体,包括:
所述RAN-UP实体通过第二接口将所述数据包或控制消息发送给RAN控制面RAN-CP实体;其中所述控制消息为数据到达指示或者寻呼指示。
本发明实施例中,所述第二接口为Xn口,n是整数。
本发明实施例中,所述方法还包括:
所述RAN-UP实体通过第二接口将所述数据包发送给RAN-CP实体时,在所述第二接口对应的接口消息中携带业务标识信息;或者,将所述数据包,以及业务标识信息打包编码成数据流发送给RAN-CP实体;其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
本发明另一实施例提供的寻呼方法,应用于RAN-CP实体;所述方法包括:
RAN-CP实体接收RAN-UP实体发送的数据包,所述RAN-CP实体将所 述数据包封装在寻呼消息中发送给UE;其中,所述寻呼消息中携有第一指示消息,所述第一指示消息用于指示UE当接收到所述寻呼消息时,保持处于休眠态,并从所述寻呼消息中提取所述数据包;或者,
RAN-CP实体接收RAN-UP实体发送的控制消息,所述RAN-CP实体封装寻呼消息发送给UE;其中,所述寻呼消息中携有第二指示消息,所述第二指示消息用于指示UE当接收到所述寻呼消息时,迁出休眠态进入连接态,并接收所述RAN-UP实体发送的数据包。
本发明实施例中,所述RAN-CP实体接收RAN-UP实体发送的数据包或控制消息,包括:
RAN-CP实体通过第二接口接收RAN-UP实体发送的数据包或控制消息;其中所述控制消息为数据到达指示或者寻呼指示。
本发明实施例中,所述第二接口为Xn口,n是整数。
本发明实施例中,所述方法还包括:
RAN-CP实体通过第二接口接收到RAN-UP实体发送的数据包时,从所述第二接口对应的接口消息中提取业务标识信息;将所述业务标识信息封装在所述寻呼消息中发送给UE;或者,
将所述业务标识信息以编码形式整合在数据包中,并将数据包封装在寻呼消息中发送给UE;或者,将RAN-UP实体发送来的编码后的数据包以及业务标识信息的数据流封装在所述寻呼消息中发送给UE;
其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
本发明另一实施例提供的寻呼方法,应用于UE,所述方法包括:
UE处于休眠态时,接收RAN-CP实体发送的寻呼消息;
从所述寻呼消息中提取出第一指示消息;
根据所述第一指示消息的指示保持处于休眠态,并在休眠态下从所述寻呼消息中提取数据包。
本发明另一实施例提供的寻呼方法,应用于UE,所述方法包括:
UE处于休眠态时,接收RAN-CP实体发送的寻呼消息;
从所述寻呼消息中提取出第二指示消息;
根据所述第二指示消息的指示迁出休眠态进入连接态,并在连接态下接收RAN-UP实体发送的数据包。
本发明实施例提供的RAN-UP实体,包括:
第一接收单元,设置为接收核心网发送的数据包;
第一发送单元,设置为将所述数据包或者控制消息发送给RAN控制面RAN-CP实体。
本发明实施例中,所述第一接收单元,设置为通过第一接口接收核心网发送的数据包。
本发明实施例中,所述第一发送单元,设置为通过第二接口将所述数据包或者控制消息发送给RAN控制面RAN-CP实体;其中所述控制消息为数据到达指示或者寻呼指示。
本发明实施例中,所述RAN-UP实体还包括:第一处理单元,设置为通过第二接口将所述数据包发送给RAN-CP实体时,在所述第二接口对应的接口消息中携带业务标识信息;或者,将所述业务标识信息编码成数据流发送给RAN-CP实体;其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
本发明实施例提供的RAN-CP实体,包括:
第二接收单元,设置为接收RAN-UP实体发送的数据包或控制消息;
第二发送单元,设置为将所述数据包封装在寻呼消息中发送给UE;其中,所述寻呼消息中携有第一指示消息,所述第一指示消息用于指示UE当接收到所述寻呼消息时,保持处于休眠态,并从所述寻呼消息中提取所述数据包;或者,设置为封装寻呼消息发送给UE;其中,所述寻呼消息中携有第二指示消息,所述第二指示消息用于指示UE当接收到所述寻呼消息时,迁出休眠态进入连接态,并接收所述RAN-UP实体发送的数据包。
本发明实施例中,所述第二接收单元,设置为通过第二接口接收RAN-UP实体发送的数据包或者控制消息;其中所述控制消息为数据到达 指示或者寻呼指示。
本发明实施例中,所述RAN-CP实体还包括:第二处理单元,设置为通过第二接口接收到RAN-UP实体发送的数据包时,从所述第二接口对应的接口消息中提取业务标识信息;
所述第二处理单元,还设置为将所述业务标识信息封装在所述寻呼消息中发送给UE;或者,将所述业务标识信息以编码形式整合在数据包中发送给UE;或者,将RAN-UP实体编码后的数据包以及业务标识信息的数据流封装在所述寻呼消息中发送给UE;
其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
本发明实施例提供的UE处于休眠态,所述UE包括:
第三接收单元,设置为接收RAN-CP实体发送的寻呼消息;
第一提取单元,设置为从所述寻呼消息中提取出第一指示消息;
第三处理单元,设置为根据所述第一指示消息的指示保持处于休眠态,并在休眠态下从所述寻呼消息中提取数据包。
本发明实施例提供的UE处于休眠态,所述UE包括:
第四接收单元,设置为接收RAN-CP实体发送的寻呼消息;
第二提取单元,设置为从所述寻呼消息中提取出第二指示消息;
第四处理单元,设置为根据所述第二指示消息的指示迁出休眠态进入连接态,并在连接态下接收RAN-UP实体发送的数据包。
本发明实施例还提供的一种计算机可读存储介质,存储有计算机可执行指令,所述计算机可执行指令被处理器执行时实现上述寻呼方法。
本发明实施例的技术方案中,在一实施方式中,RAN-UP实体接收核心网发送的数据包;所述RAN-UP实体将所述数据包发送给RAN-CP实体。RAN-CP实体接收RAN-UP实体发送的数据包;所述RAN-CP实体将所述数据包封装在寻呼消息中发送给UE;其中,所述寻呼消息中携有第一指示消息,所述第一指示消息用于指示UE当接收到所述寻呼消息时,保持 处于休眠态,并从所述寻呼消息中提取所述数据包。在另一实施方式中,RAN-UP实体接收核心网发送的数据包;所述RAN-UP实体将数据包达到指示或寻呼指示发送给RAN-CP实体。RAN-CP实体接收RAN-UP实体发送的数据包达到指示或寻呼指示;所述RAN-CP实体封装寻呼消息发送给UE;其中,所述寻呼消息中携有第二指示消息,所述第二指示消息用于指示UE当接收到所述寻呼消息时,迁出休眠态进入连接态,并接收所述RAN-UP实体发送的数据包。如此,在5G RAN控制面和用户面分离的架构下,实现了休眠态下的寻呼以及数据传递。
在阅读并理解了附图和详细描述后,可以明白其他方面。
附图概述
在附图(其不一定是按比例绘制的)中,相似的附图标记可在不同的视图中描述相似的部件。具有不同字母后缀的相似附图标记可表示相似部件的不同示例。附图以示例而非限制的方式大体示出了本文中所讨论的各个实施例。
图1为本发明实施例的RAN-CP实体和RAN-UP实体架构示意图;
图2为本发明实施例一的寻呼方法的流程示意图;
图3为本发明实施例二的寻呼方法的流程示意图;
图4为本发明实施例应用场景一的流程图;
图5为本发明实施例应用场景二的流程图;
图6为本发明实施例应用场景三的流程图;
图7为本发明实施例的RAN-UP实体的结构组成示意图;
图8为本发明实施例的RAN-CP实体的结构组成示意图;
图9为本发明实施例的UE的结构组成示意图;
图10为本发明另一实施例的UE的结构组成示意图。
详述
为了能够更加详尽地了解本发明实施例的特点与技术内容,下面结合附图对本发明实施例的实现进行详细阐述,所附附图仅供参考说明之用,并非用来限定本发明实施例。
图1为本发明实施例的RAN-CP实体和RAN-UP实体架构示意图,如图1所示,5G的RAN-CP实体和RAN-UP实体分离后,当UE处于休眠态,核心网下行数据包通过S1-U到达RAN-UP实体,RAN-UP实体收到数据包后,可选的执行两个过程:
过程1:RAN-UP实体将数据包通过Xn接口消息传递给RAN-CP实体,在一实施方式中,Xn接口消息中可以携带但不限于该数据包所在业务逻辑信道ID或业务所属承载ID。
RAN-CP实体收到RAN-UP实体通过Xn接口发来的消息,提取消息中的数据包,在一实施方式中,可提取消息中该数据包所在业务逻辑信道ID或业务所属承载ID;然后,将数据包(在一实施方式中,还将数据包所在业务逻辑信道ID或业务所属承载ID)封装在寻呼消息中传递给UE,寻呼消息中指示UE不用迁移出休眠态。
UE接收寻呼消息中的数据包,但UE不用迁移休眠态。
过程2:RAN-UP实体通过Xn接口消息通知RAN-CP实体有数据包到达,Xn接口消息中指示有数据包到达。
RAN-CP实体接收RAN-UP实体通过Xn接口发来的消息后,封装寻呼消息发给UE;寻呼消息中指示UE迁出休眠态。
UE接收到寻呼消息,UE发起流程迁出休眠态而进入连接态,UE在连接态下接收RAN-UP实体发送的下行数据包。
本发明实施例的技术方案在RAN-CP实体和RAN-UP实体分离的模式下,根据业务属性,支持UE休眠态的数据接收以及状态唤醒迁出的数据传输。
图2为本发明实施例一的寻呼方法的流程示意图,如图2所示,所述方法包括以下步骤:
步骤201:RAN-UP实体接收核心网发送的数据包。
这里,RAN-UP实体通过S1-U接口接收核心网发送的数据包。
步骤202:所述RAN-UP实体将所述数据包发送给RAN-CP实体。
这里,所述RAN-UP实体通过Xn接口将所述数据包发送给RAN控制面RAN-CP实体。
在一实施方式中,所述RAN-UP实体通过Xn接口将所述数据包发送给RAN-CP实体时,在所述Xn接口对应的接口消息中携带业务标识信息;或者,
将所述数据包,以及业务标识信息打包编码成数据流发送给RAN-CP实体;
其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
步骤203:RAN-CP实体接收RAN-UP实体发送的数据包。
这里,RAN-CP实体通过Xn接口接收RAN-UP实体发送的数据包。
步骤204:所述RAN-CP实体将所述数据包封装在寻呼消息中发送给UE;其中,所述寻呼消息中携有第一指示消息。
所述第一指示消息用于指示UE当接收到所述寻呼消息时,保持处于休眠态,并从所述寻呼消息中提取所述数据包。
本发明实施例中,RAN-CP实体通过第二接口接收到RAN-UP实体发送的数据包时,从所述第二接口对应的接口消息中提取所述业务标识信息;将所述业务标识信息封装在所述寻呼消息中发送给UE;或者,
将所述业务标识信息以编码形式整合在数据包中,并将数据包封装在寻呼消息中发送给UE;或者,
将RAN-UP实体发送来的编码后的数据包以及业务标识信息的数据流封装在所述寻呼消息中发送给UE。
步骤205:UE处于休眠态时,接收RAN-CP实体发送的寻呼消息。
步骤206:UE从所述寻呼消息中提取出第一指示消息。
步骤207:UE根据所述第一指示消息的指示保持处于休眠态,并在休 眠态下从所述寻呼消息中提取数据包。
图3为本发明实施例二的寻呼方法的流程示意图,如图3所示,所述方法包括以下步骤:
步骤301:RAN-UP实体接收核心网发送的数据包。
这里,所述RAN-UP实体将数据包达到指示或寻呼指示发送给RAN-CP实体。
步骤302:所述RAN-UP实体将数据包达到指示或寻呼指示发送给RAN-CP实体。
这里,所述RAN-UP实体通过Xn接口将数据包达到指示或寻呼指示发送给RAN-CP实体。
步骤303:RAN-CP实体接收RAN-UP实体发送的数据包达到指示或寻呼指示。
这里,RAN-CP实体通过Xn接口接收RAN-UP实体发送的数据包达到指示或寻呼指示。
步骤304:所述RAN-CP实体封装寻呼消息发送给UE;其中,所述寻呼消息中携有第二指示消息。
这里,所述第二指示消息用于指示UE当接收到所述寻呼消息时,迁出休眠态进入连接态,并接收所述RAN-UP实体发送的数据包。
步骤305:UE处于休眠态时,接收RAN-CP实体发送的寻呼消息。
步骤306:UE从所述寻呼消息中提取出第二指示消息。
步骤307:UE根据所述第二指示消息的指示迁出休眠态进入连接态,并在连接态下接收RAN-UP实体发送的数据包。
下面结合应用场景对本发明实施例的寻呼方法做进一步解释说明。
应用场景一
根据数据包业务和大小特性,通过寻呼消息将数据包携带给UE,其中,UE在休眠态下接收数据包。参照图4:
步骤401:RAN-UP实体收到核心网(CN,Core Network)用户面的下 行数据包。
步骤402:RAN-UP实体根据数据包所在业务承载或者数据包头信息,判定可以在UE休眠态下发送。
其中,所述包头信息包括但不限于服务质量(QoS,Quality of Service)等级。
步骤403:RAN-UP实体判定出据包长小于一定门限。
步骤404:RAN-UP实体将数据包封装到和RAN-CP实体之间的Xn接口消息中,消息中可以添加但不限于数据包所在业务承载ID或逻辑信道ID等。然后RAN-UP实体将消息发送给RAN-CP实体。
步骤405:RAN-CP实体接收到RAN-UP实体通过Xn接口发送过来的消息,提取该消息中的数据包和消息信元。
步骤406:RAN-CP实体将数据包封装入寻呼消息。这里,可以在寻呼消息中添加但不限于数据包所在业务承载ID或逻辑信道ID,寻呼消息中指示UE不需要迁出休眠态并接收寻呼中的数据包。
步骤407:RAN-CP实体将寻呼消息发送给UE。
步骤408:UE在休眠态下接收到寻呼消息,保持休眠态,并且接收寻呼消息中的数据包,并根据但不限于数据包中RAN-UP实体封装的业务承载ID,逻辑信道ID等信息将数据包递交到相应的业务会话中。
应用场景二
根据数据包业务特性,通过寻呼消息将UE迁出休眠态再接收数据包。参照图5:
步骤501:RAN-UP实体收到CN用户面的下行数据包。
步骤502:RAN-UP实体根据数据包所在业务承载或者数据包头信息,判定不可以在UE休眠态下发送。
这里,所述包头信息包括但不限于QoS等级。
步骤503:RAN-UP实体封装一个RAN-CP实体之间的Xn接口消息, 消息中包含但不限于指示RAN-CP实体有可接收的数据包到达。然后将消息发送给RAN-CP实体。
步骤504:RAN-CP实体接收到RAN-UP实体通过Xn接口发送过来的消息,封装寻呼消息发送给UE,指示UE需要迁出休眠态。
步骤505:UE在休眠态下接收到寻呼消息,发起请求迁出休眠态。
步骤506:UE迁出休眠态,进入连接状态后开始数据包传输。
应用场景三
根据数据包大小特性,通过寻呼消息将UE迁出休眠态,其中,UE在连接条下接收数据包。参照图6:
步骤601:RAN-UP实体收到CN用户面的下行数据包。
步骤602:RAN-UP实体根据数据包大小,判定出数据包大于一定长度,不可以在UE休眠态下发送。
步骤603:RAN-UP实体封装一个RAN-CP实体之间的Xn接口消息,消息中包含但不限于指示RAN-CP实体有可以接收的数据包到达。然后将消息发送给RAN-CP实体。
步骤604:RAN-CP实体接收到RAN-UP实体通过Xn接口发送过来的消息,封装寻呼消息发送给UE,指示UE需要迁出休眠态。
步骤605:UE在休眠态下接收到寻呼消息,发起请求迁出休眠态。
步骤606:UE迁出休眠态,进入连接状态后开始数据包传输。
图7为本发明实施例的RAN-UP实体的结构组成示意图;所述RAN-UP实体包括:
第一接收单元71,设置为接收核心网发送的数据包;
第一发送单元72,设置为将所述数据包或者控制消息发送给RAN控制面RAN-CP实体。
所述第一接收单元71,设置为通过第一接口接收核心网发送的数据包。
所述第一发送单元72,设置为通过第二接口将所述数据包或者控制消息发送给RAN控制面RAN-CP实体;其中所述控制消息为数据到达指示或者寻呼指示。
所述RAN-UP实体还包括:第一处理单元73,设置为通过第二接口将所述数据包发送给RAN-CP实体时,在所述第二接口对应的接口消息中携带业务标识信息;或者,将所述数据包,以及业务标识信息编码成数据流发送给RAN-CP实体;其中,所述业务标识信息为所述数据包所在业务逻辑信道ID和业务所属承载ID中至少之一。
本领域技术人员应当理解,图7所示的RAN-UP实体中的各实体的实现功能可参照前述寻呼方法的相关描述而理解。图7所示的RAN-UP实体中的各实体的功能可通过运行于处理器上的程序而实现,也可通过逻辑电路而实现。
图8为本发明实施例的RAN-CP实体的结构组成示意图;所述RAN-CP实体包括:
第二接收单元81,设置为接收RAN-UP实体发送的数据包或控制消息;
第二发送单元82,设置为所述数据包封装在寻呼消息中发送给UE;其中,所述寻呼消息中携有第一指示消息,所述第一指示消息用于指示UE当接收到所述寻呼消息时,保持处于休眠态,并从所述寻呼消息中提取所述数据包;或者,设置为封装寻呼消息发送给UE;其中,所述寻呼消息中携有第二指示消息,所述第二指示消息用于指示UE当接收到所述寻呼消息时,迁出休眠态进入连接态,并接收所述RAN-UP实体发送的数据包。
所述第二接收单元81,置为通过第二接口接收RAN-UP实体发送的数据包或者控制消息;其中所述控制消息为数据到达指示或者寻呼指示。
所述RAN-CP实体还包括:第二处理单元83,设置为通过第二接口接收到RAN-UP实体发送的数据包时,从所述第二接口对应的接口消息中提取业务标识信息;
所述第二处理单元83,还设置为将所述业务标识信息封装在所述寻呼 消息中发送给UE;或者,将所述业务标识信息以编码形式整合在数据包中发送给UE;或者,将RAN-UP实体编码后的数据包以及业务标识信息的数据流封装在所述寻呼消息中发送给UE;
其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
本领域技术人员应当理解,图8所示的RAN-CP实体中的各实体的实现功能可参照前述寻呼方法的相关描述而理解。图8所示的RAN-CP实体中的各实体的功能可通过运行于处理器上的程序而实现,也可通过逻辑电路而实现。
图9为本发明实施例的UE的结构组成示意图。
在本发明实施例中,所述终端包括:
第三接收单元91,设置为接收RAN-CP实体发送的寻呼消息;
第一提取单元92,设置为从所述寻呼消息中提取出第一指示消息;
第三处理单元93,设置为根据所述第一指示消息的指示保持处于休眠态,并在休眠态下从所述寻呼消息中提取数据包。
如图10所示,在本发明另一实施例中,所述终端包括:
第四接收单元101,设置为接收RAN-CP实体发送的寻呼消息;
第二提取单元102,设置为从所述寻呼消息中提取出第二指示消息;
第四处理单元103,设置为根据所述第二指示消息的指示迁出休眠态进入连接态,并在连接态下接收RAN-UP实体发送的数据包。
本领域技术人员应当理解,图9和图10所示的UE中的各单元的实现功能可参照前述寻呼方法的相关描述而理解。图9和图10所示的UE可以是同一个UE,其中的各单元的功能可通过运行于处理器上的程序而实现,也可通过逻辑电路而实现。
本发明实施例还提供的一种计算机可读存储介质,存储有计算机可执行指令,所述计算机可执行指令被处理器执行时实现上述寻呼方法。
本领域内的技术人员应明白,本发明的实施例可提供为方法、系统、 或计算机程序产品。因此,本申请可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述,仅为本发明的实施例而已,并非用于限定本申请的保护范围。
工业实用性
通过本发明实施例,在5G RAN控制面和用户面分离的架构下,实现了休眠态下的寻呼以及数据传递。

Claims (21)

  1. 一种寻呼方法,应用于RAN用户面RAN-UP实体;所述方法包括:
    RAN-UP实体接收核心网发送的数据包;
    所述RAN-UP实体将所述数据包或控制消息发送给RAN控制面RAN-CP实体。
  2. 根据权利要求1所述的寻呼方法,其中,所述RAN-UP实体接收核心网发送的数据包,包括:
    RAN-UP实体通过第一接口接收核心网发送的数据包。
  3. 根据权利要求2所述的寻呼方法,其中,所述第一接口为S1或者S1-U。
  4. 根据权利要求1所述的寻呼方法,其中,所述RAN-UP实体将所述数据包或控制消息发送给RAN控制面RAN-CP实体,包括:
    所述RAN-UP实体通过第二接口将所述数据包或控制消息发送给RAN控制面RAN-CP实体;其中所述控制消息为数据到达指示或者寻呼指示。
  5. 根据权利要求4所述的寻呼方法,其中,所述第二接口为Xn口,n是整数。
  6. 根据权利要求4所述的寻呼方法,所述方法还包括:
    所述RAN-UP实体通过第二接口将所述数据包发送给RAN-CP实体时,在所述第二接口对应的接口消息中携带业务标识信息;或者,将所述数据包,以及所述业务标识信息打包编码成数据流发送给RAN-CP实体;其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
  7. 一种寻呼方法,应用于RAN-CP实体;所述方法包括:
    RAN-CP实体接收RAN-UP实体发送的数据包,所述RAN-CP实体将所述数据包封装在寻呼消息中发送给UE;其中,所述寻呼消息中携有第一指示消息,所述第一指示消息用于指示UE当接收到所述寻呼消息时,保持处于休眠态,并从所述寻呼消息中提取所述数据包;或者,
    RAN-CP实体接收RAN-UP实体发送的控制消息,所述RAN-CP实体封装寻呼消息发送给UE;其中,所述寻呼消息中携有第二指示消息,所述第二指示消息用于指示UE当接收到所述寻呼消息时,迁出休眠态进入连接态,并接收所述RAN-UP实体发送的数据包。
  8. 根据权利要求7所述的寻呼方法,其中,所述RAN-CP实体接收RAN-UP实体发送的数据包或控制消息,包括:
    RAN-CP实体通过第二接口接收RAN-UP实体发送的数据包或控制消息;其中所述控制消息为数据到达指示或者寻呼指示。
  9. 根据权利要求8所述的寻呼方法,其中,所述第二接口为Xn口,n是整数。
  10. 根据权利要求8所述的寻呼方法,所述方法还包括:
    RAN-CP实体通过第二接口接收到RAN-UP实体发送的数据包时,从所述第二接口对应的接口消息中提取业务标识信息;将所述业务标识信息封装在所述寻呼消息中发送给UE;或者,
    将所述业务标识信息以编码形式整合在数据包中,并将数据包封装在寻呼消息中发送给UE;或者,
    将RAN-UP实体发送来的编码后的数据包以及业务标识信息的数据流封装在所述寻呼消息中发送给UE;
    其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
  11. 一种寻呼方法,应用于UE,所述方法包括:
    UE处于休眠态时,接收RAN-CP实体发送的寻呼消息;
    从所述寻呼消息中提取出第一指示消息;
    根据所述第一指示消息的指示保持处于休眠态,并在休眠态下从所述寻呼消息中提取数据包。
  12. 一种寻呼方法,应用于UE,所述方法包括:
    UE处于休眠态时,接收RAN-CP实体发送的寻呼消息;
    从所述寻呼消息中提取出第二指示消息;
    根据所述第二指示消息的指示迁出休眠态进入连接态,并在连接态下接收RAN-UP实体发送的数据包。
  13. 一种RAN-UP实体,所述RAN-UP实体包括:
    第一接收单元,设置为接收核心网发送的数据包;
    第一发送单元,设置为将所述数据包或者控制消息发送给RAN控制面RAN-CP实体。
  14. 根据权利要求13所述的RAN-UP实体,其中,所述第一接收单元,设置为通过第一接口接收核心网发送的数据包。
  15. 根据权利要求13所述的RAN-UP实体,其中,所述第一发送单元,设置为通过第二接口将所述数据包或者控制消息发送给RAN控制面RAN-CP实体;其中所述控制消息为数据到达指示或者寻呼指示。
  16. 根据权利要求15所述的RAN-UP实体,其中,所述RAN-UP实体还包括:第一处理单元,设置为通过第二接口将所述数据包发送给RAN-CP实体时,在所述第二接口对应的接口消息中携带业务标识信息;或者,将所述数据包,以及业务标识信息编码成数据流发送给RAN-CP实体;其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
  17. 一种RAN-CP实体,所述RAN-CP实体包括:
    第二接收单元,设置为接收RAN-UP实体发送的数据包或控制消息;
    第二发送单元,设置为将所述数据包封装在寻呼消息中发送给UE;其中,所述寻呼消息中携有第一指示消息,所述第一指示消息用于指示UE当接收到所述寻呼消息时,保持处于休眠态,并从所述寻呼消息中提取所述数据包;或者,设置为封装寻呼消息发送给UE;其中,所述寻呼消息中携有第二指示消息,所述第二指示消息用于指示UE当接收到所述寻呼消息时,迁出休眠态进入连接态,并接收所述RAN-UP实体发送的数据包。
  18. 根据权利要求17所述的RAN-CP实体,所述第二接收单元,设置为通过第二接口接收RAN-UP实体发送的数据包或者控制消息;其中所述 控制消息为数据到达指示或者寻呼指示。
  19. 根据权利要求18所述的RAN-CP实体,所述RAN-CP实体还包括:第二处理单元,设置为通过第二接口接收到RAN-UP实体发送的数据包时,从所述第二接口对应的接口消息中提取业务标识信息;
    所述第二处理单元,还设置为将所述业务标识信息封装在所述寻呼消息中发送给UE;或者,将所述业务标识信息以编码形式整合在数据包中发送给UE;或者,将RAN-UP实体编码后的数据包以及业务标识信息的数据流封装在所述寻呼消息中发送给UE;
    其中,所述业务标识信息为所述数据包所在业务逻辑信道标识ID和业务所属承载ID中至少之一。
  20. 一种UE,所述UE处于休眠态,所述UE包括:
    第三接收单元,设置为接收RAN-CP实体发送的寻呼消息;
    第一提取单元,设置为从所述寻呼消息中提取出第一指示消息;
    第三处理单元,设置为根据所述第一指示消息的指示保持处于休眠态,并在休眠态下从所述寻呼消息中提取数据包。
  21. 一种UE,所述UE处于休眠态,所述UE包括:
    第四接收单元,设置为接收RAN-CP实体发送的寻呼消息;
    第二提取单元,设置为从所述寻呼消息中提取出第二指示消息;
    第四处理单元,设置为根据所述第二指示消息的指示迁出休眠态进入连接态,并在连接态下接收RAN-UP实体发送的数据包。
PCT/CN2017/089367 2016-06-28 2017-06-21 寻呼方法、ran-up实体、ran-cp实体及ue WO2018001151A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17819148.2A EP3477975B1 (en) 2016-06-28 2017-06-21 Paging method, ran-up entity, ran-cp entity, and ue
US16/232,972 US10966176B2 (en) 2016-06-28 2018-12-26 Paging method, RAN-UP entity, RAN-CP entity and UE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610485952.6 2016-06-28
CN201610485952.6A CN107548153B (zh) 2016-06-28 2016-06-28 寻呼方法、ran-up实体、ran-cp实体及ue

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/232,972 Continuation US10966176B2 (en) 2016-06-28 2018-12-26 Paging method, RAN-UP entity, RAN-CP entity and UE

Publications (1)

Publication Number Publication Date
WO2018001151A1 true WO2018001151A1 (zh) 2018-01-04

Family

ID=60785920

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/089367 WO2018001151A1 (zh) 2016-06-28 2017-06-21 寻呼方法、ran-up实体、ran-cp实体及ue

Country Status (4)

Country Link
US (1) US10966176B2 (zh)
EP (1) EP3477975B1 (zh)
CN (1) CN107548153B (zh)
WO (1) WO2018001151A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020197454A1 (en) * 2019-03-28 2020-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Paging of idle state wireless communication devices
CN116648965A (zh) * 2020-11-04 2023-08-25 Oppo广东移动通信有限公司 一种rrc状态转换的方法及装置、终端设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324857B (zh) * 2018-03-28 2021-03-16 中国移动通信有限公司研究院 一种业务质量数据流的处理方法和装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101115292A (zh) * 2006-07-27 2008-01-30 华为技术有限公司 寻呼并连接终端的方法及快速激活数据传输的终端和系统
US8467681B2 (en) * 2009-10-06 2013-06-18 Futurewei Technologies, Inc. Method for characterizing wavelength switched optical network signal characteristics and network element compatibility constraints for generalized multi-protocol label switching

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101573997B (zh) * 2006-12-29 2013-05-29 艾利森电话股份有限公司 用于库配置的服务器和网关信息的自动分发
CN101242645B (zh) * 2007-02-09 2011-02-09 华为技术有限公司 移动终端从空闲态进入激活态的方法及系统
CN103945535B (zh) * 2013-01-18 2018-07-10 中兴通讯股份有限公司 寻呼优化的方法、装置、系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101115292A (zh) * 2006-07-27 2008-01-30 华为技术有限公司 寻呼并连接终端的方法及快速激活数据传输的终端和系统
US8467681B2 (en) * 2009-10-06 2013-06-18 Futurewei Technologies, Inc. Method for characterizing wavelength switched optical network signal characteristics and network element compatibility constraints for generalized multi-protocol label switching

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "On RAN Initiated Paging", 3GPP TSG-RAN WG2 MEETING #94, R2-163932, 23 May 2016 (2016-05-23), XP051095318 *
MEDIATEK INC.: "NB-IOT-Remaining Issues on Idle-Mode Procedures and Paging", 3GPPTSG RANWG2 MEETING #93BIS, R2-162882, 11 April 2016 (2016-04-11), XP051082614 *
NOKIA ET AL.: "Paging for Light Connection", GPP TSG-RAN WG3 MEETING #92, R3-161352, 23 May 2016 (2016-05-23), XP051094703 *
YANG XUYAN ET AL.: "Discussion on 5G Network Architecture", WIRELESS INTERNET TECHNOLOGY, no. 6, 31 March 2016 (2016-03-31), XP009518227, ISSN: 1672-6944 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020197454A1 (en) * 2019-03-28 2020-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Paging of idle state wireless communication devices
CN116648965A (zh) * 2020-11-04 2023-08-25 Oppo广东移动通信有限公司 一种rrc状态转换的方法及装置、终端设备

Also Published As

Publication number Publication date
CN107548153A (zh) 2018-01-05
EP3477975A1 (en) 2019-05-01
EP3477975A4 (en) 2019-11-27
CN107548153B (zh) 2020-09-18
EP3477975B1 (en) 2021-05-12
US10966176B2 (en) 2021-03-30
US20190246372A1 (en) 2019-08-08

Similar Documents

Publication Publication Date Title
WO2019232732A1 (zh) 一种寻呼消息传输方法和相关设备
WO2017194006A1 (zh) Rrc状态的控制方法和装置
US11240640B2 (en) Multicast bearer management method and terminal device
US11363528B2 (en) Method and apparatus for reducing signaling overhead and reducing battery of terminal
CN112514522B (zh) 用于恢复时挂起不活动和挂起时恢复不活动的方法
EP3500012B1 (en) Communication device, communication method, and program
TWI704830B (zh) 用於無線通訊中的分離承載預處理的緩衝器狀態報告方法和裝置
WO2022075912A1 (en) Group pdcp discard timer for low-latency services
US10057937B2 (en) Communications via multiple access points
EP2687044A1 (en) Mobile communications network and method
US20140274011A1 (en) Method and apparatus for controlling operation of a user equipment based on physical layer parameters
CN113923712A (zh) 数据处理的方法及装置
WO2018001151A1 (zh) 寻呼方法、ran-up实体、ran-cp实体及ue
EP4175356A1 (en) Wireless communication method, terminal device, and network device
US10973080B2 (en) Radio terminal, processor, and base station
CN115804201A (zh) 集中式单元和分布式单元分离架构中的数据转发
WO2014068464A2 (en) Method and apparatus for packet tunneling
JP2022539694A (ja) ダウンリンク制御チャネルのモニタリングに関するユーザ装置
CN106961726B (zh) 一种数据传输方法、装置及系统
CN108617000B (zh) 信息传输方法及装置
WO2017032197A1 (zh) 一种通信控制方法及装置
WO2023040445A1 (zh) 无线通信系统中的电子设备和方法
WO2022223031A1 (zh) 一种数据传输的通信处理方法和相关设备
WO2017011941A1 (zh) 上行数据包的传输方法、终端设备、基站及通信系统
EP4154446A1 (en) Method and apparatus for signaling suspension and resumption of network coding operation

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017819148

Country of ref document: EP

Effective date: 20190128