WO2019137434A1 - 一种通信方法，设备及其系统 - Google Patents

一种通信方法，设备及其系统 Download PDF

Info

Publication number
WO2019137434A1
WO2019137434A1 PCT/CN2019/071162 CN2019071162W WO2019137434A1 WO 2019137434 A1 WO2019137434 A1 WO 2019137434A1 CN 2019071162 W CN2019071162 W CN 2019071162W WO 2019137434 A1 WO2019137434 A1 WO 2019137434A1
Authority
WO
WIPO (PCT)
Prior art keywords
paging
indication information
page
terminal device
originating
Prior art date
Application number
PCT/CN2019/071162
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 JP2020538569A priority Critical patent/JP7106653B2/ja
Priority to AU2019207029A priority patent/AU2019207029B2/en
Priority to RU2020126718A priority patent/RU2778144C2/ru
Priority to KR1020207022800A priority patent/KR20200105512A/ko
Priority to CA3088224A priority patent/CA3088224A1/en
Priority to EP19739080.0A priority patent/EP3737172B1/en
Priority to BR112020014067-8A priority patent/BR112020014067A2/pt
Publication of WO2019137434A1 publication Critical patent/WO2019137434A1/zh
Priority to US16/925,817 priority patent/US11722987B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • 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
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier
    • 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/08—User notification, e.g. alerting and paging, for incoming communication, change of service or the like using multi-step notification by increasing the notification area
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present application relates to the field of communications, and more specifically to a communication method, device, system thereof and the like.
  • the base station In a next-generation mobile communication system, such as the 5th generation mobile communication technology (5G) system, the base station is called a gNB or an ng-eNB, wherein the ng-eNB is derived from long term evolution (long term)
  • the evolved, LTE) base station (LTE eNB) subsequent evolved base station for convenience of description, the gNB is used herein to represent the base station.
  • the system 100 shown in FIG. 1 is a schematic block diagram of a 5G system in which ng-eNB and ng-eNB are between gNB and gNB in a next generation radio access network (NG-RAN). Between, and between the gNB and the ng-eNB are interconnected through the Xn interface.
  • NG-RAN next generation radio access network
  • the gNB and the 5G core network (5G core, 5GC) devices are interconnected through the NG interface, and the ng-eNB and the 5GC device are interconnected through the NG interface.
  • the 5GC device may be an access and mobility management function (AMF) or a user plane function (UPF).
  • AMF access and mobility management function
  • UPF user plane function
  • the AMF is mainly responsible for access management functions
  • the UPF is mainly responsible for the session ( Session) management aspects.
  • the base station usually includes a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, and a radio link control ( A radio link control (RLC) layer, a media access control (MAC) layer, and a logical layer (PHY) layer such as a physical layer (PHY).
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC media access control
  • PHY logical layer
  • Next generation base stations e.g., gNBs
  • 2 is a schematic block diagram of a 5G system including a 5GC and an NG-RAN.
  • the base station gNB can be a centralized unit (CU) and a distributed unit (DU).
  • the CU and DU architecture can be understood as splitting the functions of the base stations in the traditional access network.
  • Some functions of the traditional base station are deployed in the CU, and other functions are deployed in the DU. Multiple DUs can share one CU to save costs. It is easy to expand the network, and the information exchange between the CU and the DU through the F1 interface.
  • a gNB composed of a CU and a DU, it is a base station for other external network elements.
  • the centralized unit CU can also be divided into a CU control plane (CU-CP) and a CU user plane (CU user plane, CU).
  • CU-CP CU control plane
  • CU user plane CU user plane
  • -CP CU control plane
  • the CU-CP is responsible for the control plane function, mainly including the RRC and PDCP control plane parts (PDCP-C).
  • PDCP-C is mainly responsible for the encryption and decryption of the control plane data, integrity protection, and data transmission; the CU-UP is responsible for the user.
  • the surface function mainly includes SDAP and PDCP-U.
  • the SDAP is mainly responsible for processing the data of the core network and mapping the flow to the radio bearer.
  • the PDCP-U is mainly responsible for encryption and decryption of the data plane, integrity protection, and header compression. , serial number maintenance, and data transfer.
  • the CU-CP and the CU-UP are connected through the E1 interface, the CU-CP represents the gNB connected to the core network through the Ng interface, the CU-CP is connected to the DU through the F1-C (F1 control plane) interface, and the CU-UP passes the F1- U (F1 user plane) interface and DU connection.
  • F1-C F1 control plane
  • the CU-UP passes the F1- U (F1 user plane) interface and DU connection.
  • Yet another design is that both PDCP-C and PDCP-C are at CU-UP and RRC is at CU-CP (not shown in Figure 3).
  • the current paging procedure for the UE is not perfect, which may cause the paging UE to fail;
  • the CU When the UE enters the inactive state, the CU notifies the DU to release the UE context of the UE, but the mechanism still has a defect;
  • the present application provides a communication method, a device, a system, and the like, to solve the problem that a paging procedure for a terminal device existing in a CU-DU based base station architecture or a derivative architecture thereof is not perfect, and may cause a paging UE failure.
  • an embodiment of the present application provides a communication method, where the communication method runs in a communication system, where the communication system includes a centralized unit and a distributed unit.
  • the communication system includes a centralized unit and a distributed unit.
  • the centralized unit CU sends a paging message to the distributed unit DU, where the paging message carries indication information indicating that the paging is based on a page generated by the core network or a paging generated based on the radio access network; the distributed unit Upon receiving the paging message, the indication information carried in the pageable message is learned that the paging is based on a page generated by the core network or the paging is based on a paging generated by the radio access network.
  • the DU can be informed whether the received paging message is from the core network or from the RAN side (such as a page generated by the CU), so that the paging can be correctly broadcasted in the air interface.
  • An optional design according to the first aspect includes: the indication information is information derived from the identity of the paged terminal device of the core network, and the indication information is used to indicate that the page is based on a page generated by the core network And being used to cause the distributed unit to know that the page is based on a page generated by the core network; or, the indication information is information of an identifier of a paged terminal device configured by the radio access network, then the indication Information is used to indicate that the page is based on a page generated by the radio access network and is used to cause the distributed unit to know that the page is based on a page generated by the radio access network.
  • the paging is based on the core network generated by the information of the identifier of the paged terminal device originating from the core network carried in the paging message transmitted on the interface between the CU and the DU.
  • the information of the identifier of the paged terminal device (or other information capable of identifying the terminal) configured by the radio access network side carried in the paging message transmitted on the interface between the CU and the DU may be represented.
  • the page is based on a page generated by the radio access network.
  • An optional design according to the first aspect comprises: the paging message further comprising information of the identity of the paged terminal device, or information capable of identifying the paged terminal device.
  • the indication information carried in the paging message may be used to indicate or indicate that the paging involved is based on a page generated by the core network or the paging is based on a paging generated by the radio access network, and the distributed unit receives the After the indication information, it can be known that the paging involved is based on the paging generated by the core network or the paging involved is based on the paging generated by the radio access network, for example, if the indication information indicates or indicates the homing The paging is based on the paging generated by the core network, and the distributed unit may learn, according to the indication information, that the paging involved is based on a page generated by the core network; or if the indication information indicates or indicates the seeking The call is based on the paging generated by the radio access network, and after receiving the indication information
  • An optional design according to the first aspect includes: the paging message includes information of the identity of the paged terminal device; the indication information indicates that the page is generated based on a page generated by the core network or based on a wireless access network Paging, the indication information is used to enable the distributed unit to learn that the paging is based on a page generated by the core network or the paging is based on a paging generated by the radio access network, including: the indication information indicates that the paging is The information indicating the identity of the paging terminal device is originated from the core network, and the indication information indicates that the paging is based on the paging generated by the core network, and is used to enable the distributed unit to learn that the paging is based on the core network.
  • the generated paging; or the indication information indicates that the information of the identified identity of the paged terminal device is configured by the radio access network, the indication information indicates that the paging is based on a paging generated by the radio access network, and It is used to cause the distributed unit to know that the page is based on a page generated by the wireless access network.
  • the paging message transmitted between the CU and the DU carries the indication information, and the CU can notify the information of whether the identifier of the UE carried in the PU paging message is from the core network or the RAN side. So that the DU can know whether the page originated from the paging generated by the core network or from the paging generated by the RAN side.
  • An optional design according to the first aspect includes: the indication information includes: information of the identity of the paged terminal device originating from the core network or information of the identity of the paged terminal device configured by the radio access network; When the indication information includes the information of the identifier of the paged terminal device originating from the core network, the indication information indicates that the page is based on the page generated by the core network, and is used to enable the distributed unit to learn the information.
  • the paging is based on the paging generated by the core network; or, when the indication information includes the information of the identifier of the paging terminal device configured by the radio access network, the indication information indicates that the paging is based on the wireless connection
  • the incoming network generates a page and is used to cause the distributed unit to know that the page is based on a page generated by the wireless access network.
  • the paging message between the CU and the DU may include two cells, one cell for carrying information of the identity of the paged terminal device originating from the core network, and another cell for carrying wireless information.
  • the information of the identifier of the paged terminal device configured by the access network may optionally send the contents of the two cells when the method is executed.
  • An optional design according to the first aspect includes the distributed unit having at least one of the following: a radio link control layer, a medium access control layer, and a physical layer; the centralized unit having at least one of the following: a radio resource control layer, a service data adaptation protocol layer, and a packet data convergence layer protocol layer; the distributed unit and the centralized unit belong to the radio access network, and are communication nodes in the radio access network; the distributed The unit and the centralized unit may constitute a base station in a logical sense.
  • the embodiment of the present application provides a communication method, which is implemented in a communication system, to help solve the problem that the access control mechanism is imperfect and the system may be in error during the process of the UE accessing the network.
  • the communication system includes a centralized unit and a distributed unit.
  • an exemplary operation may be performed: the centralized unit rejects an access request of the terminal device; the centralized unit sends the indication information to the distributed unit; The indication information is used to indicate that the distributed unit needs to delete context information of the terminal device.
  • An optional design according to the second aspect includes the indication information including: an indication of denying access by the terminal device and/or information rejecting the reason for access by the terminal device.
  • An alternative design according to the second aspect includes the centralized unit receiving a notification message from the distributed unit regarding access to the terminal device.
  • the present application provides a communication device, including: at least one processor and a communication interface, the communication interface is used for information interaction between the communication device and other communication devices, when the program instruction is in the at least one process When executed in the device, the communication device is enabled to implement the functions of the centralized unit or the distributed unit in the first or second aspect and its various alternative designs.
  • the present application provides a computer program product having program instructions that, when executed directly or indirectly, are made in a first or second aspect and various alternative designs thereof The functions on a centralized unit or a distributed unit are implemented.
  • the present application provides a computer program storage medium having program instructions, such as the first or second aspect and various optional thereof, when the program instructions are directly or indirectly executed.
  • program instructions such as the first or second aspect and various optional thereof, when the program instructions are directly or indirectly executed.
  • the functionality of the design on a centralized or distributed unit is achieved.
  • the present application provides a chip system including at least one processor, such as the first or second aspect and various alternatives thereof, when program instructions are executed in the at least one processor
  • the functionality of the design on a centralized or distributed unit is achieved.
  • the present application provides a communication system comprising the communication device of the third aspect.
  • FIG. 1 is a schematic block diagram of a 5G system provided by an embodiment of the present application.
  • FIG. 2 is a schematic block diagram of a 5G system provided by an embodiment of the present application.
  • FIG. 3 is a schematic block diagram of a 5G system according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of a communication system and method according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a communication system and method according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a communication system and method according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a communication system and method according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • first, “second” and the like in the present application are only intended to distinguish different objects, and “first” and “second” do not limit the actual order or function of the objects to which they are modified.
  • first and “second” in “first indication” and “second indication” are merely meant to distinguish that the two are different indications, and “first” and “second” themselves are not The actual sequence or function is limited.
  • the expressions “exemplary”, “example”, “such as”, “optional design” or “a design” appearing in the present application are merely used to denote examples, illustrations or illustrations. Any embodiment or design described in the application as “exemplary”, “example”, “such as”, “optional design” or “a design” should not be construed as The design is more preferred or more advantageous.
  • upstream and downstream appearing in this application are used to describe the direction of data/information transmission in a specific scenario.
  • uplink generally refers to the direction in which data/information is transmitted from the terminal device to the network side, or The direction in which the distributed unit transmits to the centralized unit
  • downstream generally refers to the direction in which data/information is transmitted from the network side to the terminal device, or the direction in which the centralized unit transmits to the distributed unit.
  • upstream and Downlink is only used to describe the transmission direction of data/information, and the specific starting and ending devices of the data/information transmission are not limited.
  • the terminal device may include the following forms: user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal , a wireless communication device, a user agent, or a user device.
  • the terminal device can be a station in the WLAN (STAION, ST), which can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, and a personal digital processing.
  • WLAN STAION, ST
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and next-generation communication system, for example, a terminal device in a 5G network or Terminal equipment in the future evolution of the Public Land Mobile Network (PLMN) network.
  • PLMN Public Land Mobile Network
  • the terminal device can also be a wearable device.
  • a wearable device which can also be called a wearable smart device, is a general term for applying wearable technology to intelligently design and wear wearable devices such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories.
  • the terminal device can also be a terminal device in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • Its main technical feature is to connect items to the network through communication technology, thereby realizing mutual interaction. Even, the intelligent network of physical interconnection.
  • the terminal device uses the UE as an example to describe the solution in the embodiment, but it can be understood that the terminal device in the embodiment of the present application is not limited to the UE.
  • the CU and the DU in the embodiment of the present application are also not limited to the NR gNB, and may also include the LTE base station being divided into CU and DU, or the CU is further divided into two parts, CP and UP.
  • the protocol layer does not include an SDAP layer.
  • the UE On the RAN side, the UE generally has an RRC-connected status (RRC-connected status) and an RRC-inactive status (RRC-inactive status), and may also have an RRC-inactive status.
  • RRC-connected status RRC-connected status
  • RRC-inactive status RRC-inactive status
  • Three states When the UE is in an inactive state (for example, the terminal does not have uplink and/or downlink data transmission exceeds a set time), the base station may notify the UE to enter the RRC inactive state through an RRC message. After the UE accesses the cell, the base station establishes a corresponding UE context for the UE.
  • the RRC state of the UE changes, the base station processes the UE context of the UE accordingly. For example, the UE transitions from the RRC connected state to the RRC idle state.
  • the base station may release the UE context of the UE.
  • the UE transitions from the RRC connected state to the RRC inactive state, one possible process is to maintain or suspend the UE.
  • the UE context for example, keeps the UE context of the UE on the RAN side at the base station and/or the UE.
  • the CU therein generally has an RRC layer with a function of managing the RRC state of the UE.
  • RRC idle state and the RRC inactive state there are two cases of CN-based paging and RAN-based paging, respectively.
  • the network side knows at the time that the UE is in the RRC idle state, and the network side also passes the core network-based paging. Paging the UE.
  • the core network-based paging referred to herein may be regarded as a paging initiated by the core network, and the paging based on the radio access network referred to herein may be regarded as a paging initiated by the radio access network, such as a radio access network.
  • For the core network based paging it is generally required to forward through the base station.
  • One difference between the paging initiated by the core network and the paging initiated by the base station is that the originator of the paging is different. For the UE, it is necessary to distinguish whether the received page is based on a core network or a RAN based page.
  • the UE's final discontinuous reception cycle may be: a UE-specific DRX cycle sent by the core network, and a default DRX cycle of the cell broadcast.
  • a smaller value (which may also be a value corresponding to the smaller value obtained) is taken in (default DRX cycle).
  • the final DRX cycle of the UE may be: the UE specific DRX cycle sent by the core network, and the RAN-side UE DRX cycle carried in the RRC message received by the UE and the default DRX cycle of the cell broadcast are smaller.
  • the value (which can also be a value corresponding to the smaller value obtained).
  • a special case is if the remaining DRX cycle does not exist, the remaining one or more DRX cycles take a smaller value.
  • the paging message sent by the CU to the DU may carry the cell of the paging DRX, which may be the smaller of the following: UE specific CN DRX cycle and UE specific RAN DRX cycle.
  • the paging message sent by the CU to the DU does not distinguish whether the paging is a paging originating from the CN or a paging originating from the RAN, nor how to handle the paging when the UE enters the RRC inactive state.
  • the CU when the UE enters the inactive state, in general, the CU notifies the DU to release the UE context of the UE, but the mechanism still has defects, such as whether the DU can interfere with the CU's decision about releasing the UE context, and for example, the DU receives the release.
  • the RRC connection release message sent by the CU to the UE has not been forwarded to the UE, and the UE has uplink data arrival (UL data arrival), for example, the UE sends a scheduling request to the base station (DU and/or CU). (scheduling request, SR) or buffer status report (BSR), which may cause system errors.
  • SR scheduling request
  • BSR buffer status report
  • the UE requests to establish an RRC connection with the RAN.
  • the DU or CU in the base station may reject the request of the UE to establish an RRC connection.
  • the UE sends a message 3 (MSG3) to request to establish an RRC connection (which may be any of the new, restored, or reestablished RRC connections), and the DU sends the RRC message in the MSG3 to the CU, and the MSG3 carries the UE for the UE.
  • MSG3 message 3
  • the RRC information includes the layer 1 (L1) and/or layer 2 (L2) parameters of the signaling radio bearer 1 (SRB1) configured by the DU, for example, the RRC information in the NR includes a cell group. Configure CellGroupConfig. If the CU receives the DU to CU RRC information sent by the DU, it determines that the DU allows the UE to access, otherwise it considers that the DU does not allow the UE to access.
  • the CU may perform admission control on the access of the UE. For example, if the CU rejects the UE accessing the RAN, the CU may send a response to the UE, where the response is directed to the UE.
  • the RRC message carried in the MSG3 sent by the base station is made, and the response is used to indicate that the UE desires to establish an RRC connection is rejected.
  • the RRC message is sent to the DU in the RRC Container carried in the MSG3, but the DU does not analyze whether the content in the RRC Container accepts the RRC connection setup request or rejects the RRC connection setup request.
  • the DU will establish a protocol stack entity (such as an RLC entity, a logical channel of the MAC, etc.) for transmitting the SRB1 for the UE, and
  • the UE establishes a context, where the context of the UE includes a C-RNTI of the UE, an F1 interface ID (for example, a DU UE F1AP ID and/or a CU UE F1SP ID); in addition, the DU or the CU may also be a subsequent RRC message of the UE ( For example, MSG5) performs scheduling.
  • the first case includes: the DU starts a timer after sending the message 3.
  • the DU After the timer expires, the DU still does not receive the UE context setup request message sent by the CU, and the DU The relevant configuration and UE context can be deleted.
  • the second case includes: the DU reads the type of the RRC message included in the msg3, determines whether the CU rejects according to the RRC message type, or rejects the RRC connection/reconstruction/recovery request initiated by the UE, thereby determining whether to delete the DU.
  • the configuration and/or the context of the UE In the first case, if the timer is not set properly, it will cause a system error.
  • the DU receives the UE context setup request message sent by the CU again.
  • the DU has been deleted.
  • the configuration and/or UE context will result in unsuccessful UE context establishment.
  • the assumption that the RRC layer is in the CU in the 5G RAN system is not met.
  • the CU rejects the UE access, the CU needs to display the indicated DU, so that the DU deletes the above configuration and the UE context.
  • the embodiment of the present application provides a communication system and a method for operating the same, to solve the problem that the paging mechanism based on the CU-DU architecture is imperfect, for example, when paging a UE in an RRC inactive state, The paging mechanism can lead to system errors.
  • the CU provides indication information to the DU, and the indication information is used to indicate that a page is a core network based paging and/or a RAN based paging, so that the DU
  • the UE can be informed and informed that the page is a core network based paging or a RAN based paging.
  • system 400 includes CUs, DUs, and UEs, where CUs and DUs are functional nodes in the RAN architecture.
  • System 400 can operate in the following exemplary manner:
  • Operation 401 The CU sends indication information for indicating a paging type to the DU.
  • the indication information for indicating the type of the paging may be generated by the CU, and the indication information of the paging type may be carried in a paging message sent by the CU to the F1 application protocol (F1AP) of the DU.
  • F1AP F1 application protocol
  • the indication information for indicating the paging type is information of the identifier of the paged UE originating from the core network, and the indication information is used to indicate that the paging involved is based on a page generated by the core network, and used to enable the distributed unit to learn that the page is based on a page generated by the core network; or, the indication information is information of the identity of the paged UE configured by the radio access network, The indication information is then used to indicate that the page is based on a page generated by the wireless access network and is used to cause the distributed unit to know that the page is based on a page generated by the wireless access network.
  • the indication information may be referred to as a resume ID, or other identifier information derived based on the recovery identifier, where the recovery identifier may be used in an RRC inactive state.
  • the UE may also be used to indicate that the paging involved is based on RAN-based paging, and the recovery identifier may also be used to acquire the context of the UE.
  • an exemplary implementation includes: the paging message of the F1AP sent by the CU to the DU may carry the UE Identity Index value and the UE Paging identity.
  • Information element IE
  • the UE Identity Index value may be a UE_ID
  • the UE paging identifier of the core network in the NR system may be other names, and no limitation is imposed herein.
  • the above two values can be used to calculate a paging frame (PF) and a paging occasion (PO).
  • the identity information of the UE (such as the paging identifier of the UE) provided by the CU to the DU is originated from the core network, and the paging identifier information of the UE is The core network S-TMSI and/or the IMSI may be; when the paging is based on the RAN-based paging, the paging identifier information of the UE provided by the CU is a resume ID or a RAN in the RAN. Information generated by the side for the UE identity of the paging procedure.
  • the UE paging identifier may be actively provided by the DU to the CU, or sent to the CU based on the CU request.
  • the DU identifies, according to the preset configuration, information about the paging identifier of the UE generated by the core network (for example, the core network TMSI or IMSI), or the paging identifier information of the UE generated on the RAN side (for example, Is the resume ID or a message generated on the RAN side for the UE identity of the paging procedure).
  • the DU may determine a discontinuous reception period of the UE according to the paging type.
  • the determining that the final discontinuous reception period of the UE by the DU may include: a UE-specific DRX period sent by the core network, and a smaller default DRX period of the cell broadcast.
  • the value (which can also be a value corresponding to the smaller value obtained).
  • the DU determines that the UE's final DRX cycle may include: the UE specific DRX cycle sent by the core network, and the RAN side UE carried in the RRC message received by the UE.
  • the DRX cycle and the default DRX cycle of the cell broadcast take a smaller value (which may also be a value corresponding to the smaller value obtained).
  • One possibility is that if one of the individual DRX cycles does not exist, the remaining one or more DRX cycles take a smaller value.
  • the DU may optionally send the indication information for indicating the paging type to the UE in operation 402.
  • the information of the paging identifier of the UE may be placed.
  • the broadcast paging message (such as carried in the cell PagingRecord) is broadcast in the air interface, and/or the indication is carried in the broadcast paging message to the UE to enable the UE to know that the paging is based on the paging generated by the RAN side. It is also based on the paging generated by the CN.
  • the UE may determine whether to be based on a paging of the core network or a paging based on the radio access network based on the indication. Similar to the DU, the UE can determine the final discontinuous reception period according to the paging type.
  • an alternative design operation 401 2 comprising: transmitting a paging message to the DU CU includes information identifying the paged UE; it is, for indicating when the paging indication information indicates the type of paging is directed Based on the paging generated by the core network or the paging generated based on the radio access network, the indication information is used to cause the DU to know that the paging involved is based on a page generated by the core network or the paging is generated based on the radio access network.
  • the specific process of paging including:
  • the indication information indicates that the information of the identifier of the paged UE is from the core network, it indicates that the page is based on a page generated by the core network, and the indication information is used to enable the DU to know that the page involved is Based on the paging generated by the core network; or, the indication information indicates that the information of the identifier of the paged UE is configured by the radio access network, indicating that the paging is based on a paging generated by the radio access network, and the indication information is Used to cause the DU to know that the page is based on a page generated by the radio access network.
  • the CU may set the displayed cell to indicate, in addition to the UE Paging identity cell, the F1AP paging message sent by the DU, for example, the indication may be a RAN based Paging indication.
  • the indication may be a CN based Paging indication.
  • the indication is 0, the paging is based on a paging generated by the radio access network, and when the indication is 1, the paging is based on the core network. Generated pages.
  • the indication information for indicating the paging type includes: information of the identifier of the paged terminal device originating from the core network or the paging terminal device configured by the radio access network. Identification of the information.
  • two information cells may be set in the indication information, where one cell is used to carry the information of the identifier of the paged terminal device originating from the core network, and another cell is used to carry the radio access network configuration. The information of the identified identity of the terminal device, but when the indication information is sent, the information carried by the two cells may be sent.
  • the indication information when the indication information includes information of an identifier of a paged terminal device originating from a core network, the indication information indicates that the page is based on a page generated by the core network, and is used for Having the distributed unit knowing that the paging is based on a page generated by the core network; or, when the indication information includes information of an identifier of a paged terminal device configured by a radio access network, The indication information indicates that the page is based on a page generated by the radio access network and is used to cause the distributed unit to learn that the page is based on a page generated by the radio access network.
  • one of the paging messages of the F1AP sent by the CU to the DU carries the identification information of the UE configured on the CN side, indicating that the paging is based on the paging generated by the CN side, or is sent to the DU through the CU.
  • the other cell in the paging message of the F1AP carries the ID information of the UE configured on the RAN side, indicating that the paging is based on the paging generated by the RAN side.
  • the paging message sent by the CU to the F1AP of the DU includes the UE paging identifier, and the UE Paging identity may carry the UE allocated by the CN side.
  • Identification information if it is based on RAN-based paging, the paging message sent by the CU to the F1AP of the DU includes the newly set cell, for example, the cell is a UE radio access network paging.
  • the UE Paging Identity for RAN based Paging
  • the cell may carry the identifier information of the UE allocated by the RAN side.
  • a new IE may be separately set in the F1AP paging message sent by the CU to the DU, and the new IE is used to enable the CU to provide the resume ID or the information of the UE identity generated by the RAN side for the paging process.
  • the new IE may be UE Paging Identity for RAN based paging.
  • the DU may select the received resume ID or the information of the UE identifier generated by the RAN side for the paging process.
  • the UE Paging Identity for RAN based paging is sent to the UE in the paging message broadcasted by the air interface (for example, in the PagingRecord), or carries an indication in the broadcast paging message to the UE to enable the UE to learn the The paging is based on whether the paging generated by the RAN side or the paging generated by the CN.
  • an indication of whether or not the RAN based paging can be given in the PagingRecord for example, 0 indicates CN based paging, and 1 indicates RAN based paging.
  • the operation 402 is enabled to perform the DU to transmit indication information for indicating the paging type to the UE.
  • the operation 401 is an optional operation, that is, the CU may not send the indication information of the paging category to the DU, and the specific paging type is determined by the DU.
  • the identification information of the UE originating from the core network may be used between the CU and the DU, but the DU is in the air interface to the CN based paging and the RAN based paging. The situation is differentiated.
  • the broadcast paging message sent by the DU carries an indication of whether it is RAN based paging.
  • the indication bit when the value of the bit is 0, indicates that the page is CN based paging, and when the value of the bit is 1, it indicates that the page is RAN based paging. It can be understood that the meaning of the specific value may be different. For example, when the value of the bit is 1, it indicates that the paging is CN based paging. When the value of the bit is 0, the paging is RAN. Based paging.
  • the CU in the system 400 can be further divided into a CP and an UP according to the manner of FIG. 3.
  • the functions of the foregoing CU in the system 400 can be implemented by the CP, of course, in the system 400.
  • the functions of the aforementioned CU can also be implemented in UP.
  • the information about the identity of the UE configured on the RAN side in any of the foregoing designs may also be other information that can be used to identify the UE that is configured on the RAN side, as long as the related information of the configured UE can identify the UE, or Helps find the context of the UE or helps identify the type of paging for that UE.
  • the RAN side configuration that is, the CU in the RAN side performs the configuration, or the DU performs the configuration, or the CU and the DU complete the configuration through negotiation, for example, initiated by the RAN side.
  • Paging by the CU or by the DU or by the CU in conjunction with the DU, to configure the paging with a message capable of identifying the UE, to help identify that the type of the paging is initiated by the core network on the DU side. Still on the radio access network initiated paging.
  • the embodiment of the present application further provides a communication system and a method for operating the same, to help solve the problem that the CU notifies the DU to release the UE context of the UE when the UE enters the inactive state. Defects.
  • the system 500 has CUs and DUs that, when the system 500 is running, exchange messages between the CUs and the DUs to perform the following exemplary method 500:
  • the CU sends a message for releasing the UE context to the DU, for example, the message may be a UE context release message, and the message includes a reason value indicating that the UE enters the RRC inactive state (UE enter into inactive).
  • the CU sends a message to the UE to release the UE context, for example, the message may be a UE context release message, where the message may be sent to the UE for releasing the RRC connection, for example, RRC connection release message; or the CU may also carry an RRC connection release in another F1AP message, such as a DL RRC message transfer message, which may also include a cause value (eg, UE enter into inactive) and / Or RRC message type.
  • the UE can learn that the UE enters the RRC inactive state, so the context of the UE is released.
  • the DU learns that the UE enters the RRC inactive state, reserves the UE context, and suspends the wireless signaling and/or the wireless data bearer.
  • An optional design includes: for a scenario in which an uplink data arrival (UL data arrival) occurs: when the DU has not forwarded the RRC release message sent by the CU to the UE, the SR/BSR sent by the UE is received, and the DU learns the UL data arrival.
  • the DU notifies the CU to refuse to release the UE context.
  • the notification message includes a cause value of UL data arrival.
  • the information that the DU can be carried to determine the UE to enter the inactive state, and the implementation manner of the notification message may be an active/inactive indication, or an indication that the inactive timer expires.
  • the DU sends a notification message to notify the CU UE to enter the inactive state, and has not received the CU reply, and finds that there is uplink data arrival (UL data arrival), the DU notifies the CU of the situation (ie, UL data arrival), so that the CU can make the timely
  • the correct decision for example, the CU can decide that the UE cannot enter the RRC inactive state.
  • An optional design includes: for a scenario in which DL data arrival occurs: after the CU sends a UE context release and/or an RRC release message to the DU, a downlink data arrival (DL data arrival) occurs, optionally The CU determines that the DU may have not released the UE context and/or forwards the RRC release message. Optionally, the CU sends a UE context release cancel message and/or a DL RRC message transfer cancel message to the DU, where the message includes the cause value.
  • the message may further include at least one of paging information (for example, resume ID, paging DRX, UE Identity Index value, Paging priority, and UE paging identity, or three operations of the foregoing operation 401).
  • paging information for example, resume ID, paging DRX, UE Identity Index value, Paging priority, and UE paging identity, or three operations of the foregoing operation 401).
  • an optional design includes: the CP (CU-CP) in the CU sends a UE context release message to the DU and/or the UP (CU-UP) in the CU, and the message includes the reason.
  • the CU-CP may also carry an RRC connection release in another F1AP message, such as a DL RRC message transfer message, and the message may also include a reason value of the UE enter into inactive or an RRC message type.
  • the subsequent DU receives the UE context release message sent by the CU, and it can be presumed that the UE needs to release the UE context because the UE enters into inactive.
  • An optional design includes: for the case of uplink data arrival (UL data arrival): reference can be made to the description of the foregoing CU-DU architecture, and the function of the CU can be implemented in the CP.
  • An optional design includes: for the occurrence of downlink data arrival (DL data arrival): assuming that the CU-UP notifies the CU-CP that the UE is in an inactive state, the CU-UP can provide the timer to the time through the CU-CP. It is determined whether the UE enters an inactive state. If the CU-UP has not received the indication that the UE sent by the CU-CP has entered the inactive state or the UE context release, then:
  • Optional operation 1 The CU-UP sends a DL data arrival indication to the CU-CP, for example, the E1 interface UE identifier, such as gNB-CU-UP UE E1APID, DL data arrival indication, etc., is included in the E1 interface message.
  • the subsequent operations may refer to the description of the foregoing CU-DU architecture, and the function of the CU is implemented in the CU-CP.
  • the CU-CP notifies the DU and knows that the UE has not entered the inactive state, the CU-CP notifies the CU-UP that the downlink data DL data can be sent to the DU.
  • Optional operation 2 The CU-UP directly sends the DL data arrival indication or the downlink data DL data to the DU. If the DU receives the DL data arrival or the DL data, the RRC connection release message is cancelled and sent to the UE. Optionally, the DU notifies the CU. - The CP does not release the UE context or the UE does not enter the inactive state, and the notification message may also include a DL data arrival indication.
  • An optional design includes the CU monitoring the downlink transmission status, and the DU monitoring the uplink transmission status and reporting the uplink transmission status to the active/inactive to the CU.
  • the timer may be used when the DU determines the uplink transmission state. The timer may be set by the DU itself, or the CU may provide a timer to the DU.
  • the DU reports the uplink transmission status, it can follow the UE granularity, PDU session granularity, slice granularity, or DRB granularity.
  • the DU may report, for example, a UE identity and an active/inactive indication.
  • the DU may report, for example, the UE identity, the PDU session identifier/slice identifier/DRB identifier, and the active/inactive state of the corresponding PDU session/slice/DRB.
  • the timer may also be PDU session/slice/DRB granularity, that is, each PDU session identifier/slice identifier/DRB identifier corresponds to a timer.
  • An optional design includes the DU monitoring the uplink transmission status and the downlink transmission status, and reporting the uplink transmission status and the downlink transmission status to the CU.
  • the timer can be directed to the uplink and to the downlink. Either the uplink timer is for uplink transmission and the downlink timer is for downlink transmission.
  • the timer may be set by the DU itself, or the CU may provide a timer to the DU.
  • the DU reports the uplink transmission state, it may be according to the UE granularity, the PDU session granularity, the slice granularity, or the DRB granularity.
  • the DU reports the downlink transmission status, it can also follow the UE granularity, PDU session granularity, slice granularity, or DRB granularity.
  • the embodiment of the present application further provides a communication method, where the communication method runs in a communication system, where the communication system includes a centralized unit and a distributed unit.
  • the following exemplary operations can be performed: centralized The unit rejects the access request of the terminal device; the centralized unit sends the indication information to the distributed unit; the indication information is used to indicate that the distributed unit needs to delete the context information of the terminal device.
  • the optional design includes: the indication information includes: an indication of denying access by the terminal device and/or information rejecting the reason for access by the terminal device.
  • An optional design includes: the centralized unit receives a notification message sent by the distributed unit about allowing the terminal device to access.
  • the embodiment of the present application provides a communication system and method 600, where the system includes three network nodes: a CU, a DU, and a UE, where the CU and the DU constitute a base station system.
  • the system and method 600 includes:
  • Optional operation 601 The UE sends a message 3 to the base station system.
  • the message 3 may contain an RRCConnectionRequest, or an RRCConnectionResumeRequest (or may be other similar messages, the message name may be different), or an RRCConnectionRestablishmentRequest.
  • Optional operation 602 The DU sends a message 3 to the CU.
  • the DU sends a CU-DU interface message, such as an F1AP message, to the CU, where the F1AP message may include the message 3 of the UE.
  • the foregoing F1AP message may further include a container of the DU to the CU, where the L1/L2 configuration of the SRB1 carrying the UE, for example, the cell group configuration CellGroupConfig.
  • the foregoing F1AP message may be an Initial UL RRC Message.
  • the DU determines whether the access of the UE is allowed.
  • the F1AP message includes the container for the CU to the CU, for example, DU to CU RRC information, which includes the cell group configuration; otherwise, if the DU does not If the access of the UE is allowed, the F1AP message does not include the container of the DU to the CU.
  • the CU can know whether the DU allows access by the UE.
  • the CU may reply to the message 4 (the process is optional operations 603 and 604 as shown in FIG. 6).
  • the CU determines whether the access of the UE is allowed. If the access of the UE is denied, the message 4 includes an RRC message corresponding to the content of the message 3, indicating that the UE is denied access, such as RRCConnectionReject, RRCConnectionReestablishmentReject.
  • the CU sends an F1AP message to the DU, where the acknowledgment indication and/or the refusal cause value is used to notify the DU, and the CU rejects the access of the UE, thereby triggering the DU to delete the context of the UE (as shown in FIG.
  • the action of deleting the context of the UE by the DU includes at least one of the following: the DU releases the C-RNTI/Temp CRNTI allocated for the UE, the DU releases the resource reserved for the UE, and the DU deletes the L1/L2 of the UE. Configure, and the DU releases the DU UE F1AP ID assigned to the UE.
  • the foregoing F1AP message is DL RRC Message Transfer.
  • the reason that the CU decides to reject the access of the UE may be a DU rejection, or the CU rejects itself.
  • a possible situation is that if the CU knows that the DU rejects the access of the UE, the CU does not need to send a reject indication to the DU; optionally, if the CU knows that the DU allows the UE to access, and the CU does not allow the UE to access, The CU needs to send a reject indication to the DU, thereby notifying the DU to delete the context of the UE.
  • the embodiment of the present application provides a communication system and method 700, where the system includes three network nodes: a CU, a DU, and a UE, where the CU and the DU constitute a base station system.
  • the operation of the system and method 700 helps to solve the problem that the access control mechanism is imperfect and the system is faulty when the UE accesses the network in the prior art.
  • one example of the operation of the system and method 700 includes:
  • Optional operation 701 The UE sends a message 3 to the base station system.
  • the message 3 may contain an RRCConnectionRequest, or an RRCConnectionResumeRequest (or other similar message, the name may be different), or an RRCConnectionRestablishmentRequest.
  • Optional operation 702 The DU sends a message 3 to the CU. After receiving the above message 3 sent by the UE, the DU sends the message 3 to the CU.
  • the DU sends an F1AP message to the CU, where the F1AP message includes the message 3 of the UE.
  • the foregoing F1AP message further includes a container of the DU to the CU, where the L1/L2 configuration of the SRB1 of the UE is carried.
  • the foregoing F1AP message may be an Initial UL RRC Message.
  • the DU informs the CU whether to allow access by the UE.
  • the DU determines whether the access of the UE is allowed, and if so, the container of the CU is included in the F1AP message; otherwise, if the DU does not allow access by the UE, the F1AP message is not Contains the container for the DU to the CU.
  • the CU can know whether the DU allows access by the UE.
  • Optional operation 703 After receiving the message 3 sent by the UE, the CU replies to the message 4 to the UE.
  • the CU determines whether the access of the UE is allowed. If the access of the UE is denied, the message 4 may include an RRC message corresponding to the content in the message 3, indicating that the UE is denied access, such as RRCConnectionReject, RRCConnectionReestablishmentReject.
  • the CU sends an F1AP message to the DU, where the message 4 is carried.
  • the above F1AP message may be DL RRC Message Transfer.
  • the CU sends a reject indication and/or a reject cause value to the DU, to notify the DU to delete the context of the UE.
  • the CU sends an F1AP message to the DU, where the refusal indication and/or the rejection reason value are included.
  • the F1AP message is a UE Context Release.
  • the action of deleting the context of the UE by the DU includes at least one of the following: the DU releases the C-RNTI/Temp CRNTI allocated to the UE, the DU releases the resource reserved for the UE, and the DU deletes the L1/L2 configuration of the UE. And the DU releases the DU UE F1AP ID assigned to the UE.
  • the reason that the CU determines to reject the access of the UE may be at least one of the following: the DU rejects the UE access, and the CU side rejects the UE access by itself.
  • the CU knows that the DU rejects the access of the UE, the CU does not need to send a reject indication to the DU; if the CU knows that the DU allows the UE to access, and the CU does not allow the UE to access, the CU needs to A rejection indication is sent to the DU, thereby informing the DU to delete the context of the UE.
  • the CU-UP can be physically deployed separately from the CU-CP and the DU, or can be deployed in a centralized manner.
  • any of the designs shown above may be understood as a technical solution designed for a specific scenario or a specific technical problem, but it is not necessary to implement the technical content described in the present application, and any one of the designs may be required according to needs. Implemented in conjunction with other designs to more specifically address specific objective technical issues.
  • the distributed unit DU has the functions of the RLC, MAC, and PHY protocol layers
  • the centralized unit CU has the functions of the RRC, SDAP, and/or PDCP protocol layers
  • the DU and CU The protocol layers that are formed together constitute the RRC, SDAP, PDCP, RLC, MAC and PHY or RRC, PDCP, RLC, MAC and PHY protocol layer architecture settings that the base station has.
  • RRC Secure Digital Access
  • PDCP Radio Resource Control Protocol
  • RLC radio link control protocol
  • MAC and PHY protocol layer architecture settings that the base station has.
  • the DU has a MAC and a PHY
  • the CU has RRC, SDAP, PDCP and RLC or RRC, PDCP and RLC, where Not limited.
  • the DU can be physically integrated with the radio system as two parts of a communication device, and the DU and CU can also be physically part of a communication device to integrate the two, or The RF system and the DU and CU can also be physically part of the same network node so that the three can be integrated.
  • the hardware platform having the processor and the communication interface can execute program instructions to respectively implement any of the foregoing embodiments in the present application.
  • the function involved in the design, based on this, as shown in FIG. 8 the embodiment of the present application provides a schematic block diagram of a communication device 800, where the communication device 800 includes:
  • At least one processor 801 optionally including a communication interface 802 for supporting communication interaction between the communication device 800 and other devices; when the program instructions are executed in the at least one processor 801, the foregoing embodiment of the present application
  • the functionality of any of the following devices operating on any of the following devices is implemented: UE, CU, DU, CP, and UP.
  • the communication device 800 may further include a memory 803 for storing program instructions necessary for implementing the above-described device functions or process data generated during program execution.
  • the communication device 800 can also include an internal interconnecting line to implement communication interaction between the at least one processor 801, the communication interface 802, and the memory 803.
  • the at least one processor 801 can be implemented by a dedicated processing chip, a processing circuit, a processor, or a general purpose chip.
  • a dedicated circuit/chip may be provided in the at least one processor.
  • the implementation can also be implemented by using a general-purpose processor provided in the at least one processor 801 to execute a program instruction related to a PHY function, an F1 port or an E1 port communication function; for example, the embodiment of the present application relates to a MAC in the device.
  • the at least one processor 801 may comprise a communication processing chip, by performing MAC layer, RLC layer, PDCP layer, SDAP layer and RRC layer.
  • the relevant functions of the program instructions are implemented. It can be understood that the various methods, processes, operations or steps involved in the embodiments of the present application can be combined in one-to-one correspondence by computer software, electronic hardware, or a combination of computer software and electronic hardware. A corresponding implementation. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. For example, considering the generality, low cost, low hardware and software decoupling, etc., it can be implemented by means of executing program instructions, for example. Considering system performance and reliability, it can be implemented using dedicated circuits. A person skilled in the art can use different methods for implementing the described functions for each specific application, which is not limited herein.
  • the communication interface 802 generally has the function of performing information interaction between two communication peers.
  • the communication interface may be designed as an interface circuit or include the same.
  • the hardware module of the interface circuit supports the wired form communication interaction between the communication peers.
  • the F1 port between the DU and the CU involved in the present application and the communication function of the E1 port between the CP and the UP can be adopted.
  • This type of interface design for the case where the wireless communication information interaction is performed between the communication peers, the communication interface may be an interface circuit having a radio frequency transceiving function, or a hardware system including the interface circuit having the radio frequency transceiving function.
  • the communication interface of the DU and the UE can adopt this design.
  • the CU, DU, the CP, or the UP can also be implemented by directly or indirectly executing the implementation program instructions of the embodiment related design by using a general hardware platform (having processing resources and storage resources). Or the function of UP in each design of the embodiment of the present application.
  • An actual deployment method may be that the CU, the CP, or the UP may be close to the core network device, or may be deployed cooperatively, and may be physically separated or combined; the functions of the CU, CP, or UP may also be used as part of the core network device.
  • the embodiment of the present application further provides a computer program product having program instructions, when the program instructions are directly or indirectly executed, for example, when executed in the communication device 800 in the foregoing embodiment,
  • the functions of any of the following devices in any of the design embodiments are implemented: UE, CU, CP, UP, and DU.
  • the program instructions may 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 program instructions may be from a website site, a computer
  • the server or data center is transported to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.).
  • a program instruction When a program instruction is executed, considering that a specific network device generally includes a hardware layer, an operating system layer and/or an intermediate layer running on the hardware layer, when program instructions related to the embodiment of the present application are executed, The invocation and execution of layer software, so the program instructions can be an indirect execution process in a hardware device (general purpose processing circuit or dedicated processing circuit).
  • the embodiment of the present application further provides a chip system, the chip system including at least one processor, when program instructions are executed in the at least one processor, such that the design is as described in the first aspect and any of the The functions on any of the following devices are implemented: UE, CU, DU, CP, and UP.
  • the present application also provides the following embodiments. It should be noted that the numbering manner of the following embodiments is not based on the numbering manner of the foregoing embodiments.
  • Embodiment 1 A communication method includes: a centralized unit sends a paging message to a distributed unit, where the paging message carries a page indicating that the paging is generated based on a core network or the paging is based on The indication information of the paging generated by the radio access network;
  • the indication information is used to cause the distributed unit to learn that the page is based on a page generated by a core network or that the page is based on a page generated by a wireless access network.
  • Embodiment 2 The communication method as described in Embodiment 1, comprising: the indication information is information originating from an identifier of a paged terminal device of a core network, and the indication information is used to indicate that the paging is And generating, according to the paging generated by the core network, the distributed unit, that the paging is based on a page generated by the core network; or the indication information is configured by a radio access network Paging information identifying the terminal device, the indication information being used to indicate that the page is based on a page generated by the radio access network, and used to cause the distributed unit to learn the page It is based on a page generated by the radio access network.
  • Embodiment 3 The communication method according to Embodiment 1, wherein the paging message further includes information of an identifier of the paged terminal device; the indication information indicates that the paging is based on a page generated by a core network or The paging is based on a paging generated by a radio access network, the indication information being used to cause the distributed unit to learn that the paging is based on a page generated by a core network or the paging is based on a wireless connection
  • the paging generated by the network includes: the indication information indicates that the paging is based on a page generated by the core network, and is used to enable the distributed unit to learn that the paging is based on the core network Generating a page; or, the indication information indicates that the page is based on a page generated by the radio access network, and is used to cause the distributed unit to learn that the page is based on the wireless connection The page generated by the network.
  • Embodiment 4 The communication method as described in Embodiment 1, wherein the paging message further includes information of an identifier of the paged terminal device; the indication information indicates that the paging is based on a page generated by a core network or The paging is based on a paging generated by a radio access network, the indication information being used to cause the distributed unit to learn that the paging is based on a page generated by a core network or the paging is based on a wireless connection
  • the paging generated by the network includes: the indication information indicates that the information of the identifier of the paged terminal device originates from a core network, and the indication information indicates that the paging is based on a page generated by the core network. And being used to cause the distributed unit to learn that the paging is based on a page generated by the core network; or,
  • the indication information indicates that the information of the identifier of the paged terminal device is configured by the radio access network, and the indication information indicates that the paging is based on a paging generated by the radio access network, and is used Having the distributed unit know that the page is based on a page generated by the wireless access network.
  • Embodiment 5 The communication method as described in Embodiment 1, wherein the indication information includes: information of an identifier of a paged terminal device originating from a core network or an identifier of a paged terminal device configured by a radio access network Information; when the indication information includes information of an identifier of a paged terminal device originating from a core network, the indication information indicates that the page is based on a page generated by the core network, and is used for Having the distributed unit knowing that the paging is based on a page generated by the core network; or, when the indication information includes information of an identifier of a paged terminal device configured by a radio access network, The indication information indicates that the page is based on a page generated by the radio access network and is used to cause the distributed unit to learn that the page is based on a page generated by the radio access network.
  • Embodiment 6 A communication method, comprising: a distributed unit receiving a paging message from a centralized unit, the paging message carrying a page indicating that the paging is based on a core network or the paging Is the indication information of the paging generated by the radio access network; the distributed unit is configured to learn, according to the indication information, that the paging is based on a paging generated by a core network, or the paging is generated based on a radio access network. Paging.
  • Embodiment 7 the communication method as described in Embodiment 6, comprising: the indication information is information derived from an identifier of a paged terminal device of the core network, and the indication information is used to indicate that the paging is Based on the paging generated by the core network, the distributed unit learns, according to the indication information, that the paging is based on a page generated by the core network; or, the indication information is a configuration of a radio access network configuration. Paging information of the identifier of the terminal device, wherein the indication information is used to indicate that the paging is based on a page generated by the radio access network, and the distributed unit learns the paging according to the indication information It is based on a page generated by the radio access network.
  • Embodiment 8 The communication method according to Embodiment 6, wherein the paging message further includes information of an identifier of the paged terminal device; the indication information indicates that the paging is based on a page generated by a core network or The paging is based on a paging generated by the radio access network, and the distributed unit learns, according to the indication information, that the paging is based on a paging generated by a core network, or the paging is generated based on a radio access network.
  • the paging includes: the indication information indicates that the paging is based on a page generated by the core network, and the distributed unit learns, according to the indication information, that the paging is based on the core network generated Or the indication information indicates that the paging is based on a paging generated by the radio access network, and the distributed unit learns, according to the indication information, that the paging is generated based on the radio access network. Paging.
  • Embodiment 9 The communication method as described in Embodiment 6, wherein the paging message further includes information of an identifier of the paged terminal device; the indication information indicates that the paging is based on a page generated by a core network or The paging is based on a paging generated by the radio access network, and the distributed unit learns, according to the indication information, that the paging is based on a paging generated by a core network, or the paging is generated based on a radio access network.
  • the paging includes: the indication information indicates that the information of the identifier of the paged terminal device is derived from a core network, and the indication information indicates that the paging is based on a page generated by the core network,
  • the distributed unit learns, according to the indication information, that the paging is based on a page generated by the core network; or, the indication information indicates that the information of the identifier of the paged terminal device is configured by the radio access network, And the indication information indicates that the paging is based on a paging generated by the radio access network, and the distributed unit learns, according to the indication information, that the paging is based on a paging generated by the radio access network. .
  • Embodiment 10 The communication method as described in Embodiment 6, wherein the indication information includes: information of an identifier of a paged terminal device originating from a core network or an identifier of a paged terminal device configured by a radio access network Information; when the indication information includes information of an identifier of a paged terminal device originating from a core network, the indication information indicates that the paging is based on a page generated by the core network, the distributed Determining, according to the indication information, that the paging is based on a page generated by the core network; or, when the indication information includes information of an identifier of a paging terminal device configured by a radio access network, The indication information indicates that the paging is based on a page generated by the radio access network, and the distributed unit learns, according to the indication information, that the paging is based on a page generated by the radio access network.
  • Embodiment 11 A communication method, comprising: a centralized unit rejecting an access request of a terminal device; the centralized unit sending indication information to the distributed unit; the indication information is used to indicate that the distributed unit needs to delete the The context information of the terminal device.
  • Embodiment 13 The communication method as described in Embodiment 10 or 11, comprising: the centralized unit receiving a notification message sent by the distributed unit about allowing access by the terminal device.
  • Embodiment 14 a communication method, including: in a case where an access request of a terminal device is rejected by a centralized unit,
  • the distributed unit receives the indication information sent by the centralized unit; the indication information is used to indicate that the distributed unit needs to delete the context information of the terminal device.
  • the communication method of embodiment 14, comprising: the indication information comprising: an indication of denying access by the terminal device and/or information rejecting a reason for access by the terminal device.
  • Embodiment 16 The communication method of embodiment 14 or 15, comprising: the distributed unit transmitting a notification message to the centralized unit about allowing access by the terminal device.
  • the distributed unit has at least one of: a radio link control layer, a medium access control layer, and a physical layer;
  • the formula unit has at least one of the following: a radio resource control layer, a service data adaptation protocol layer, and a packet data convergence layer protocol layer; the distributed unit and the centralized unit belong to the radio access network or belong to one Base station.
  • Embodiment 18 A communication device, comprising: at least one processor and a communication interface, wherein the communication interface is used for information interaction between the communication device and other communication devices, when program instructions are in the at least one processing When executed in the apparatus, the communication device is caused to implement the functions of any of the methods of any of embodiments 1-17 on any of the following: the distributed unit and the centralized unit.
  • Embodiment 19 A computer program storage medium having program instructions, when the program instructions are directly or indirectly executed, such that the method of any of embodiments 1-17 is as follows The functionality on either device is achieved: the distributed unit and the centralized unit.
  • Embodiment 20 A chip system, the chip system comprising at least one processor, when program instructions are executed in the at least one processor, such that the method according to any one of embodiments 1-17 is as follows The functionality on either device is achieved: the distributed unit and the centralized unit.
  • Embodiment 21 A communication system, comprising: the communication device as described in Embodiment 18.

Landscapes

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

Abstract

本申请实施例提供了一种通信方法，以有助于解决现有技术中基于集中式单元CU和分布式单元DU架构的无线接入网存在的寻呼机制不完善，并可能导致寻呼失败的问题，该方法包括以下过程：集中式单元向分布式单元发送寻呼消息，该寻呼消息中携带表明所涉及的寻呼是基于核心网产生的寻呼或该寻呼是基于无线接入网产生的寻呼的指示信息；分布式单元通过该指示信息可以获知涉及的寻呼是基于核心网产生的寻呼还是基于无线接入网产生的寻呼。通过该方法，有助于使得背景技术中的寻呼机制趋于合理完善，减少系统寻呼失败的情况。

Description

一种通信方法，设备及其系统
本申请要求于2018年01月12日提交中国国家知识产权局、申请号为201810030917.4、发明名称为“一种通信方法，设备及其系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，更具体的，涉及一种通信方法，设备及其系统等。
背景技术
在下一代移动通信系统中，比如第五代移动通信(the 5th generation mobile communication technology，5G)系统中，基站被称为gNB或ng-eNB，其中，ng-eNB是源于长期演进(long term evolution，LTE)系统基站(LTE eNB)的后续演进基站，仅为便于描述，本文采用gNB来表示基站。图1所示系统100为一种5G系统的示意性框图，其中，下一代无线接入网(next generation radio access network，NG-RAN)中的gNB和gNB之间，ng-eNB和ng-eNB之间，以及gNB和ng-eNB之间通过Xn接口互连。gNB和5G核心网(5G core，5GC)设备之间通过NG接口互连，ng-eNB和5GC设备之间通过NG接口互连。其中，5GC设备可以是接入和移动性管理功能实体(access and mobility management function，AMF)或用户面功能实体(user plane function，UPF)，AMF主要负责接入管理方面功能，UPF主要负责会话(session)管理方面功能。基站通常包括无线资源控制(radio resource control，RRC)层，业务数据适配协议(service data adaptation protocol，SDAP)层，分组数据汇聚层协议(packet data convergence protocol，PDCP)层，无线链路控制(radio link control，RLC)层，媒体接入控制(media access control，MAC)层，以及物理层(physical layer，PHY)等逻辑功能协议层。下一代基站(例如gNB)对传统基站架构进行了演进。图2为一种5G系统的示意性框图，该系统200包括5GC和NG-RAN，在NG-RAN中，基站gNB可以由集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU)构成，CU和DU架构可以理解为是对传统接入网中的基站的功能进行拆分，传统基站的一部分功能部署在CU，其余功能部署在DU，多个DU可共用一个CU以节省成本并易于网络扩容，CU和DU之间通过F1接口进行信息交互。对于由CU和DU构成的gNB，对于外部其他网元而言是一个基站。
如图3所示的一种5G系统的示意性框图中，在gNB中，集中式单元CU还可以划分为CU控制面(CU control plane,CU-CP)和CU用户面(CU user plane，CU-CP)。其中，CU-CP负责控制面功能，主要包含RRC和PDCP控制面部分(PDCP-C)，PDCP-C主要负责控制面数据的加解密，完整性保护，以及数据传输等；CU-UP负责用户面功能，主要包含SDAP和PDCP-U，其中SDAP主要负责将核心网的数据进行处理并将流(flow)映射到无线承载，PDCP-U主要负责数据面的加解密，完整性保护，头压缩，序列号维护，以及数据传输等。其中，CU-CP和CU-UP通过E1接口连接，CU-CP代表gNB通过Ng接口和核心网连接，CU-CP通过F1-C(F1控制面)接口和DU连接，CU-UP通过F1-U(F1用户面)接口和DU连接。还有一种设计是PDCP-C和PDCP-C都在CU-UP，RRC在CU-CP (图3中未示出)。
基于基站的CU-DU架构或其衍生架构，还存在如下问题中的至少一种：
当前针对UE的寻呼流程尚不完善，可能导致寻呼UE失败；
当UE进入非激活态时，CU通知DU释放该UE的UE上下文，但该机制尚存在缺陷；以及，
在UE接入网络的过程中，存在准入控制机制不完善而导致系统可能出错的问题。
发明内容
本申请提供一种通信方法，设备及其系统等，以解决基于CU-DU的基站架构或其衍生架构中存在的针对终端设备的寻呼流程尚不完善，可能导致寻呼UE失败的问题。
第一方面，本申请实施例提供了一种通信方法，该通信方法运行在通信系统中，该通信系统包括集中式单元和分布式单元，在该通信系统运行时，可执行如下示例性的操作：
集中式单元CU向分布式单元DU发送寻呼消息，该寻呼消息中携带表明该寻呼是基于核心网产生的寻呼或基于无线接入网产生的寻呼的指示信息；该分布式单元收到该寻呼消息，可寻呼消息中携带的该指示信息获知该寻呼是基于核心网产生的寻呼或该寻呼是基于无线接入网产生的寻呼。通过该方案，使得DU能够获知收到的寻呼消息是来自于核心网还是来自于RAN侧(比如CU产生的寻呼)，从而能够在空口正确的广播该寻呼。
根据第一方面的一种可选设计包括：该指示信息是源于核心网的被寻呼终端设备的标识的信息，则该指示信息被用于表明该寻呼是基于核心网产生的寻呼，并被用于使得该分布式单元获知该寻呼是基于所述核心网产生的寻呼；或者，该指示信息是无线接入网配置的被寻呼终端设备的标识的信息，则该指示信息被用于表明该寻呼是基于无线接入网产生的寻呼，并被用于使得该分布式单元获知该寻呼是基于该无线接入网产生的寻呼。通过该方案，可以通过在CU和DU之间的接口上传输的寻呼消息中携带的源于核心网的被寻呼终端设备的标识的信息来表示该寻呼是基于核心网产生的寻呼，或者，可以通过在CU和DU之间的接口上传输的寻呼消息中携带的无线接入网侧配置的被寻呼终端设备的标识的信息(或者其他能够标识该终端的信息)来表示该寻呼是基于无线接入网产生的寻呼。
根据第一方面的一种可选设计包括：该寻呼消息中还包括被寻呼终端设备的标识的信息，或者能够标识该被寻呼终端设备的信息。该寻呼消息中携带的该指示信息可用来指示或者表明所涉及的寻呼是基于核心网产生的寻呼或该寻呼是基于无线接入网产生的寻呼，该分布式单元收到该指示信息后，即可获知所涉及的寻呼是基于核心网产生的寻呼或所涉及的寻呼是基于无线接入网产生的寻呼，示例性的，如果该指示信息指示或者表明该寻呼是基于所述核心网产生的寻呼，那么该分布式单元可以根据该指示信息获知所涉及的寻呼是基于所述核心网产生的寻呼；或者，如果该指示信息指示或者表明该寻呼是基于无线接入网产生的寻呼，分布式单元收到指示信息后，即可获知该寻呼是基于无线接入网产生的寻呼。
根据第一方面的一种可选设计包括：该寻呼消息中包括被寻呼终端设备的标识的信息；该指示信息表明该寻呼是基于核心网产生的寻呼或基于无线接入网产生的寻呼，该指示信息被用于使得该分布式单元获知该寻呼是基于核心网产生的寻呼或该寻呼是基于无线接入网产生的寻呼，包括：该指示信息表明该被寻呼终端设备的标识的信息是源于核心网的， 则该指示信息表明该寻呼是基于该核心网产生的寻呼，并被用于使得该分布式单元获知该寻呼是基于核心网产生的寻呼；或者，该指示信息表明该被寻呼终端设备的标识的信息是无线接入网配置的，则该指示信息表明该寻呼是基于该无线接入网产生的寻呼，并被用于使得该分布式单元获知该寻呼是基于该无线接入网产生的寻呼。通过该方案，CU和DU之间传输的寻呼消息中携带指示信息，通过该指示信息，CU可以告知DU寻呼消息中携带的UE的标识的信息是来源于核心网的还是在RAN侧配置的，从而使得DU能够获知该寻呼是源于核心网产生的寻呼，还是源于RAN侧产生的寻呼。
根据第一方面的一种可选设计包括：该指示信息中包括：源于核心网的被寻呼终端设备的标识的信息或无线接入网配置的被寻呼终端设备的标识的信息；当该指示信息中包括源于核心网的被寻呼终端设备的标识的信息时，则该指示信息表明该寻呼是基于该核心网产生的寻呼，并被用于使得该分布式单元获知该寻呼是基于该核心网产生的寻呼；或者，当该指示信息中包括无线接入网配置的被寻呼终端设备的标识的信息时，则该指示信息表明该寻呼是基于该无线接入网产生的寻呼，并被用于使得该分布式单元获知该寻呼是基于该无线接入网产生的寻呼。通过该方案，CU和DU之间的寻呼消息中可以包含两个信元，一个信元用于携带源于核心网的被寻呼终端设备的标识的信息，另一个信元用于携带无线接入网配置的被寻呼终端设备的标识的信息，在方法执行时，可择一发送这两个信元的内容。
根据第一方面的一种可选设计包括：该分布式单元具有如下中至少一种：无线链路控制层，媒体接入控制层，以及物理层；该集中式单元具有如下中至少一种：无线资源控制层，业务数据适配协议层，以及分组数据汇聚层协议层；该分布式单元和该集中式单元属于该无线接入网，是该无线接入网中的通信节点；该分布式单元和该集中式单元可以构成一个逻辑意义上的基站。
第二方面，本申请实施例提供了一种通信方法，该通信方法运行在通信系统中，以有助于解决在UE接入网络的过程中，存在准入控制机制不完善而导致系统可能出错的问题。该通信系统包括集中式单元和分布式单元，在该通信系统运行时，可执行如下示例性的操作：集中式单元拒绝终端设备的接入请求；该集中式单元向分布式单元发送指示信息；该指示信息用于表明该分布式单元需要删除该终端设备的上下文信息。
根据第二方面的一种可选设计包括：该指示信息包含：拒绝该终端设备接入的指示和/或拒绝该终端设备接入的原因的信息。
根据第二方面的一种可选设计包括：该集中式单元接收来自于该分布式单元发送的关于允许该终端设备接入的通知消息。
第三方面，本申请提供了一种通信设备，该通信设备包括：至少一个处理器和通信接口，该通信接口用于该通信设备与其他通信设备进行信息交互，当程序指令在该至少一个处理器中执行时，使得通信设备实现第一或第二方面及其各种可选的设计中在集中式单元或分布式单元的功能。
第四方面，本申请提供了一种计算机程序产品，该计算机程序产品具有程序指令，当该程序指令被直接或者间接执行时，使得如第一或第二方面及其各种可选的设计中在集中式单元或分布式单元上的功能得以实现。
第五方面，本申请提供了一种计算机程序存储介质，该计算机程序存储介质具有程序指令，当该程序指令被直接或者间接执行时，使得如第一或第二方面及其各种可选的设计 中在集中式单元或分布式单元上的功能得以实现。
第六方面，本申请提供了一种芯片系统，该芯片系统包括至少一个处理器，当程序指令在该至少一个处理器中执行时，使得如第一或第二方面及其各种可选的设计中在集中式单元或分布式单元上的功能得以实现。
第八方面，本申请提供了一种通信系统，该通信系统包括如第三方面所述的通信设备。
附图说明
图1是本申请实施例提供的一种5G系统的示意性框图；
图2是本申请实施例提供的一种5G系统的示意性框图；
图3为本申请实施例提供的一种5G系统的示意性框图；
图4为本申请实施例提供的一种通信系统及方法的示意图；
图5为本申请实施例提供的一种通信系统及方法的示意图；
图6为本申请实施例提供的一种通信系统及方法的示意图；
图7为本申请实施例提供的一种通信系统及方法的示意图；
图8为本申请实施例提供的一种通信设备的示意性框图。
具体实施方式
首先对本申请各实施例出现的术语中具有共性的部分进行一般性描述。
本申请中的术语“第一”、“第二”等仅是为了区分不同的对象，“第一”、“第二”并不对其修饰的对象的实际顺序或功能进行限定。例如，“第一指示”和“第二指示”中的“第一”、“第二”，仅仅是为了区分这两者是不同的指示，“第一”和“第二”本身并不对其实际先后顺序或者功能进行限定。本申请中出现的“示例性的”，“示例”，“例如”，“可选的设计”或者“一种设计”等表述，仅用于表示举例子、例证或说明。本申请中被描述为“示例性的”，“示例”，“例如”，“可选的设计”或者“一种设计”的任何实施例或设计方案都不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用这些词旨在以具体方式呈现相关概念。本申请中出现的术语“上行”和“下行”，用于在特定场景描述数据/信息传输的方向，比如，“上行”方向一般是指数据/信息从终端设备向网络侧传输的方向，或者分布式单元向集中式单元传输的方向，“下行”方向一般是指数据/信息从网络侧向终端设备传输的方向，或者集中式单元向分布式单元传输的方向，可以理解，“上行”和“下行”仅用于描述数据/信息的传输方向，该数据/信息传输的具体起止的设备都不作限定。
本申请中出现的术语“和/或”，仅仅是一种描述对象之间的关联关系，表示对象间可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本申请中字符“/”，如无特别说明，则一般表示前后对象之间是一种“或”的关系。本申请中出现的字符“-”，一般用来表示该字符前后的对象两者之间具有对应/关联/映射/协作关系。例如，对于表述“分组数据汇聚协议处理的用户面功能(PDCP-U)”中“-”，可理解为表示PDCP功能中对应的用户面部分功能。
本申请中出现的类似于“项目包括如下中至少一种：A，B，以及C”表述的含义，如无特别说明，通常是指该项目可以为如下中任一个：A；B；C；A和B；A和C；B和C；A，B和C；A和A；A，A和A；A，A和B；A，A和C，A，B和B；A，C和C；B和B，B，B和 B，B，B和C，C和C；C，C和C，以及其他A，B和C的组合。以上是以A，B和C共3个元素进行举例来说明该项目的可选用条目，当该表达为“项目包括如下中至少一种：A，B，……，以及X”时，即该表达中具有更多元素时，那么该项目可以适用的条目也可以按照前述规则获得。
在本申请中可能出现的对各种消息/信息/设备/网元/系统/装置/动作/操作/流程/概念等各类客体进行了赋名，可以理解的是，这些具体的名称并不构成对相关客体的限定，所赋名称可随着场景，语境或者使用习惯等因素而变更，对本申请中技术术语的技术含义的理解，应主要从其在技术方案中所体现/执行的功能和技术效果来确定。
在本申请中，终端设备可以包含如下形式：用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统，例如，5G网络中的终端设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。终端设备还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，终端设备以UE为例进行实施例方案的描述，但可以理解的是，本申请实施例中终端设备并不局限于UE。
本申请实施例中CU和DU也不限于NR gNB，还可能包括LTE基站划分为CU和DU，或者CU还进一步划分为CP和UP两部分。当为LTE基站时，所述协议层不包含SDAP层。
本申请实施例描述的网络架构以及业务场景是为了便于读者清楚理解本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
在RAN侧，UE一般具有RRC连接态(RRC-connected status)和RRC空闲态(RRC-idle status)，还可以具有RRC非激活态(RRC-inactive status)，也可以称RRC非激活态为第三态。当UE处在非活跃状态(例如，终端没有上行和/或下行数据发送超过设定时间)时，基站可以通过RRC消息通知UE进入RRC非激活态。UE接入小区后，在基站为该UE建立相应的UE上下文，当UE的RRC状态发生改变时，基站随之相应处理该UE的UE上下文。例如，UE从RRC连接态转变为RRC空闲态，相应的，基站可以释放该UE的UE上下文；当UE从RRC连接态转换为RRC非激活态时，一种可能的处理是保持或者悬挂该UE的UE上下文，比如，在基站和/或UE保留该UE在RAN侧的UE上下文。
对于具有CU-DU架构和/或具有后续基于CU-DU衍生架构的基站而言，其中的CU一般具有RRC层，该RRC层具有管理UE的RRC状态的功能。对于处于RRC空闲态以及RRC非激活态的UE，分别具有基于核心网的寻呼(CN-based paging)以及基于无线接入网的寻呼 (RAN-based paging)两种情况。特别地，还有一种可能的情况是，UE认为自己处在RRC非激活态，但实际上网络侧当时获知的情况是该UE处于RRC空闲态，则网络侧还会通过基于核心网的寻呼对该UE进行寻呼。此处所称的基于核心网的寻呼可以认为是核心网发起的寻呼，此处所称的基于无线接入网的寻呼可以认为是在无线接入网发起的寻呼，比如无线接入网中的基站，或者CU或者CP等网络节点发起的寻呼。对于基于核心网的寻呼，一般需要通过基站进行转发。此处核心网发起的寻呼和基站发起的寻呼的一个区别即在于寻呼的发起方不同。对于UE而言，需要区分收到的寻呼是基于核心网的寻呼，还是基于RAN的寻呼。对于核心网发起的寻呼，UE的最终的非连续接收周期(discontinuous reception cycle，DRX cycle)可以为：核心网发送的UE特定的DRX周期(UE specific DRX cycle)，以及小区广播的默认DRX周期(default DRX cycle)中取较小值(还可以是对应于该取得的较小值的一个值)。对于基站发起的寻呼，UE的最终的DRX cycle可以为：核心网发送的UE specific DRX cycle，UE接收到的RRC消息中携带的RAN侧UE DRX cycle以及小区广播的default DRX cycle中取较小值(还可以是对应于该取得的较小值的一个值)。一种特殊的情况是，如果其中个别DRX cycle不存在，则剩余的1个或多个DRX cycle取较小值。
CU给DU发送的寻呼消息可以携带寻呼DRX的信元，该信元可以是取如下两者中的较小者：UE specific CN DRX cycle和UE specific RAN DRX cycle。但CU给DU的发送的寻呼消息并未区分该寻呼是源于CN的寻呼还是源于RAN的寻呼，也未给出UE进入RRC非激活态时如何处理寻呼。
另外，当UE进入非激活态时，一般的，CU通知DU释放该UE的UE上下文，但该机制尚存在缺陷，比如DU是否可以干预CU关于释放UE上下文的决策，又比如，DU收到释放UE上下文的通知后，还未把CU发给UE的RRC连接释放消息转发给UE，而此时UE有上行数据到达(UL data arrival)，如UE向基站(DU和/或CU)发送调度请求(scheduling request，SR)或缓冲区状态报告(buffer status report，BSR)，则可能导致系统出错。
还比如，基于CU-DU的RAN架构，UE请求和RAN建立RRC连接，一般的，基站中的DU或者CU可以拒绝UE的该建立RRC连接的请求。如，UE发送消息3(MSG3)以请求建立RRC连接(可以是新建、恢复或重建RRC连接中的任一种)，DU将MSG3中的RRC消息发送给CU，同时MSG3中携带为该UE分配的小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)或临时小区无线网络临时标识(Temp CRNTI)，以及DU发给CU的RRC信息(DU to CU RRC information)，该DU发给CU的RRC信息中包含该DU为该UE配置的信令无线承载1(signaling radio bearer，SRB1)的层1(L1)和/或层2(L2)参数，例如NR中所述RRC信息包含小区组配置CellGroupConfig。如果该CU收到该DU发送的DU to CU RRC information，则判断该DU允许该UE接入，否则认为DU不允许该UE接入。在上述UE请求建立RRC连接的过程中，可以由CU对UE的接入进行准入控制，例如，在CU拒绝UE接入RAN的情况下，CU可以向UE发送响应，该响应是针对UE向基站发送的MSG3中携带的RRC消息作出，该响应用于指示UE期望建立RRC连接的请求被拒绝。一般的，RRC消息被携带在MSG3中的RRC容器(RRC Container)中发给DU，但DU并不解析该RRC Container中的内容是接受RRC连接建立请求还是拒绝RRC连接建立请求。此时，若DU允许UE接入，并且系统默认设置中CU也允许接入的话，则DU将为UE建立用于传输SRB1的协议栈实体(例如RLC实体，MAC的逻辑信道等)，并为该UE建立上下文，该UE的上下文中包含UE的C-RNTI，F1接口ID(例如DU UE F1AP ID和/或CU UE F1SP ID)；另外，DU或 者CU还可以为该UE后续的RRC消息(例如MSG5)进行调度。可选地，存在第一种情况包括：DU在发送消息3之后启动定时器，当该定时器超时后，DU仍然未收到CU发送的UE上下文建立请求消息(UE context setup request)，则DU可以删除相关配置和UE上下文。或者，存在第二种情况包括：DU读取msg3中包含的RRC消息的类型，根据RRC消息类型判断CU是否拒绝或者是否将拒绝UE发起的RRC连接/重建/恢复请求，从而决定在DU是否删除所述配置和/或UE的上下文。对于第一种情况，如果定时器的设置不合理将导致系统出错。例如，若该定时器设置时长较小，则DU删除了所述配置和/或UE上下文后，DU再收到来自CU发送的UE上下文建立请求消息，这种情况下，由于DU已经删除了所述配置和/或UE上下文，将导致UE上下文建立不成功。对于第二种情况，则不符合5G RAN系统中RRC层在CU的假设前提。根据本发明实施例，如果CU拒绝UE接入，则CU需要显示的指示DU，以使得DU删除上述配置和UE上下文。
以下结合附图及实施例对本申请涉及的技术方案进行阐述。
如图4所示，本申请实施例提供了一种通信系统及其运行方法400，以解决基于CU-DU架构的寻呼机制不完善的问题，比如，寻呼处于RRC非激活态的UE时当前的寻呼机制可能导致系统出错的情况。
有鉴于此，本实施例的主要思想之一可表述为：CU向DU提供指示信息，该指示信息用于表明一个寻呼是基于核心网的寻呼和/或基于RAN的寻呼，以便DU能够获知并通知UE该寻呼是基于核心网的寻呼或基于RAN的寻呼。如图4所示，系统400包括CU，DU，以及UE，其中，CU和DU作为RAN架构中的功能节点。系统400可按照如下示例性方式运行：
操作401：CU将用于指示寻呼类型的指示信息发送给DU。
该用于指示寻呼类型的指示信息可以是CU产生的，该寻呼类型的指示信息可以携带在CU发给DU的F1应用层协议(F1application protocol，F1AP)的寻呼消息中。
根据步骤401的可选设计1，包括：该用于指示寻呼类型的指示信息是源于核心网的被寻呼UE的标识的信息，则该指示信息被用于表明涉及的寻呼是基于核心网产生的寻呼，并被用于使得该分布式单元获知该寻呼是基于核心网产生的寻呼；或，该指示信息是无线接入网配置的被寻呼UE的标识的信息，则该指示信息被用于表明该寻呼是基于该无线接入网产生的寻呼，并被用于使得该分布式单元获知该寻呼是基于无线接入网产生的寻呼。其中，可选的，该指示信息从功能上可以称之为恢复标识(resume ID)，或者是基于该恢复标识衍生的其他的标识信息，该恢复标识可被用于处在RRC非激活态的UE，该恢复标识还可被用于表示涉及的寻呼是基于RAN产生的寻呼(RAN-based paging)，该恢复标识也还可以用于获取UE的上下文。
根据可选设计1，一种示例性的实现包括：CU给DU发送的F1AP的寻呼消息中可以携带UE标识索引值(UE Identity Index value)和UE寻呼标识(UE Paging identity)这两个信元(information element，IE)。其中，UE Identity Index value可以是UE_ID，该UE_ID可通过公式：UE_ID＝IMSI mod 1024获得，UE寻呼标识可以是核心网S-TMSI或IMSI，其中，S-TMSI是源于核心网的SAE临时移动用户标识(SAE temporary mobile subscriber identity)，IMSI是UE的国际移动用户识别码(international mobile subscriber identity)。可以理解，NR系统中核心网的UE寻呼标识可以是其他名称，本文不做限制。上述这2个值可用于计算寻呼帧(paging frame，PF)和寻呼时机(paging occasion，PO)。当涉及寻呼是基于核心网产生的寻呼(CN based paging)时，CU向DU提供的UE的标识信息(比如UE的寻呼标识) 是源于核心网的，该UE的寻呼标识信息可以是核心网S-TMSI和/或IMSI；当涉及寻呼是基于RAN侧产生的寻呼(RAN-based paging)时，CU提供的该UE的寻呼标识信息是resume ID或者是一个在RAN侧产生的用于寻呼过程的UE标识的信息。可选的，所述UE寻呼标识可以是DU主动提供给CU的，或者基于CU请求发送给CU的。DU根据预设的配置，识别其收到的是核心网产生的UE的寻呼标识的信息(比如可以是核心网TMSI或IMSI)，还是在RAN侧产生的UE的寻呼标识信息(比如可以是resume ID或者是一个在RAN侧产生的用于寻呼过程的UE标识的信息)。可选的，DU可以根据寻呼类型确定UE的非连续接收周期。可选的，当DU识别是基于核心网的寻呼时，DU确定UE的最终的非连续接收周期可以包括：核心网发送的UE特定的DRX周期，以及小区广播的默认DRX周期中取较小值(还可以是对应于该取得的较小值的一个值)。可选的，当DU识别是基于无线接入网的寻呼时，DU确定UE的最终的DRX cycle可以包括：核心网发送的UE specific DRX cycle，UE接收到的RRC消息中携带的RAN侧UE DRX cycle以及小区广播的default DRX cycle中取较小值(还可以是对应于该取得的较小值的一个值)。一种可能的情况是，如果其中个别DRX cycle不存在，则剩余的1个或多个DRX cycle取较小值。
DU收到上述F1AP的寻呼消息后，可选的，在操作402中，DU将用于指示寻呼类型的指示信息发送给UE，示例性的，可以将该UE的寻呼标识的信息放入广播寻呼消息中(比如携带在信元PagingRecord中)在空口广播，和/或，在给UE的广播寻呼消息中携带指示以使得UE能够获知该寻呼是基于RAN侧产生的寻呼，还是基于CN产生的寻呼，例如，可以在PagingRecord里面给出是否为RAN based paging的指示，比如0表示CN based paging，1表示RAN based paging。可选的，UE可以基于所述指示判断是基于核心网的寻呼，还是基于无线接入网的寻呼。和DU类似地，UE可以根据寻呼类型确定最终的非连续接收周期。 根 据操作401的可选设计2，包括：CU向DU发送的寻呼消息中包括被寻呼UE的标识的信息；则，当该用于指示寻呼类型的指示信息表明涉及的寻呼是基于核心网产生的寻呼或基于无线接入网产生的寻呼，该指示信息被用于使得DU获知涉及的寻呼是基于核心网产生的寻呼或该寻呼是基于无线接入网产生的寻呼的具体过程，包括：
该指示信息指示了该被寻呼UE的标识的信息是源于核心网时，则表明该寻呼是基于核心网产生的寻呼，该指示信息并被用于使得DU获知涉及的寻呼是基于核心网产生的寻呼；或者，该指示信息表明该被寻呼UE的标识的信息是无线接入网配置的，则表明寻呼是基于无线接入网产生的寻呼，该指示信息被用于使得DU获知该寻呼是基于无线接入网产生的寻呼。
可选地，CU在给DU发送的F1AP寻呼消息中除了UE寻呼标识(UE Paging identity)信元，还可以设置显示的信元用于指示，例如该指示可以是RAN based Paging指示，当该指示取值为0时表示所涉及的寻呼是基于核心网产生的寻呼，反之当该指示取值为1时则表示所涉及的寻呼是基于无线接入网产生的寻呼。或者该指示可以是CN based Paging指示，当该指示取值为0时表示该寻呼是基于无线接入网产生的寻呼，反之当该指示取值为1时表示该寻呼是基于核心网产生的寻呼。
根据操作401的可选设计3，包括：该用于指示寻呼类型的指示信息中包括：源于核心网的被寻呼终端设备的标识的信息或无线接入网配置的被寻呼终端设备的标识的信息。可选的，该指示信息中可以设置两个信元，一个信元用于携带该源于核心网的被寻呼终端设备的标识的信息，另一个信元用于携带该无线接入网配置的被寻呼终端设备的标识的信息， 但发送该指示信息时，可以择一发送这两个信元所携带的信息。比如，当所述指示信息中包括源于核心网的被寻呼终端设备的标识的信息时，则所述指示信息表明所述寻呼是基于所述核心网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述核心网产生的寻呼；或者，当所述指示信息中包括无线接入网配置的被寻呼终端设备的标识的信息时，则所述指示信息表明所述寻呼是基于所述无线接入网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述无线接入网产生的寻呼。
示例性的，通过CU向DU发送的F1AP的寻呼消息中的一个信元携带CN侧配置的UE的标识信息，表明该寻呼是基于CN侧产生的寻呼，或者，通过CU向DU发送的F1AP的寻呼消息中的另一个信元携带RAN侧配置的UE的ID信息，表明该寻呼是基于RAN侧产生的寻呼。在一种可选设计中：如果是基于CN产生的寻呼(CN based paging)，则CU发给DU的F1AP的寻呼消息中包含UE寻呼标识UE Paging identity可以携带CN侧分配的UE的标识信息；如果是基于RAN侧产生的寻呼(RAN-based paging)，则CU发给DU的F1AP的寻呼消息中包含新设置的信元，例如该信元是UE无线接入网寻呼标识(UE Paging identity for RAN based Paging)，该信元可以携带RAN侧分配的UE的标识信息。
又例如，在CU给DU发送的F1AP寻呼消息中可另行设置新的IE，通过该新的IE使CU向DU提供resume ID或者是在RAN侧产生的用于寻呼过程的UE标识的信息，以表示涉及的寻呼类型是RAN based paging，示例性的，该新的IE可以是UE Paging Identity for RAN based paging。
DU收到含有该新的IE的F1AP的寻呼消息后，可选的，在操作402中，DU可以将收到的resume ID或者该RAN侧产生的用于寻呼过程的UE标识的信息(比如，UE Paging Identity for RAN based paging)携带在空口广播的寻呼消息中发送给UE(比如在信元PagingRecord中)，或者，在给UE的广播寻呼消息中携带指示以使得UE能够获知该寻呼是基于RAN侧产生的寻呼还是基于CN产生的寻呼，例如，可以在PagingRecord里面给出是否为RAN based paging的指示，比如0表示CN based paging，1表示RAN based paging。这样，使得操作402得以执行DU将用于指示寻呼类型的指示信息发送给UE。
需要说明的是，本操作401为可选操作，也就是说，CU也可以不发送寻呼类别的指示信息给DU，具体的寻呼类型由DU自主判断。比如，对于RAN-based paging和CN based paging这两种情况，在CU和DU之间可以都使用源于核心网的UE的标识信息，但是DU在空口对CN based paging和RAN based paging这两种情况进行区分，可选的，在操作402中，在DU发送的广播寻呼消息中，携带是否为RAN based paging的指示，示例性的，可以在信元PagingRecord里面给出是否为RAN based paging的指示比特，当该比特取值为0时，表示该寻呼是CN based paging，当该比特取值为1时，表示该寻呼是RAN based paging。可以理解，具体取值代表的含义可以有不同的方式，比如，当该比特取值为1时，表示该寻呼是CN based paging，当该比特取值为0时，表示该寻呼是RAN based paging。
可以理解，对于系统400中的CU可以按照图3的方式进一步划分成CP和UP，对于CP和UP进一步分离的架构，那么系统400中前述CU的功能可以由CP来实现，当然，系统400中前述CU的功能也可以放在UP中实现。
可以理解，前述任一设计中所称的RAN侧配置的UE的标识的信息，也可以在RAN侧配置的其他可用于标识UE的信息，只要配置的UE的相关信息能够标识这个UE，或者有助于找到该UE的上下文，或者有助于标识针对该UE的寻呼类型。可以理解，本文所称的“RAN 侧配置”，即可是RAN侧中的CU执行该配置，也可以是DU执行该配置，或者是CU和DU通过协商来完成配置，比如，针对RAN侧发起的寻呼，由CU或由DU或由CU结合DU共同来为该寻呼配置一个能够标识该UE的信息，以有助于在DU侧能够识别该寻呼的类型是核心网发起的寻呼，还是在无线接入网发起的寻呼。
如图5所示，本申请实施例还提供了一种通信系统及其运行方法500，以有助于解决当UE进入非激活态时，CU通知DU释放该UE的UE上下文的机制中尚存在的缺陷。该系统500具有CU和DU，当该系统500运行时，通过CU和DU之间交互消息，以执行如下示例性的方法500：
CU给DU发送用于释放UE上下文的消息，比如该消息可以是UE上下文释放消息UE context release message)，该消息中包含用于表示该UE进入RRC非激活态(UE enter into inactive)的原因值信息；或者，CU给DU发送用于释放UE上下文的消息，比如该消息可以是UE上下文释放消息UE context release message)，在该消息中可以携带发送给UE的用于释放RRC连接的消息，例如RRC连接释放消息(RRC connection release message)；或者，CU也可以在其他F1AP消息，例如DL RRC message transfer消息中携带RRC connection release，该消息中也可以包含原因值(例如UE enter into inactive)和/或RRC消息类型。那么DU后续收到CU发送的UE context release消息时，则可以获知UE进入RRC非激活态，故要释放该UE的上下文。另一种可能的情况，DU获知UE进入RRC非激活态，保留UE上下文，挂起无线信令和/或无线数据承载。
一种可选设计包括：对于出现上行数据到达(UL data arrival)的场景：DU尚未将CU发送的RRC释放消息转发给UE时，收到UE发送的SR/BSR，DU获知UL data arrival。DU通知CU拒绝释放UE上下文，可选的，通知消息中包含原因值为出现上行数据到达(UL data arrival)。可选的，在此之前，DU发送通知消息中可携带DU判断UE进入非激活态的信息，通知消息的实现方式，可以是active/inactive指示，或者inactive timer到时的指示。若DU在发送通知消息通知CU UE进入inactive态后，尚未收到CU的回复，就发现有上行数据到达(UL data arrival)，则DU通知CU该情况(即UL data arrival)，以便CU及时作出正确的决策，例如，CU可以决策UE不能进入RRC非激活态。
一种可选设计包括：对于出现下行数据到达(DL data arrival)的场景：CU给DU发送UE context release和/或RRC释放消息后，出现下行数据到达(DL data arrival)的情况，可选的，CU判断DU可能存在尚未释放UE上下文和/或转发RRC释放消息的情况，可选的，CU将发送UE context release cancel消息和/或DL RRC message transfer cancel消息给DU，该消息中包含原因值(例如DL data arrival)，可选的，该消息还可包含paging信息(例如resume ID，paging DRX，UE Identity Index value，Paging priority，以及UE paging identity中的至少一个，或者前面操作401的三种可选设计中包含的信元。DU如果取消发送RRC释放消息和/或未释放UE上下文，则通知CU未释放UE上下文或者UE未进入RRC非激活态。如果出现DU已经转发了RRC消息且释放了UE上下文的情况，则可以基于paging信息直接发起RAN-based paging。
对于CU具有CP-UP架构时，一种可选设计包括：CU中的CP(CU-CP)给DU和/或CU中的UP(CU-UP)发送UE context release消息，该消息中包含原因值UE enter into inactive。或者CU-CP也可能在另一条F1AP消息，例如DL RRC message transfer消息中携带RRC connection release，该消息中也可以包含原因值UE enter into inactive或者RRC消息类型。那 么后续DU收到CU发送的UE context release消息则可以推测是由于UE enter into inactive才需要释放UE上下文。另一种可能的情况，DU获知UE进入RRC非激活态，保留UE上下文，挂起无线信令和/或无线数据承载。
一种可选设计包括：对于出现上行数据到达的情况(UL data arrival)：可以参考前述CU-DU架构的描述，CU的功能可以在CP中实现。
一种可选设计包括：对于出现下行数据到达的情况(DL data arrival):假设CU-UP通知CU-CP关于UE处于非激活状态的信息，CU-UP可通过CU-CP提供的timer到时间来判定UE是否进入非激活态。若CU-UP尚未收到CU-CP发送的UE进入inactive态或UE context release指示，则：
可选操作1：CU-UP发送DL data arrival指示给CU-CP，例如在E1接口消息中包含E1接口UE标识例如gNB-CU-UP UE E1APID，DL data arrival指示等。CU-CP收到CU-UP的DL data arrival指示消息后，后续操作可参考前述CU-DU架构的描述，CU的功能在CU-CP实现。当CU-CP通知DU后，且获知UE未进入inactive态时，CU-CP通知CU-UP可以发送下行数据DL data给DU。
可选操作2：CU-UP直接将DL data arrival指示或下行数据DL data发送给DU，DU收到DL data arrival或DL data，则取消发送RRC连接释放消息给UE，可选的，DU通知CU-CP未释放UE上下文或者UE未进入inactive态，通知消息中还可以包含DL data arrival指示。
一种可选设计包括，CU监视下行传输状态，DU监视上行传输状态并将上行传输状态为active/inactive上报给CU。其中DU决定上行传输状态时可能使用定时器，该定时器可以是DU自行设置，也可以是CU提供定时器给DU。DU上报上行传输状态时，可以按照UE粒度、PDU会话粒度、slice粒度或DRB粒度。针对UE粒度，DU可以上报例如UE标识和active/inactive指示。针对PDU会话或slice粒度或DRB粒度，DU可以上报例如UE标识，PDU会话标识/slice标识/DRB标识，以及对应PDU会话/slice/DRB的active/inactive状态。可选的，定时器也可以是PDU会话/slice/DRB粒度的，即每个PDU会话标识/slice标识/DRB标识分别对应一个定时器。
一种可选的设计包括，DU监视上行传输状态和下行传输状态，并上报上行传输状态和下行传输状态给CU。其中定时器可以即针对上行，又针对下行。或者上行定时器针对上行传输，下行定时器针对下行传输。所述定时器可以是DU自行设置，也可以是CU提供定时器给DU。特别地，DU上报上行传输状态时，可以按照UE粒度、PDU会话粒度、slice粒度或DRB粒度。DU上报下行传输状态时，也可以按照UE粒度、PDU会话粒度、slice粒度或DRB粒度。
本申请实施例还提供了一种通信方法，该通信方法运行在通信系统中，该通信系统包括集中式单元和分布式单元，在该通信系统运行时，可执行如下示例性的操作：集中式单元拒绝终端设备的接入请求；该集中式单元向分布式单元发送指示信息；该指示信息用于表明该分布式单元需要删除该终端设备的上下文信息。其中，一种可选设计包括：该指示信息包含：拒绝该终端设备接入的指示和/或拒绝该终端设备接入的原因的信息。其中，一种可选设计包括：该集中式单元接收来自于该分布式单元发送的关于允许该终端设备接入的通知消息。通过该系统及方法的运行，有助于解决现有技术中UE进行接入网络时，存在准入控制机制不完善而导致系统出错的问题。示例性的，以下结合附图6和附图7对本实施例作进一步说明。
如图6所示，本申请实施例提供了一种通信系统及方法600，该系统包括CU，DU以及UE这三个网络节点，其中CU和DU构成基站系统。如图6所示，该系统和方法600运行的一个示例包括：
可选操作601：UE向基站系统发送消息3。该消息3中可以包含RRCConnectionRequest，或RRCConnectionResumeRequest(或者可以是其他类似的消息，消息名称可以不同)，或者RRCConnectionRestablishmentRequest。
可选操作602：DU向CU发送消息3。可选的，DU收到UE发送的消息3后，DU向CU发送CU-DU接口消息，例如F1AP消息，该F1AP消息中可包含UE的消息3。可选的，上述F1AP消息还可包含DU给CU的容器(container)，其中携带UE的SRB1的L1/L2配置例如小区组配置CellGroupConfig。示例性的，上述F1AP消息可以为Initial UL RRC Message。一种可能的情况是，DU判断是否允许该UE的接入，若允许，则在F1AP消息中包含上述DU给CU的容器例如DU to CU RRC information，里面包含小区组配置；反之，若DU不允许该UE的接入，则上述F1AP消息不包含DU给CU的容器。从而，CU可以获知DU是否允许该UE的接入。
CU收到UE发送的消息3后，可以回复消息4(流程如图6所示可选操作603和604)。示例性的，CU判断是否允许UE的接入，若拒绝UE的接入，则消息4中包含与消息3中内容对应的，表示拒绝UE接入的RRC消息，例如RRCConnectionReject,RRCConnectionReestablishmentReject。可选的，CU向DU发送F1AP消息，其中携带拒绝指示和/或拒绝原因值，用于告知DU，CU拒绝了UE的接入，从而触发DU删除该UE的上下文(如图6所示可选操作603)。示例性的，DU删除该UE的上下文的动作包括如下中的至少一项：DU释放为UE分配的C-RNTI/Temp CRNTI，DU释放为UE预留的资源，DU删除该UE的L1/L2配置，以及DU释放为UE分配的DU UE F1AP ID。可选的，上述F1AP消息为DL RRC Message Transfer。可选的，CU决定拒绝UE的接入的原因可以为DU拒绝，或者CU自己拒绝。一种可能的情况是，若CU得知DU拒绝UE的接入，CU无需向DU发送拒绝指示；可选的，若CU得知DU允许UE的接入，而CU不允许UE的接入，CU需要向DU发送拒绝指示，从而通知DU删除该UE的上下文。
如图7所示，本申请实施例提供了一种通信系统及方法700，该系统包括CU，DU以及UE这三个网络节点，其中CU和DU构成基站系统。通过该系统及方法700的运行，有助于解决现有技术中UE进行接入网络时，存在准入控制机制不完善而导致系统出错的问题。如图7所示，该系统和方法700运行的一个示例包括：
可选操作701：UE向基站系统发送消息3。该消息3中可以包含RRCConnectionRequest，或RRCConnectionResumeRequest(或其他类似的消息，名称可能不一样)，或者RRCConnectionRestablishmentRequest。
可选操作702：DU向CU发送消息3。DU收到UE发送的上述消息3后，将该消息3发送给CU。可选的，DU向CU发送F1AP消息，该F1AP消息中包含UE的消息3。可选的，上述F1AP消息还包含DU给CU的容器(container)，其中携带UE的SRB1的L1/L2配置。示例性的，上述F1AP消息可以为Initial UL RRC Message。可选的，DU告知CU是否允许UE的接入。一种可能的情况是，DU判断是否允许该UE的接入，若允许，则在F1AP消息中包含上述DU给CU的容器；反之，若DU不允许该UE的接入，则上述F1AP消息不包含DU给CU的容器。从而，CU可以获知DU是否允许该UE的接入。
可选操作703：CU收到UE发送的消息3后，CU向UE回复消息4。可选的，CU判断是否 允许UE的接入，若拒绝UE的接入，则该消息4中可包含与消息3中内容对应的，表示拒绝UE接入的RRC消息，例如RRCConnectionReject,RRCConnectionReestablishmentReject。可选的，CU向DU发送F1AP消息，其中携带上述消息4。示例性的，上述F1AP消息可以是DL RRC Message Transfer。可选的，CU向DU发送拒绝指示和/或拒绝原因值，用于告知DU删除该UE的上下文。具体的，CU向DU发送F1AP消息，其中包含拒绝指示和/或拒绝原因值。示例性的，该F1AP消息为UE Context Release。具体的，DU删除该UE的上下文的动作包括如下中的至少一项：DU释放为UE分配的C-RNTI/Temp CRNTI，DU释放为UE预留的资源，DU删除该UE的L1/L2配置，以及DU释放为UE分配的DU UE F1AP ID。可选的，CU决定拒绝UE的接入的原因可以为如下至少一种：DU拒绝该UE接入，以及CU侧自身拒绝该UE接入。一种可能的情况是，若CU得知DU拒绝UE的接入，则CU无需向DU发送拒绝指示；若CU得知DU允许UE的接入，而CU不允许UE的接入，则CU需要向DU发送拒绝指示，从而通知DU删除该UE的上下文。
可以理解，前述各实施例中对操作/各种可选设计进行了顺序编号，但可理解的是，该顺序编号仅为了便于行文，并不意味着必须按照顺序编号来依次执行操作。
一种可选设计中，前述实施例中，CU-UP在物理上可以和CU-CP，DU分开部署，也可以集中部署。例如存在CU-CP，CU-UP，DU三个在物理上全部单独部署，或者CU-CP和DU在物理上集中部署，但是CU-UP单独部署，或者CU-CP和CU-UP在物理上集中部署，但是DU单独部署，或者CU-CP单独部署，CU-UP和DU集中部署等可能情况。
以上所示出的任一种设计，可以理解为针对特定场景或者特定技术问题而设计的技术方案，但并不能理解为实施本申请所记载技术内容所必须，其中的任一种设计可根据需要和其他设计相结合实施，以更有针对性的解决特定的客观技术问题。
一种可选设计中，在本申请实施例中，分布式单元DU具有RLC，MAC和PHY协议层的功能，集中式单元CU具有RRC，SDAP和/或PDCP协议层的功能，DU和CU所具有的协议层共同构成了基站所具有的RRC，SDAP，PDCP，RLC，MAC以及PHY或者RRC，PDCP，RLC，MAC以及PHY协议层架构设置。当然，在基站中对CU和DU之间的协议层划分也可以有其他的方式，举例如，DU具有MAC和PHY，则CU具有RRC，SDAP，PDCP和RLC或RRC，PDCP和RLC，此处不做限定。DU在物理上可以和射频系统为一个通信设备的两个部分从而实现两者集成在一起，所述DU和CU也可以物理上作为同属于一个通信设备的部分从而实现两者集成在一起，或者，射频系统和DU以及CU物理上也可以作为同属于一个网络节点的部分从而实现三者可以集成在一起。
可以理解的是，对于前述实施例所涉及的UE，CU，DU，CP，以及UP，可通过具有处理器和通信接口的硬件平台执行程序指令来分别实现其在本申请前述实施例中任一设计中涉及的功能，基于此，如图8所示出的，本申请实施例提供了一种通信设备800的示意性框图，所述通信设备800包括：
至少一个处理器801，可选包括通信接口802，该通信接口用于支持该通信设备800和其他设备进行通信交互；当程序指令在所述至少一个处理器801中执行时，本申请前述实施例任一设计中在如下任一设备上操作的功能得以实现：UE，CU，DU，CP以及UP。一种可选设计中，该通信设备800还可以包含存储器803，以存储实现上述设备功能所必须的程序指令或者程序执行过程中所产生的过程数据。可选的，该通信设备800还可以包含内部的互联线路，以实现该至少一个处理器801，通信接口802以及存储器803之间的通信交 互。该至少一个处理器801可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。例如，对于实施例中涉及的DU中PHY功能的全部或者部分的处理，或者涉及的F1口或者E1口上的全部或者部分的协议通信功能，可以在该至少一个处理器中设置专用电路/芯片来实现，当然也可以通过该至少一个处理器801中设置的通用处理器执行具有PHY功能，F1口或者E1口通信功能相关的程序指令来实现；又例如，对于本申请实施例涉及设备中的MAC层，RLC层，PDCP层，SDAP层以及RRC层的相关功能的全部或者部分处理，该至少一个处理器801可以包含通信处理芯片，通过执行MAC层，RLC层，PDCP层，SDAP层以及RRC层的相关功能的程序指令来实现。可以理解的是，本申请实施例描述的各种设计涉及的的方法，流程，操作或者步骤，能够以一一对应的方式，通过计算机软件，电子硬件，或者计算机软件和电子硬件的结合来一一对应实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件，比如，考虑通用性好成本低软硬件解耦等方面，可以采纳执行程序指令的方式来实现，又比如，考虑系统性能和可靠性等方面，可以采纳使用专用电路来实现。普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，此处不做限定。
该通信接口802，通常具有为两个通信对端之间执行进行信息交互的功能，对于通信对端之间执行的是有线形式的信息交互的情况，通信接口可以设计成接口电路，或者包含该接口电路的硬件模块，以支持通信对端之间进行的有线形式的通信交互，比如本申请中涉及的DU和CU之间的F1口，CP和UP之间的E1口的通信功能，可以采纳这种形式的接口设计；对于通信对端之间执行的是无线形式的信息交互的情况，通信接口可以是具有射频收发功能的接口电路，或者是包含该具有射频收发功能的接口电路的硬件系统，比如在DU和UE之间进行无线通信时，那么DU和UE的通信接口可以采纳这种设计。
可选的，对于CU，DU，CP或者UP的实现，也可以通过采用通用硬件平台(具有处理资源，存储资源)直接或者间接执行实施例相关设计的实现性程序指令来完成CU，DU，CP或者UP在本申请实施例各设计中的功能。一种实际部署方式可以是，CU，CP或者UP可以和核心网设备就近，或者协同部署，物理上可以分开也可以合一；CU，CP或者UP的功能也可以作为核心网设备的一部分。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品具有程序指令，当该程序指令被直接或者间接执行时，比如，在前述实施例中的通信设备800中被执行时，使得本申请实施例任一设计中在如下任一设备的功能得以实现：UE，CU，CP，UP以及DU。可以理解的是，所述程序指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述程序指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。程序指令被执行时，考虑到具体的网络设备中一般包括硬件层、运行在硬件层之上的操作系统层和/或中间层，与本申请实施例相关的程序指令被执行时，往往经过多层软件的调用和执行，因此该程序指令在硬件设备(通用处理电路或者专用处理电路)可以是一种间接的执行过程。
本申请实施例还提供了一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得如第一方面及其任一所述的设计中在如下任一设备上的功能得到实现：UE，CU，DU，CP，以及UP。
本申请还提供了如下实施例，需要说明的是，如下实施例的编号方式并未依据前文所述实施例的编号方式。
实施例1、一种通信方法，包括：集中式单元向分布式单元发送寻呼消息，所述寻呼消息中携带表明所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼的指示信息；
所述指示信息被用于使得所述分布式单元获知所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼。
实施例2、如实施例1所述的通信方法，包括：所述指示信息是源于核心网的被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是基于所述核心网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述核心网产生的寻呼；或者，所述指示信息是无线接入网配置的被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是基于所述无线接入网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述无线接入网产生的寻呼。
实施例3、如实施例1所述的通信方法，所述寻呼消息中还包括被寻呼终端设备的标识的信息；所述指示信息表明所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼，所述指示信息被用于使得所述分布式单元获知所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼，包括：所述指示信息表明所述寻呼是基于所述核心网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述核心网产生的寻呼；或者，所述指示信息表明所述寻呼是基于所述无线接入网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述无线接入网产生的寻呼。
实施例4、如实施例1所述的通信方法，所述寻呼消息中还包括被寻呼终端设备的标识的信息；所述指示信息表明所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼，所述指示信息被用于使得所述分布式单元获知所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼，包括：所述指示信息表明所述被寻呼终端设备的标识的信息源于核心网，则所述指示信息表明所述寻呼是基于所述核心网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述核心网产生的寻呼；或者，
所述指示信息表明所述被寻呼终端设备的标识的信息是无线接入网配置的，则所述指示信息表明所述寻呼是基于所述无线接入网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述无线接入网产生的寻呼。
实施例5、如实施例1所述的通信方法，所述指示信息中包括：源于核心网的被寻呼终端设备的标识的信息或无线接入网配置的被寻呼终端设备的标识的信息；当所述指示信息中包括源于核心网的被寻呼终端设备的标识的信息时，则所述指示信息表明所述寻呼是基于所述核心网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述核心网产生的寻呼；或者，当所述指示信息中包括无线接入网配置的被寻呼终端设备的标识的信息时，则所述指示信息表明所述寻呼是基于所述无线接入网产生的寻呼，并被用于使得所述分布式单元获知所述寻呼是基于所述无线接入网产生的寻呼。
实施例6、一种通信方法，包括：分布式单元接收来自于集中式单元的寻呼消息，所述寻呼消息中携带表明所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼的指示信息；所述分布式单元根据所述指示信息获知所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼。
实施例7、如实施例6所述的通信方法，包括：所述指示信息是源于核心网的被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是基于所述核心网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于所述核心网产生的寻呼；或者，所述指示信息是无线接入网配置的被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是基于所述无线接入网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于所述无线接入网产生的寻呼。
实施例8、如实施例6所述的通信方法，所述寻呼消息中还包括被寻呼终端设备的标识的信息；所述指示信息表明所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼，包括：所述指示信息表明所述寻呼是基于所述核心网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于所述核心网产生的寻呼；或者，所述指示信息表明所述寻呼是基于所述无线接入网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于所述无线接入网产生的寻呼。
实施例9、如实施例6所述的通信方法，所述寻呼消息中还包括被寻呼终端设备的标识的信息；所述指示信息表明所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于核心网产生的寻呼或所述寻呼是基于无线接入网产生的寻呼，包括：所述指示信息表明所述被寻呼终端设备的标识的信息来源于核心网，则所述指示信息表明所述寻呼是基于所述核心网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于所述核心网产生的寻呼；或者，所述指示信息表明所述被寻呼终端设备的标识的信息是无线接入网配置的，则所述指示信息表明所述寻呼是基于所述无线接入网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于所述无线接入网产生的寻呼。
实施例10、如实施例6所述的通信方法，所述指示信息中包括：源于核心网的被寻呼终端设备的标识的信息或无线接入网配置的被寻呼终端设备的标识的信息；当所述指示信息中包括源于核心网的被寻呼终端设备的标识的信息时，则所述指示信息表明所述寻呼是基于所述核心网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于所述核心网产生的寻呼；或者，当所述指示信息中包括无线接入网配置的被寻呼终端设备的标识的信息时，则所述指示信息表明所述寻呼是基于所述无线接入网产生的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是基于所述无线接入网产生的寻呼。
实施例11、一种通信方法，包括：集中式单元拒绝终端设备的接入请求；所述集中式单元向分布式单元发送指示信息；所述指示信息用于表明所述分布式单元需要删除所述终端设备的上下文信息。
实施例12、如实施例11所述的通信方法，包括：所述指示信息包含：拒绝所述终端设备接入的指示和/或拒绝所述终端设备接入的原因的信息。
实施例13、如实施例10或11所述的通信方法，包括：所述集中式单元接收来自于所述分布式单元发送的关于允许所述终端设备接入的通知消息。
实施例14、一种通信方法，包括：在终端设备的接入请求被集中式单元拒绝的情况下，
分布式单元接收来自于所述集中式单元发送的指示信息；所述指示信息用于表明所述分布式单元需要删除所述终端设备的上下文信息。
实施例15、如实施例14所述的通信方法，包括：所述指示信息包含：拒绝所述终端设 备接入的指示和/或拒绝所述终端设备接入的原因的信息。
实施例16、如实施例14或15所述的通信方法，包括：所述分布式单元向所述集中式单元发送关于允许所述终端设备接入的通知消息。
实施例17、如实施例1-16中任一所述的通信方法，所述分布式单元具有如下中至少一种：无线链路控制层，媒体接入控制层，以及物理层；所述集中式单元具有如下中至少一种：无线资源控制层，业务数据适配协议层，以及分组数据汇聚层协议层；所述分布式单元和所述集中式单元属于所述无线接入网或属于一个基站。
实施例18、一种通信设备，所述通信设备包括：至少一个处理器和通信接口，所述通信接口用于所述通信设备与其他通信设备进行信息交互，当程序指令在所述至少一个处理器中执行时，使得所述通信设备实现如实施例1-17中任一所述的方法中在如下任一设备上的功能：所述分布式单元和所述集中式单元。
实施例19、一种计算机程序存储介质，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得如实施例1-17中任一所述的方法中在如下任一设备上的功能得以实现：所述分布式单元和所述集中式单元。
实施例20、一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得如实施例1-17中任一所述的方法中在如下任一设备上的功能得以实现：所述分布式单元和所述集中式单元。
实施例21、一种通信系统，所述通信系统包括：如实施例18所述的通信设备。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (33)

  1. 一种通信方法，其特征在于，包括：
    分布式单元接收集中式单元发送的寻呼消息，所述寻呼消息中携带指示信息，所述指示信息用于表明所述寻呼是源于核心网的寻呼或所述寻呼是源于无线接入网的寻呼；
    所述分布式单元根据所述指示信息获知所述寻呼是源于所述核心网的寻呼或所述寻呼是源于所述无线接入网的寻呼。
  2. 如权利要求1所述的通信方法，其特征在于，所述方法还包括：
    所述分布式单元将所述指示信息发向被寻呼终端设备。
  3. 如权利要求1或2所述的通信方法，其特征在于，所述指示信息包括：源于所述核心网的被寻呼终端设备的标识或所述无线接入网配置的被寻呼终端设备的标识。
  4. 如权利要求1或2所述的通信方法，其特征在于：
    所述指示信息是源于所述核心网的所述被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是源于所述核心网的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是源于所述核心网的寻呼；或者，
    所述指示信息是所述无线接入网配置的所述被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是源于所述无线接入网的寻呼，所述分布式单元根据所述指示信息获知所述寻呼是源于所述无线接入网的寻呼。
  5. 如权利要求1-4中任一所述的通信方法，其特征在于，
    所述源于核心网的被寻呼终端设备的标识为所述被寻呼终端设备的临时移动用户标识TMSI或者国际移动用户识别码IMSI。
  6. 一种通信方法，其特征在于，包括：
    集中式单元向分布式单元发送寻呼消息，所述寻呼消息中携带指示信息，所述指示信息用于表明所述寻呼是源于核心网的寻呼或所述寻呼是源于无线接入网的寻呼；
    所述指示信息被用于使得所述分布式单元获知所述寻呼是源于所述核心网的寻呼或所述寻呼是源于所述无线接入网的寻呼。
  7. 如权利要求6所述的通信方法，其特征在于，所述指示信息被所述分布式单元发向所述被寻呼终端设备。
  8. 如权利要求6或7所述的通信方法，其特征在于，所述指示信息包括：源于核心网的被寻呼终端设备的标识或所述无线接入网配置的被寻呼终端设备的标识。
  9. 如权利要求6或7所述的通信方法，其特征在于：
    所述指示信息是源于所述核心网的被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是源于所述核心网的寻呼，并被用于使得所述分布式单元获知所述寻呼是源于所述核心网的寻呼；或者，
    所述指示信息是所述无线接入网配置的被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是源于所述无线接入网的寻呼，并被用于使得所述分布式单元获知所述寻呼是源于所述无线接入网的寻呼。
  10. 如权利要求6-9中任一所述的通信方法，其特征在于，所述源于核心网的被寻呼终端设备的标识为所述被寻呼终端设备的临时移动用户标识TMSI或者国际移动用户识别码IMSI。
  11. 一种通信方法，其特征在于，包括：
    集中式单元拒绝终端设备的接入请求；
    所述集中式单元向分布式单元发送指示信息；
    所述指示信息用于表明所述分布式单元需要删除所述终端设备的上下文信息。
  12. 如权利要求11所述的通信方法，其特征在于，包括：
    所述指示信息包含：拒绝所述终端设备接入的指示和/或拒绝所述终端设备接入的原因的信息。
  13. 如权利要求10或11所述的通信方法，其特征在于，包括：
    所述集中式单元接收来自于所述分布式单元发送的关于允许所述终端设备接入的通知消息。
  14. 一种通信方法，其特征在于，包括：
    在终端设备的接入请求被集中式单元拒绝的情况下，
    分布式单元接收来自于所述集中式单元发送的指示信息；
    所述指示信息用于表明所述分布式单元需要删除所述终端设备的上下文信息。
  15. 如权利要求14所述的通信方法，其特征在于，包括：
    所述指示信息包含：拒绝所述终端设备接入的指示和/或拒绝所述终端设备接入的原因的信息。
  16. 如权利要求14或15所述的通信方法，其特征在于，包括：
    所述分布式单元向所述集中式单元发送关于允许所述终端设备接入的通知消息。
  17. 如权利要求1-16中任一所述的通信方法，其特征在于，
    所述分布式单元具有如下中一个或多个：无线链路控制层功能，媒体接入控制层功能，以及物理层功能；
    所述集中式单元具有如下中一个或多个：无线资源控制层功能，业务数据适配协议层功能，以及分组数据汇聚层协议层功能；
    所述分布式单元和所述集中式单元属于所述无线接入网或属于同一个基站。
  18. 一种通信设备，其特征在于，所述通信设备包括：至少一个处理器和通信接口，所述通信接口用于所述通信设备与其他通信设备进行信息交互，当程序指令在所述至少一个处理器中执行时，使得所述通信设备实现如权利要求1-17中任一所述的方法中在如下任一设备上的功能：所述分布式单元和所述集中式单元。
  19. 一种计算机程序存储介质，其特征在于，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得如权利要求1-17中任一所述的方法中在如下任一设备上的功能得以实现：所述分布式单元和所述集中式单元。
  20. 一种芯片系统，其特征在于，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得如权利要求1-17中任一所述的方法中在如下任一设备上的功能得以实现：所述分布式单元和所述集中式单元。
  21. 一种通信装置，其特征在于，包括：
    一个模块，用于接收集中式单元发送的寻呼消息，所述寻呼消息中携带指示信息，所述指示信息用于表明所述寻呼是源于核心网的寻呼或所述寻呼是源于无线接入网的寻呼；
    一个模块，用于根据所述指示信息获知所述寻呼是源于所述核心网的寻呼或所述寻呼 是源于所述无线接入网的寻呼。
  22. 如权利要求21所述的通信装置，其特征在于，所述通信装置还包括：
    一个模块，用于将所述指示信息发向被寻呼终端设备。
  23. 如权利要求21或22所述的通信装置，其特征在于，所述指示信息包括：源于所述核心网的被寻呼终端设备的标识或所述无线接入网配置的被寻呼终端设备的标识。
  24. 如权利要求21或22所述的通信装置，其特征在于：
    所述指示信息是源于所述核心网的所述被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是源于所述核心网的寻呼，所述通信装置根据所述指示信息获知所述寻呼是源于所述核心网的寻呼；或者，
    所述指示信息是所述无线接入网配置的所述被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是源于所述无线接入网的寻呼，所述通信装置根据所述指示信息获知所述寻呼是源于所述无线接入网的寻呼。
  25. 如权利要求21-24中任一所述的通信装置，其特征在于，所述源于核心网的被寻呼终端设备的标识为所述被寻呼终端设备的临时移动用户标识TMSI或者国际移动用户识别码IMSI。
  26. 一种通信装置，其特征在于，包括：
    一个模块，用于向分布式单元发送寻呼消息，所述寻呼消息中携带指示信息，所述指示信息用于表明所述寻呼是源于核心网的寻呼或所述寻呼是源于无线接入网的寻呼；
    所述指示信息被用于使得所述分布式单元获知所述寻呼是源于所述核心网的寻呼或所述寻呼是源于所述无线接入网的寻呼。
  27. 如权利要求26所述的通信装置，其特征在于，所述指示信息被所述分布式单元发向所述被寻呼终端设备。
  28. 如权利要求26或27所述的通信装置，其特征在于，所述指示信息包括：源于核心网的被寻呼终端设备的标识或所述无线接入网配置的被寻呼终端设备的标识。
  29. 如权利要求26或27所述的通信装置，其特征在于，包括：
    所述指示信息是源于所述核心网的被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是源于所述核心网的寻呼，并被用于使得所述分布式单元获知所述寻呼是源于所述核心网的寻呼；或者，
    所述指示信息是所述无线接入网配置的被寻呼终端设备的标识的信息，则所述指示信息被用于表明所述寻呼是源于所述无线接入网的寻呼，并被用于使得所述分布式单元获知所述寻呼是源于所述无线接入网的寻呼。
  30. 如权利要求26-29中任一所述的通信装置，其特征在于，所述源于核心网的被寻呼终端设备的标识为所述被寻呼终端设备的临时移动用户标识TMSI或者国际移动用户识别码IMSI。
  31. 一种通信装置，其特征在于，所述通信装置执行如权利要求1-17中任一所述的方法中在如下设备的操作：所述分布式单元或所述集中式单元。
  32. 一种通信系统，其特征在于，所述通信系统包括如下中任一种：如权利要求18所述的通信设备，如权利要求19所述的计算机程序存储介质，如权利要求20所述的芯片系统，或者，如权利要求21-31中任一所述的通信装置。
  33. 一种计算机程序产品，其特征在于，所述计算机程序产品具有程序指令，当所述 程序指令被直接或者间接执行时，使得如权利要求1-17中任一所述的方法中在如下任一设备上的功能得以实现：所述分布式单元和所述集中式单元。
PCT/CN2019/071162 2018-01-12 2019-01-10 一种通信方法，设备及其系统 WO2019137434A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
JP2020538569A JP7106653B2 (ja) 2018-01-12 2019-01-10 通信方法、通信デバイス、および通信システム
AU2019207029A AU2019207029B2 (en) 2018-01-12 2019-01-10 Communication method, communications device, and communications system
RU2020126718A RU2778144C2 (ru) 2018-01-12 2019-01-10 Способ связи, устройство связи и система связи
KR1020207022800A KR20200105512A (ko) 2018-01-12 2019-01-10 통신 방법 및 디바이스, 및 그 시스템
CA3088224A CA3088224A1 (en) 2018-01-12 2019-01-10 Communication method, communications device, and communications system
EP19739080.0A EP3737172B1 (en) 2018-01-12 2019-01-10 Communication method and device, and system thereof
BR112020014067-8A BR112020014067A2 (pt) 2018-01-12 2019-01-10 método de comunicação, dispositivo de comunicações, e sistema de comunicações
US16/925,817 US11722987B2 (en) 2018-01-12 2020-07-10 Communication method, communications device, and communications system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810030917.4A CN110035498B (zh) 2018-01-12 2018-01-12 一种通信方法，设备及其系统
CN201810030917.4 2018-01-12

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/925,817 Continuation US11722987B2 (en) 2018-01-12 2020-07-10 Communication method, communications device, and communications system

Publications (1)

Publication Number Publication Date
WO2019137434A1 true WO2019137434A1 (zh) 2019-07-18

Family

ID=67218868

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/071162 WO2019137434A1 (zh) 2018-01-12 2019-01-10 一种通信方法，设备及其系统

Country Status (9)

Country Link
US (1) US11722987B2 (zh)
EP (1) EP3737172B1 (zh)
JP (1) JP7106653B2 (zh)
KR (1) KR20200105512A (zh)
CN (1) CN110035498B (zh)
AU (1) AU2019207029B2 (zh)
BR (1) BR112020014067A2 (zh)
CA (1) CA3088224A1 (zh)
WO (1) WO2019137434A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200111793A (ko) * 2018-01-31 2020-09-29 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 페이징을 위한 방법, 단말 기기 및 네트워크 기기
WO2019193553A1 (en) * 2018-04-06 2019-10-10 Telefonaktiebolaget Lm Ericsson (Publ) Qos flow management over e1
EP3669609B1 (en) * 2018-10-04 2021-01-13 Google LLC Method for handling a radio resource control cell group configuration
US20220132600A1 (en) * 2019-02-12 2022-04-28 Lg Electronics Inc. Early data transmission in cu-du split
BR112022000849A2 (pt) * 2019-07-29 2022-03-08 Nec Corp Nó mestre, nó secundário e método para os mesmos
WO2021026706A1 (zh) * 2019-08-09 2021-02-18 华为技术有限公司 一种f1接口管理方法及装置
CN112399498B (zh) * 2019-08-15 2021-09-07 华为技术有限公司 用于小区测量的方法和装置
CN114503785A (zh) * 2019-09-30 2022-05-13 华为技术有限公司 用于寻呼的方法和装置
CN113141284B (zh) * 2020-01-17 2022-07-19 大唐移动通信设备有限公司 一种接入网设备及数据传输方法
CN113939044A (zh) * 2020-06-29 2022-01-14 华为技术有限公司 一种通信方法和装置
CN116171631B (zh) * 2020-08-03 2024-05-07 荣耀终端有限公司 用于上行链路资源配置的方法、装置和系统
EP4140210A4 (en) * 2020-08-07 2024-01-17 Zte Corp METHOD, DEVICE, AND SYSTEM FOR PAGING AND TRANSMISSION OF UE IDENTITIES IN WIRELESS NETWORKS
WO2022126391A1 (zh) * 2020-12-15 2022-06-23 北京小米移动软件有限公司 一种寻呼消息监听方法、寻呼消息监听装置及存储介质
CN113225696B (zh) 2021-06-02 2022-06-24 上海移远通信技术股份有限公司 寻呼处理方法、装置、设备及存储介质
KR102619369B1 (ko) * 2021-11-26 2023-12-29 주식회사 블랙핀 무선 이동 통신 시스템에서 단말이 페이징 메시지를 처리하는 방법 및 장치
KR102628661B1 (ko) * 2021-11-26 2024-01-24 주식회사 블랙핀 무선 이동 통신 시스템에서 기지국이 페이징 메시지를 처리하는 방법 및 장치
KR102628660B1 (ko) * 2021-11-26 2024-01-24 주식회사 블랙핀 무선 이동 통신 시스템에서 분산 유닛이 페이징 메시지를 처리하는 방법 및 장치
CN117693074A (zh) * 2022-09-02 2024-03-12 中兴通讯股份有限公司 通信方法、网元设备、介质及程序产品

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105144809A (zh) * 2013-03-07 2015-12-09 英特尔德国有限责任公司 用于在两个通信设备之间准备直接通信的装置和方法

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5473612A (en) * 1994-11-28 1995-12-05 Motorola, Inc. Method and apparatus for minimizing false detection of packet data in a communication receiver
US9198156B2 (en) * 2004-08-23 2015-11-24 Telefonaktiebolaget L M Ericsson (Publ) Paging mobile stations in a hybrid network
WO2010032477A1 (ja) * 2008-09-22 2010-03-25 パナソニック株式会社 無線通信基地局、無線通信装置、及び無線通信システム
EP2426960B1 (en) 2009-04-28 2014-02-19 Huawei Technologies Co., Ltd. A paging method, location update method and device
US9125122B2 (en) * 2012-06-09 2015-09-01 Apple Inc. Paging for circuit switched fallback (CSFB) in long term evolution (LTE) connected mode
US8682283B2 (en) * 2012-06-09 2014-03-25 Apple Inc. Adjusting connection states of a mobile wireless device
CN107295637B (zh) * 2016-03-31 2019-09-17 电信科学技术研究院 一种寻呼方法、设备及系统
CN107343299B (zh) * 2016-05-03 2021-01-05 株式会社Kt 用于改变ue的连接状态的方法和装置
CN106162730B (zh) * 2016-07-12 2019-11-15 上海华为技术有限公司 一种通信的方法、设备及系统
CN109391963B (zh) 2017-08-11 2022-03-11 华为技术有限公司 一种传输方法和网络设备

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105144809A (zh) * 2013-03-07 2015-12-09 英特尔德国有限责任公司 用于在两个通信设备之间准备直接通信的装置和方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Further considerations on RAN and CN paging in INACTIVE", 3GPP TSG-RAN WG2 #97 TDOC R2-1700893, 17 February 2017 (2017-02-17), XP051211672 *
HUAWEI: "F1 AP procedures for RRC Connection Setup", 3GPP TSG-RAN3 NR ADHOC R3-172176, 29 June 2017 (2017-06-29), XP051302122 *
HUAWEI: "Further discussions on Paging over F1", 3GPP TSG-RAN3 MEETING #98 R3-174480, 1 December 2017 (2017-12-01), pages 1 - 4, XP051373376 *
See also references of EP3737172A4

Also Published As

Publication number Publication date
BR112020014067A2 (pt) 2020-12-01
CN110035498A (zh) 2019-07-19
KR20200105512A (ko) 2020-09-07
JP7106653B2 (ja) 2022-07-26
US11722987B2 (en) 2023-08-08
RU2020126718A3 (zh) 2022-03-17
CA3088224A1 (en) 2019-07-18
EP3737172A4 (en) 2021-02-24
CN110035498B (zh) 2022-08-26
EP3737172A1 (en) 2020-11-11
AU2019207029B2 (en) 2022-03-31
AU2019207029A1 (en) 2020-07-30
EP3737172B1 (en) 2024-01-10
RU2020126718A (ru) 2022-02-14
JP2021510273A (ja) 2021-04-15
US20200344719A1 (en) 2020-10-29

Similar Documents

Publication Publication Date Title
WO2019137434A1 (zh) 一种通信方法，设备及其系统
JP7394940B2 (ja) 伝送方法およびネットワークデバイス
US11770873B2 (en) Method for keeping mobile initiated connection only mode user equipment in connected mode
EP3952449B1 (en) Method and apparatus for moving between communications systems
CN107645779B (zh) 一种数据发送、传输方法及装置
CN109892003B (zh) 经由具有中继能力的用户装备ue在远程ue和电信网络之间建立连接的方法和系统
WO2019096281A1 (zh) 一种通信方法，通信设备及其通信系统
US20200383035A1 (en) Communications method and apparatus
WO2021088660A1 (zh) 通信方法、装置及设备
WO2018019001A1 (zh) 一种终端状态转换方法及装置
WO2019129197A1 (zh) 一种通信方法，设备及其系统
CN110519807B (zh) 一种通信方法及装置
WO2022205381A1 (zh) 广播多播业务传输方法、装置及存储介质
CN107231623A (zh) 一种数据调度方法、基站及系统
US20230070712A1 (en) Communication method, apparatus, and system
CN109429366B (zh) 一种pdu会话处理方法及设备
KR20160060091A (ko) 페이징 방법, 네트워크 디바이스 및 통신 시스템
CN110636572A (zh) 通信方法及装置
EP4187941A1 (en) Data transmission method, apparatus and system
US11979247B2 (en) Message forwarding method and apparatus
WO2021189235A1 (zh) 一种数据传输方法及装置、通信设备
US20200008268A1 (en) Enhanced Procedure Transaction ID Handling
CN112789892B (zh) 无线通信方法、装置及系统
US20230156436A1 (en) Data Transmission Method, Apparatus, and System
RU2778144C2 (ru) Способ связи, устройство связи и система связи

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3088224

Country of ref document: CA

Ref document number: 2020538569

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019207029

Country of ref document: AU

Date of ref document: 20190110

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20207022800

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019739080

Country of ref document: EP

Effective date: 20200807

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020014067

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020014067

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200709