WO2015096673A1 - 集群业务属性上报和接收的方法、装置和系统 - Google Patents

集群业务属性上报和接收的方法、装置和系统 Download PDF

Info

Publication number
WO2015096673A1
WO2015096673A1 PCT/CN2014/094477 CN2014094477W WO2015096673A1 WO 2015096673 A1 WO2015096673 A1 WO 2015096673A1 CN 2014094477 W CN2014094477 W CN 2014094477W WO 2015096673 A1 WO2015096673 A1 WO 2015096673A1
Authority
WO
WIPO (PCT)
Prior art keywords
cluster
terminal
base station
service attribute
random access
Prior art date
Application number
PCT/CN2014/094477
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 US15/309,484 priority Critical patent/US20170150529A1/en
Publication of WO2015096673A1 publication Critical patent/WO2015096673A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0838—Random access procedures, e.g. with 4-step access using contention-free random access [CFRA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/08—Trunked mobile radio systems
    • 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

Definitions

  • the present invention relates to the field of trunking communication technologies, and in particular, to a method, apparatus, and system for reporting and receiving cluster service attributes.
  • the base station does not know which terminals in the cell are receiving the group call, that is, whether the terminal receives the group call, which is unknown to the base station.
  • the current solution is to let the base station know the relevant situation from the network side. For example, the base station directly learns from the network side whether the UE with the individual service to be scheduled belongs to the group call, or the base station knows all the UEs of the group call from the network side. Then, the UE in the cell with individual service to be scheduled is monitored and judged whether it belongs to the group call.
  • a cluster service attribute reporting method includes: when a cluster terminal has a cluster service attribute to be reported, the cluster terminal reports the third message MSG3 through random access.
  • the cluster service attributes are described to the base station.
  • a cluster service attribute receiving method is further provided, that is, the base station receives the cluster service attribute reported by the cluster terminal by using the third message MSG3 that the cluster terminal contends for random access.
  • a cluster terminal is provided to implement the foregoing method, and the terminal includes a reporting module, configured to compete for a random access third message MSG3 when the cluster terminal has a cluster service attribute to be reported.
  • the cluster service attribute is reported to the base station.
  • the base station includes a receiving module, configured to receive the cluster service attribute reported by the cluster terminal by the MSG3 that the cluster terminal contends for random access.
  • the present invention also proposes a system for cluster service attribute processing, including cluster terminals and base stations as described above.
  • FIG. 1 is a block diagram showing a basic processing flow of reporting and receiving a cluster service attribute according to the present invention
  • FIG. 3 is a flowchart of a non-contention random access procedure in an LTE system
  • Figure 5 is a list of LCIDs including a custom G-RNTI
  • FIG. 6 is a structural diagram of a G-RNTI MAC CE
  • FIG. 10 is a structural block diagram of a device of a cluster terminal according to an embodiment of the present invention.
  • FIG. 11 is a structural block diagram of a device of a base station according to another embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a system according to still another embodiment of the present invention.
  • FIG. 13 is a block diagram showing the hardware structure of a cluster terminal in an embodiment of the present invention.
  • FIG. 14 is a block diagram showing the hardware structure of a base station according to another embodiment of the present invention.
  • the present invention proposes a technical solution for cluster attribute processing, which interprets the above problem from another angle, and does not increase network side complexity.
  • FIG. 1 The basic processing flow diagram of the cluster service attribute reporting and receiving proposed by the present invention is shown in FIG. 1 , and the method includes two parts: a terminal side and a base station side.
  • Step 101 The cluster terminal determines that the cluster service attribute needs to be reported
  • Step 102 When the cluster terminal has a cluster service attribute to be reported, the cluster terminal reports the cluster service attribute to the base station by using the third message MSG3 that contends for random access, as shown in the solid line part of FIG.
  • the case where the cluster terminal has a cluster service attribute to be reported includes: when the cluster terminal has a cluster group call called service or when the cluster group call called service changes.
  • the cluster terminal reports the cluster service attribute to the base station when the cluster terminal is in the radio resource control idle RRC_Idle state and the cluster group calls the called service.
  • the contention random access may be a re-established random access; the re-established random access
  • the trigger conditions for incoming include: radio link failure, handover failure, integrity protection failure, or RRC connection reconfiguration failure.
  • the contention random access may also be a random access that arrives at the uplink data; the trigger condition of the random access that the uplink data arrives includes: uplink out-of-synchronization or no scheduling request resource.
  • Step 103 The cluster terminal may also report the cluster service attribute to the base station by using the first uplink data/letter packet after obtaining the cluster service attribute, as shown by the dotted line in FIG.
  • the cluster terminal When the cluster terminal is handed over to the target cell, the cluster terminal reports the cluster service attribute to the base station after receiving the cluster service attribute of the cluster group call service in the target cell. In this case, it can be reported by the MSG3 that contends for random access, or can be reported by the first uplink data/letter packet after obtaining the cluster service attribute.
  • the cluster terminal reports the cluster service attribute to the base station by using the media access control channel resource MAC CE of the MSG3 or the MAC CE of the first uplink data/report packet.
  • the cluster service attribute includes but is not limited to a group radio network temporary identifier G-RNTI.
  • the MAC CE may be a G-RNTI MAC CE.
  • Step 104 The base station may receive the cluster service attribute reported by the cluster terminal by using the cluster terminal to contend for the randomly accessed MSG3, as shown in the solid line part of FIG. or,
  • Step 105 The base station may further receive the cluster service attribute reported by the cluster terminal by using the cluster terminal uplink data/letter packet, as shown in the dotted line of FIG.
  • the base station receives the MAC CE of the MSG3 or the uplink data/letter packet MAC CE, and solves the cluster service attribute reported by the cluster terminal.
  • the cluster service attributes include but are not limited to G-RNTI.
  • the MAC CE is a G-RNTI MAC CE.
  • the logical channel identifier LCID of the existing LTE uplink shared channel UL-SCH channel is as shown in FIG. 4 .
  • 5 is a list of LCIDs including a custom G-RNTI, where the index corresponding to the LCID defining the G-RNTI is 11000, and is of course not limited thereto.
  • the G-RNTI MAC CE has a fixed length of 16 bits, and stores the G-RNTI of the called group service of the terminal group.
  • the structure of the G-RNTI MAC CE is as shown in FIG. 6.
  • the terminal reports the cluster service attribute by using the G-RNTI MAC CE as shown in FIG. 6.
  • Embodiment 1 Initial competition random access reporting
  • the initial random access procedure is as follows:
  • Step 701 The UE initiates the first message MSG1, and uses RA-RNTI scrambling, and the RRC state is RRC_Idle;
  • Step 702 The base station receives the MSG1, and sends a second message MSG2, where the temporary cell radio network temporary identifier Temp C-RNTI is carried, and the MSG2 uses the random access cell radio network temporary identifier RA-RNTI to scramble;
  • Step 703 The UE receives the MSG2, acquires the Temp C-RNTI, and sends the MSG3, which is scrambled by the Temp C-RNTI, and the RRC state is RRC_Idle;
  • Step 704 The base station receives the MSG3, and uses the C-RNTI to establish the UE entity C-RNTI value as the Temp C-RNTI, and sends the MSG4 to use the Temp C-RNTI scrambling.
  • the base station can use the UE entity to communicate with the corresponding UE.
  • the terminal receives the fourth message MSG4, and sets a C-RNTI, which is a value of Temp C-RNTI, and switches the RRC state from RRC_Idle to the radio resource control connection RRC_Connected.
  • the base station side cell is Cell0
  • the cell0 has a cluster group call service
  • the G-RNTI is 10
  • the cluster terminal UE0 exists in the cell, and is in the RRC_Idle state and receives the cluster group call service.
  • Terminal side UE0
  • the UE0 in the MSG3 carries the G-RNTI to the base station side cell through the G-RNTI MAC CE; the terminal scrambles the MSG3 through the Temp C-RNTI allocated by the base station side.
  • the base station side cell Cell0 receives the G-RNTI MAC CE in the MSG3 through the Temp C-RNTI (now 12), and resolves the G-RNTI to 10, and considers that the terminal corresponding to the Temp C-RNTI has a G-RNTI of 10
  • the cluster group calls the called service.
  • the base station side uses the C-RNTI to establish an instance corresponding to the UE0, and the value of the C-RNTI is Temp C-RNTI, which is 12. Then, the base station side considers that the UE0 with the C-RNTI of 12 has a cluster group called called service with a G-RNTI of 10.
  • Embodiment 2 reporting that the cluster terminal switches to the target base station
  • Step 801 The source cell sends a handover command (HO (Handover) Command) to the terminal, where the information includes a dedicated preamble and C-RNTI corresponding to the terminal in the target cell.
  • HO Handover
  • Step 802 After receiving the handover command sent by the source cell, the terminal solves the information such as the dedicated preamble and the C-RNTI in the handover command, and initiates the dedicated pre-targeted cell. MSG1;
  • Step 803 The target cell receives the MSG1; and sends the MSG2, where the Temp C-RNTI is carried in the value (the value may be the C-RNTI value in the handover command), and the MSG2 uses the RA-RNTI to scramble;
  • Step 804 The UE receives the MSG2; sends a handover confirmation command (HO Confirm) through the uplink grant in the MSG2, and performs scrambling using the C-RNTI.
  • HO Confirm handover confirmation command
  • the base station side there are cells Cell0 and Cell1 on the base station side, and a cluster group call service exists in both Cell0 and Cell1.
  • the G-RNTI of the cluster group call service in Cell0 is 100, and G- in Cell1.
  • the RNTI is 150, and the cluster terminal UE0 exists in the cell, and is in the RRC_Idle state and receives the cluster group call service.
  • Terminal side UE0
  • the terminal UE0 After receiving the attribute G-RNTI of the cluster group call of the target cell Cell1, the terminal UE0 transmits the G-RNTI to the base station side cell through the G-RNTI MAC CE in the first uplink data packet.
  • UE0 sends a G-RNTI to the base station side cell through the G-RNTI MAC CE when transmitting the handover confirmation command in step 804, and passes the C-RNTI (now 12). ) Scrambling.
  • Base station side cell Cell1
  • the base station side cell Cell1 receives the G-RNTI MAC CE in the first uplink data packet of the terminal UE0 through the C-RNTI (now 12), and resolves the G-RNTI to 150, and considers that the G-RNTI exists in the terminal.
  • the cluster group of 150 calls the called service.
  • the terminal may perform attribute reporting by the MSG3 that contends for random access, and the base station side performs corresponding reception.
  • Embodiment 3 Random access reporting of uplink data arrival
  • Step 901 The UE initiates MSG1 and performs RA-RNTI scrambling.
  • Step 902 The base station receives the MSG1, and sends the MSG2, where the Temp C-RNTI is carried, and the MSG2 uses the RA-RNTI to scramble.
  • Step 903 The UE receives the MSG2, acquires the Temp C-RNTI, and sends the MSG3, and uses the Temp C-RNTI to scramble.
  • Step 904 The base station receives the MSG3, and resolves the C-RNTI in the C-RNTI MAC CE in the MSG3, which is C, and finds the UE entity whose C-RNTI is C from the UE entity of the base station side cell; and sends the MSG4, Scrambling with C-RNTI;
  • the terminal receives the MSG4.
  • the base station side cell is Cell0
  • the cell0 has a cluster group call service
  • the G-RNTI is 22
  • the cluster terminal UE0 exists in the cell
  • the UE0 is in the RRC_Connected state and receives the cluster group call service, and its C -RNTI is 33.
  • Terminal side UE0
  • the UE0 informs the base station side cell that the G-RNTI MAC CE carries the G-RNTI (for 22) in the MSG3, and the C-RNTI MAC CE carries the C-RNTI of the UE0 (33) in the MSG3;
  • the Temp C-RNTI (now 35) scrambles MSG3.
  • the base station side cell Cell0 receives the MSG3 through the Temp C-RNTI (now 35),
  • the C-RNTI is obtained from the C-RNTI MAC CE of the MSG3, and is 33; the G-RNTI is obtained from the G-RNTI MAC CE of the MSG3, and is 22; the base station side cell considers that the C-RNTI is 33 corresponding to the UE entity.
  • Embodiment 4 Reporting of cluster business changes
  • the base station side cell is Cell0, and the cell0 has a cluster group call service.
  • the G-RNTI is 22, and the cluster terminal UE0 exists in the cell.
  • the UE0 is in the RRC_Connected state and receives the cluster group call service, and its C-RNTI is 33.
  • Cell0 newly establishes a cluster group call service with a G-RNTI of 56, and UE0 also belongs to the cluster group call.
  • the group call service with a G-RNTI of 56 has a higher priority than the group call service with a G-RNTI of 22.
  • the UE0 receives the paging of the trunking group call service with the G-RNTI of 56, and determines that the priority of the group call service with the G-RNTI of 56 is higher than the priority of the group call service with the G-RNTI of 22, and the terminal enters G. After the RNTI is 56, the G-RNTI is 56, and the G-RNTI is reported to the base station side Cell0 by the G-RNTI MAC CE.
  • the present invention also provides a cluster terminal that implements the foregoing method.
  • the terminal includes a reporting module 1010, which is used to report the random access of the MSG3 through the random access when the cluster service attribute needs to be reported.
  • the cluster service attributes are described to the base station.
  • the reporting module reports the cluster service attribute to the base station.
  • the contention random access is a re-established random access.
  • the trigger conditions of the re-established random access include: radio link failure, handover failure, integrity protection failure, or RRC connection reconfiguration failure.
  • the contention random access is a random access where uplink data arrives.
  • the trigger condition of the random access that the uplink data arrives includes: uplink out-of-synchronization or no scheduling request resource.
  • the reporting module reports the cluster service attribute to the base station by using the first uplink data/letter packet after obtaining the cluster service attribute.
  • the cluster terminal further includes a receiving module 1020, configured to receive, when the cluster terminal switches to the target cell, a cluster service attribute of the cluster group call service in the target cell.
  • the reporting module reports the cluster service attribute received by the receiving module to the base station.
  • the cluster terminal reports the cluster service attribute to the base station by using the MAC CE of the MSG3 or the MAC CE of the first uplink data/signal packet.
  • the cluster service attribute includes but is not limited to a G-RNTI.
  • the MAC CE is a G-RNTI MAC CE.
  • the cluster terminal When the cluster terminal has the cluster service attribute to be reported, the cluster terminal has a cluster group call called service or when the cluster group call called service changes.
  • the present invention also provides a base station that implements the foregoing method, and includes a receiving module 1110, configured to receive, by the cluster terminal, a random access MSG3, the cluster service attribute reported by the cluster terminal.
  • the receiving module is further configured to receive the cluster service attribute reported by the cluster terminal by using the cluster terminal uplink data/the packet.
  • the base station further includes a processing module 1120, configured to solve the cluster service attribute reported by the cluster terminal after receiving the MAC CE of the MSG3 or the uplink data/the packet MAC CE.
  • the cluster service attribute includes but is not limited to a G-RNTI.
  • the MAC CE is a G-RNTI MAC CE.
  • the present invention finally proposes a system for cluster service attribute processing.
  • the system includes the terminal 1210 and the base station 1220 as described above.
  • FIG. 13 is a schematic diagram showing the hardware structure of a terminal reported by a cluster service attribute according to an embodiment of the present invention.
  • the hardware includes one or more processors 1310, memory 1320, and one or more program instructions stored on memory 1320 for execution by one or more processors 1310, including, for example, performing the foregoing.
  • the instructions of each step in the method embodiment that is, the reporting instruction 1321 and the receiving instruction 1322, the detailed procedure of which is described in the method embodiment regarding the terminal side method or the description of the terminal side device.
  • FIG. 14 is a schematic diagram showing the hardware of a base station for receiving cluster service attributes according to another embodiment of the present invention.
  • the hardware includes one or more processors 1410, memory 1420, and one or more program instructions stored on memory 1420 for execution by one or more processors 1410, including, for example, performing the foregoing.
  • the instructions of the steps in the method embodiment that is, the receiving instruction 1421 and the processing instruction 1422, the detailed procedure of which is described in the method embodiment regarding the base station side method or the description of the base station side device.
  • the present invention can know whether the terminal under the cell is in a certain cluster group call and called service on the premise that the base station side does not increase the air interface information, and the base station is well solved. It is not known which terminals in the cell are receiving the limitation of the group call.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

　本发明提出一种集群业务属性上报的方法，包括：集群终端有集群业务属性需上报时，所述集群终端通过竞争随机接入的第三消息MSG3上报所述集群业务属性给基站，或者所述集群终端通过获得所述集群业务属性后的第一个上行数据/信令包上报所述集群业务属性给基站。基于同样的构思，本发明还提出一种集群业务属性接收的方法，以及相应的集群终端、基站和系统。

Description

集群业务属性上报和接收的方法、装置和系统 技术领域
本发明涉及集群通信技术领域，尤其涉及集群业务属性上报和接收的方法、装置和系统。
发明背景
在无线集群通信系统中，对于一个具体的组呼而言，基站并不知道本小区内哪些终端在接收该组呼，即，终端是不是接收这个组呼，对基站而言是不可知的。目前的一种解决办法是让基站从网络侧获知相关情况，比如基站直接从网络侧获知有个体业务待调度的UE是否属于所述组呼；或者基站从网络侧获知组呼的全部UE组成，然后监控本小区中有个体业务待调度的UE并判断其是否属于组呼。
发明内容
针对上述问题，根据本发明的一个方面，提出一种集群业务属性上报方法，该方法包括：集群终端有集群业务属性需上报时，所述集群终端通过竞争随机接入的第三消息MSG3上报所述集群业务属性给基站。
根据本发明的另一方面，还提出一种集群业务属性接收方法，包括：基站通过集群终端竞争随机接入的第三消息MSG3接收所述集群终端上报的集群业务属性。
根据本发明的又一方面，提出了一种实现上述方法的集群终端，该终端包括上报模块，用于当所述集群终端有集群业务属性需上报时，通过竞争随机接入的第三消息MSG3上报所述集群业务属性给基站。
根据本发明的又一方面，还提出一种实现上述方法的基站，所述基 站包括接收模块，用于通过集群终端竞争随机接入的MSG3接收所述集群终端上报的集群业务属性。
最后，本发明还提出一种集群业务属性处理的系统，包括如上所述的集群终端和基站。
附图简要说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明提出的集群业务属性上报和接收的基本处理流程框图；
图2为LTE系统中竞争随机接入过程的流程图；
图3为LTE系统中非竞争随机接入过程的流程图；
图4为现有LTE的UL-SCH信道的LCID列表；
图5为包含自定义G-RNTI的LCID列表；
图6为G-RNTI MAC CE结构图；
图7为初始随机接入过程的流程图；
图8为切换下的非竞争随机接入流程图；
图9为上行数据到达的竞争随机接入流程图；
图10为本发明一个实施例中集群终端的装置结构框图；
图11为本发明另一实施例中基站的装置结构框图；
图12为本发明又一实施例中系统的结构框图；
图13本发明一个实施例中集群终端的硬件结构框图；
图14为本发明另一实施例中基站的硬件结构框图。
实施本发明的方式
发明人在发明过程中发现，现有方法能够实现让基站获知组呼业务属性的目的，但是该方法的实现会增加网络侧处理的复杂程度和维护难度。因此，本发明提出一种集群属性处理的技术方案，从另一个角度解读上述问题，并且不增加网络侧复杂度。
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明提出的集群业务属性上报和接收的基本处理流程框图如图1所示，方法包括终端侧和基站侧两部分。
终端侧：
步骤101，集群终端确定有集群业务属性需上报；
步骤102，集群终端有集群业务属性需上报时，所述集群终端通过竞争随机接入的第三消息MSG3上报所述集群业务属性给基站，如图1实线部分。其中，所述集群终端有集群业务属性需上报的情况包括：集群终端有集群组呼被叫业务时或所述集群组呼被叫业务发生变更时。
其中，当所述集群终端处于无线资源控制空闲RRC_Idle状态且有集群组呼被叫业务时，所述集群终端上报所述集群业务属性给基站。
所述竞争随机接入可以是重建立的随机接入；所述重建立的随机接 入的触发条件包括：无线链路失败、切换失败、完整性保护失败或RRC连接重配失败。
竞争随机接入还可以是上行数据到达的随机接入；所述上行数据到达的随机接入的触发条件包括：上行失步或没有调度请求资源。
步骤103，所述集群终端还可以通过获得所述集群业务属性后的第一个上行数据/信今包上报所述集群业务属性给基站，如图1的虚线部分。
当所述集群终端切换到目标小区时，所述集群终端在收到所述集群组呼被叫业务在所述目标小区的集群业务属性后上报所述集群业务属性给基站。此时，可以通过竞争随机接入的MSG3上报，也可以通过获得所述集群业务属性后的第一个上行数据/信今包上报。
具体的，所述集群终端通过所述MSG3的媒质接入控制信道资源MAC CE或所述第一个上行数据/信今包的MAC CE将集群业务属性上报给基站。
上述方法中，所述集群业务属性包括但不限于群组无线网络临时标识G-RNTI。此时，所述MAC CE可以是G-RNTI MAC CE。
基站侧：
步骤104，基站可以通过集群终端竞争随机接入的MSG3接收所述集群终端上报的集群业务属性，如图1实线部分所示。或者，
步骤105，基站还可以通过集群终端上行数据/信今包接收所述集群终端上报的集群业务属性，如图1虚线部分所示。
具体的，所述基站接收所述MSG3的MAC CE或所述上行数据/信今包MAC CE，解出所述集群终端上报的集群业务属性。其中，集群业务属性包括但不限于G-RNTI。此时，所述MAC CE是G-RNTI MAC CE。
下面以LTE系统为例，对本发明的具体实现进行详细说明。
根据《3GPP TS 36.300V11.7.0》文档规定，终端的随机接入有两种方式：竞争随机接入(如图2所示)和非竞争随机接入(如图3所示)。有6种事件触发随机接入，分别为：初始随机接入、RRC连接重建立过程、切换、RRC连接态下的下行数据到达、RRC连接态下的上行数据到达和RRC连接态下的位置定位。其中，前面5个事件支持竞争随机接入，RRC连接态下的下行数据到达、切换和RRC连接态下的位置定位支持非竞争随机接入。
基于《3GPP TS 36.321V11.3.0》文档，现有LTE的上行共享信道UL-SCH信道的逻辑信道标识LCID如图4所示。图5为包含自定义G-RNTI的LCID列表，其中，定义G-RNTI的LCID对应的索引为11000，当然也不限于此。G-RNTI MAC CE的长度固定，为16个比特，里面存放终端的集群组呼被叫业务的G-RNTI，其G-RNTI MAC CE的结构如图6所示。
以下的各实施例中，假设终端采用如图6所示的G-RNTI MAC CE上报集群业务属性。
实施例一：初始竞争随机接入上报
首先介绍LTE中的初始随机接入过程，如图7所示。
初始随机接入流程如下：
步骤701：UE发起第一消息MSG1，采用RA-RNTI加扰，RRC状态为RRC_Idle；
步骤702：基站接收MSG1；并下发第二消息MSG2，其中携带临时小区无线网络临时标识Temp C-RNTI，MSG2采用随机接入小区无线网络临时标识RA-RNTI加扰；
步骤703：UE接收MSG2，获取Temp C-RNTI；并发送MSG3，采用Temp C-RNTI加扰，RRC状态为RRC_Idle；
步骤704：基站接收MSG3，对该终端采用C-RNTI建立UE实体C-RNTI的值为Temp C-RNTI；发送MSG4，采用Temp C-RNTI加扰；
该基站可以采用该UE实体与相应的UE进行通信。
终端接收第四消息MSG4，并设置C-RNTI，其取值为Temp C-RNTI，把RRC状态由RRC_Idle切换到无线资源控制连接RRC_Connected。
本实施例中：今基站侧小区为Cell0，Cell0存在集群组呼业务，其G-RNTI为10，小区中存在集群终端UE0，处于RRC_Idle状态并在接收该集群组呼业务。当基站侧小区Cell0和该终端UE0发生初始随机接入过程时，
终端侧UE0：
UE0在MSG3中通过G-RNTI MAC CE携带G-RNTI告知基站侧小区；该终端通过基站侧分配的Temp C-RNTI对MSG3加扰。
基站侧Cell0：
基站侧小区Cell0在通过Temp C-RNTI(今为12)接收到MSG3中的G-RNTI MAC CE，解出G-RNTI，为10，则认为Temp C-RNTI对应的终端存在G-RNTI为10的集群组呼被叫业务。
具体的，基站侧在接收MSG3后会对该终端采用C-RNTI建立UE0对应的实例，C-RNTI的值为Temp C-RNTI，即为12。则基站侧认为C-RNTI为12的UE0存在G-RNTI为10的集群组呼被叫业务。
实施例二：集群终端切换到目标基站的上报
首先介绍切换下的非竞争随机接入流程，如图8所示。
步骤801：源小区向终端发送切换命令(HO(Handover)Command)，里面包含专用前导和该终端在目标小区对应的C-RNTI等信息；
步骤802：终端接收到源小区发送的切换命令后，解出切换命令里的专用前导和C-RNTI等信息；并采用该专用前导向目标小区发起 MSG1；
步骤803：目标小区接收到MSG1；并下发MSG2，其中携带Temp C-RNTI(取值可以为切换命令中的C-RNTI值)，MSG2采用RA-RNTI加扰；
步骤804：UE接收MSG2；通过MSG2中的上行授权，发送切换确认命令(HO Confirm)，采用C-RNTI加扰。
本实施例中：今基站侧存在小区Cell0和Cell1，一个集群组呼业务在Cell0和Cell1均存在，今该集群组呼业务在Cell0中的G-RNTI为100，在Cell1中的G-RNTI为150，小区中存在集群终端UE0，处于RRC_Idle状态并在接收该集群组呼业务。当基站侧小区Cell0和Cell1和该终端UE0发生切换下的非竞争随机接入过程时，
终端侧UE0：
终端UE0收到目标侧小区Cell1的集群组呼的属性G-RNTI后，在第一个上行数据包中通过G-RNTI MAC CE携带G-RNTI告知基站侧小区。
具体的，基于如图8所示的非竞争随机接入流程，UE0在步骤804中发送切换确认命令时通过G-RNTI MAC CE携带G-RNTI告知基站侧小区，通过C-RNTI(今为12)加扰。
基站侧小区Cell1：
基站侧小区Cell1在通过C-RNTI(今为12)接收到终端UE0的第一上行数据包中的G-RNTI MAC CE，解出G-RNTI，为150，则认为该终端存在G-RNTI为150的集群组呼被叫业务。
当然，本实施例中，终端也可以通过竞争随机接入的MSG3进行属性上报，基站侧进行相应的接收。
实施例三：上行数据到达的随机接入上报
首先介绍上行数据到达的竞争随机接入流程。
步骤901：UE发起MSG1，采用RA-RNTI加扰；
步骤902：基站接收MSG1；并下发MSG2，其中携带Temp C-RNTI，MSG2采用RA-RNTI加扰；
步骤903：UE接收MSG2，获取Temp C-RNTI；并发送MSG3，采用Temp C-RNTI加扰；
步骤904：基站接收MSG3，解出MSG3中的C-RNTI MAC CE中的C-RNTI，今为C，并从基站侧小区的UE实体中找出C-RNTI为C的UE实体；发送MSG4，采用C-RNTI加扰；
最后，终端接收MSG4。
本实施例中：今基站侧小区为Cell0，Cell0存在集群组呼业务，其G-RNTI为22，小区中存在集群终端UE0，UE0处于RRC_Connected状态并在接收该集群组呼业务，其C-RNTI为33。当基站侧小区Cell0和该终端UE0发生上行数据到达的竞争随机接入过程时，
终端侧UE0：
UE0在MSG3中通过G-RNTI MAC CE携带G-RNTI(为22)告知基站侧小区，MSG3中还包含C-RNTI MAC CE携带UE0的C-RNTI(为33)；该终端通过基站侧小区分配的Temp C-RNTI(今为35)对MSG3加扰。
基站侧Cell0：
基站侧小区Cell0在通过Temp C-RNTI(今为35)接收到MSG3，
从MSG3的C-RNTI MAC CE中解出C-RNTI，为33；从MSG3的G-RNTI MAC CE中解出G-RNTI，为22；则基站侧小区认为C-RNTI为33对应的UE实体存在G-RNTI为22的集群组呼被叫业务。
实施例四：集群业务变更的上报
今基站侧小区为Cell0，Cell0存在集群组呼业务，其G-RNTI为22，小区中存在集群终端UE0，UE0处于RRC_Connected状态并在接收该集群组呼业务，其C-RNTI为33。
Cell0新建立一个G-RNTI为56的集群组呼业务，且UE0也属于该集群组呼。G-RNTI为56的组呼业务的优先级比G-RNTI为22的组呼业务的优先级高。
UE0接收G-RNTI为56的集群组呼业务的寻呼，并判断G-RNTI为56的组呼业务的优先级比G-RNTI为22的组呼业务的优先级高，则终端进入G-RNTI为56的集群组呼业务后，通过G-RNTI MAC CE向基站侧Cell0上报G-RNTI为56。
基于相同的构思，本发明还提出一种实现上述方法的集群终端，如图10所示，该终端包括上报模块1010，用于有集群业务属性需上报时，通过竞争随机接入的MSG3上报所述集群业务属性给基站。
优选的，当所述集群终端处于RRC_Idle状态且有集群组呼被叫业务时，所述上报模块上报所述集群业务属性给基站。
优选的，所述竞争随机接入是重建立的随机接入。所述重建立的随机接入的触发条件包括：无线链路失败、切换失败、完整性保护失败或RRC连接重配失败。
优选的，所述竞争随机接入是上行数据到达的随机接入。所述上行数据到达的随机接入的触发条件包括：上行失步或没有调度请求资源。
优选的，所述上报模块通过获得所述集群业务属性后的第一个上行数据/信今包上报所述集群业务属性给基站。
优选的，该集群终端还包括接收模块1020，用于当所述集群终端切换到目标小区时，接收所述集群组呼被叫业务在所述目标小区的集群业务属性。该上报模块将所述接收模块所接收的集群业务属性上报给基 站。
优选的，所述集群终端通过所述MSG3的MAC CE或所述第一个上行数据/信今包的MAC CE将集群业务属性上报给基站。
优选的，所述集群业务属性包括但不限于G-RNTI。此时，所述MAC CE是G-RNTI MAC CE。
上述集群终端有集群业务属性需上报的情况包括：集群终端有集群组呼被叫业务时或所述集群组呼被叫业务发生变更时。
基于相同的构思，本发明还提出一种实现如上方法的基站，包括接收模块1110，用于通过集群终端竞争随机接入的MSG3接收所述集群终端上报的集群业务属性。
该接收模块，还用于通过集群终端上行数据/信今包接收所述集群终端上报的集群业务属性。
该基站还包括处理模块1120，用于在接收所述MSG3的MAC CE或所述上行数据/信今包MAC CE后，解出所述集群终端上报的集群业务属性。
优选的，所述集群业务属性包括但不限于G-RNTI。此时，所述MAC CE是G-RNTI MAC CE。
基于相同的构思，最后本发明还提出一种集群业务属性处理的系统，如图12所示，该系统包括如上所述的所述终端1210和所述基站1220。
图13示出了根据本发明一个实施例的集群业务属性上报的终端的硬件结构示意图。如图13所示，所述硬件包括一个或多个处理器1310、存储器1320以及存储在存储器1320上用来由一个或多个处理器1310来执行的一个或多个程序指令，例如包括执行前述方法实施例中各步骤的指令，即上报指令1321和接收指令1322，其详细过程见方法实施例中关于终端侧方法的描述或者关于终端侧装置的描述。
图14示出了根据本发明另一实施例的集群业务属性接收的基站的硬件示意图。如图14所示，所述硬件包括一个或多个处理器1410、存储器1420以及存储在存储器1420上用来由一个或多个处理器1410来执行的一个或多个程序指令，例如包括执行前述方法实施例中各步骤的指令，即接收指令1421和处理指令1422，其详细过程见方法实施例中关于基站侧方法的描述或者关于基站侧装置的描述。
由以上的具体说明能够看出，本发明可以在基站侧不增加空口信今的前提下即可获知该小区下的终端是否正处于某个集群组呼被叫业务，很好地解决了基站并不知道本小区内哪些终端在接收该组呼的局限性问题。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (37)

  1. 一种集群业务属性上报方法，其特征在于，包括：
    集群终端有集群业务属性需上报时，所述集群终端通过竞争随机接入的第三消息MSG3上报所述集群业务属性给基站。
  2. 根据权利要求1所述的方法，其特征在于，所述集群终端有集群业务属性需上报的情况包括：集群终端有集群组呼被叫业务时或所述集群组呼被叫业务发生变更时。
  3. 根据权利要求1或2所述的方法，其特征在于，当所述集群终端处于无线资源控制空闲RRC_Idle状态且有集群组呼被叫业务时，所述集群终端上报所述集群业务属性给基站。
  4. 根据权利要求1或2所述的方法，其特征在于，所述竞争随机接入是重建立的随机接入。
  5. 根据权利要求4所述的方法，其特征在于，所述重建立的随机接入的触发条件包括：无线链路失败、切换失败、完整性保护失败或RRC连接重配失败。
  6. 根据权利要求1或2所述的方法，其特征在于，所述竞争随机接入是上行数据到达的随机接入。
  7. 根据权利要求6所述的方法，其特征在于，所述上行数据到达的随机接入的触发条件包括：上行失步或没有调度请求资源。
  8. 根据权利要求1所述的方法，其特征在于，该方法还包括：所述集群终端通过获得所述集群业务属性后的第一个上行数据/信令包上报所述集群业务属性给基站。
  9. 根据权利要求8所述的方法，其特征在于，所述集群终端有集群业务属性需上报的情况包括：集群终端有集群组呼被叫业务时或所述集 群组呼被叫业务发生变更时。
  10. 根据权利要求8或9所述的方法，其特征在于，当所述集群终端切换到目标小区时，所述集群终端在收到所述集群组呼被叫业务在所述目标小区的集群业务属性后，上报所述集群业务属性给基站。
  11. 根据权利要求8～10任意一项所述的方法，其特征在于，所述集群终端通过所述MSG3的媒质接入控制信道资源MAC CE或所述第一个上行数据/信令包的MAC CE将集群业务属性上报给基站。
  12. 根据权利要求1～11任意一项所述的方法，其特征在于，所述集群业务属性包括但不限于群组无线网络临时标识G-RNTI。
  13. 根据权利要求12所述的方法，其特征在于，所述MAC CE是G-RNTI MAC CE。
  14. 一种集群业务属性接收方法，其特征在于，包括：基站通过集群终端竞争随机接入的第三消息MSG3接收所述集群终端上报的集群业务属性。
  15. 根据权利要求14所述的方法，其特征在于，该方法还包括：基站通过集群终端上行数据/信令包接收所述集群终端上报的集群业务属性。
  16. 根据权利要求14或15所述的方法，其特征在于，所述基站接收所述MSG3的媒质接入控制信道资源MAC CE或所述上行数据/信令包MAC CE，解出所述集群终端上报的集群业务属性。
  17. 根据权利要求14～16任意一项所述的方法，其特征在于，所述集群业务属性包括但不限于群组无线网络临时标识G-RNTI。
  18. 根据权利要求17所述的方法，其特征在于，所述MAC CE是G-RNTI MAC CE。
  19. 一种集群终端，其特征在于，所述集群终端包括：上报模块， 用于当所述集群终端有集群业务属性需上报时，通过竞争随机接入的第三消息MSG3上报所述集群业务属性给基站。
  20. 根据权利要求19所述的集群终端，其特征在于，所述有集群业务属性需上报的情况包括：所述集群终端有集群组呼被叫业务时或所述集群组呼被叫业务发生变更时。
  21. 根据权利要求19或20所述的集群终端，其特征在于，当所述集群终端处于无线资源控制空闲RRC_Idle状态且有集群组呼被叫业务时，所述上报模块上报所述集群业务属性给基站。
  22. 根据权利要求19或20所述的集群终端，其特征在于，所述竞争随机接入是重建立的随机接入。
  23. 根据权利要求22所述的集群终端，其特征在于，所述重建立的随机接入的触发条件包括：无线链路失败、切换失败、完整性保护失败或RRC连接重配失败。
  24. 根据权利要求19或20所述的集群终端，其特征在于，所述竞争随机接入是上行数据到达的随机接入。
  25. 根据权利要求24所述的集群终端，其特征在于，所述上行数据到达的随机接入的触发条件包括：上行失步或没有调度请求资源。
  26. 根据权利要求19所述的集群终端，其特征在于，所述上报模块通过获得所述集群业务属性后的第一个上行数据/信令包上报所述集群业务属性给基站。
  27. 根据权利要求26所述的集群终端，其特征在于，所述有集群业务属性需上报的情况包括：所述集群终端有集群组呼被叫业务时或所述集群组呼被叫业务发生变更时。
  28. 根据权利要求26或27所述的集群终端，其特征在于，所述集群终端还包括接收模块，用于当所述集群终端切换到目标小区时，接收 所述集群组呼被叫业务在所述目标小区的集群业务属性；
    所述上报模块将所述接收模块所接收的集群业务属性上报给基站。
  29. 根据权利要求19～28任意一项所述的集群终端，其特征在于，所述上报模块通过所述MSG3的媒质接入控制信道资源MAC CE或所述第一个上行数据/信令包的MAC CE将集群业务属性上报给基站。
  30. 根据权利要求29～30任意一项所述的集群终端，其特征在于，所述集群业务属性包括但不限于群组无线网络临时标识G-RNTI。
  31. 根据权利要求30所述的集群终端，其特征在于，所述MAC CE是G-RNTI MAC CE。
  32. 一种基站，其特征在于，所述基站包括接收模块，用于通过集群终端竞争随机接入的第三消息MSG3接收所述集群终端上报的集群业务属性。
  33. 根据权利要求32所述的基站，其特征在于，所述接收模块，还用于通过集群终端上行数据/信令包接收所述集群终端上报的集群业务属性。
  34. 根据权利要求32或33所述的基站，其特征在于，所述基站还包括处理模块，用于在接收所述MSG3的媒质接入控制信道资源MAC CE或所述上行数据/信令包MAC CE后，解出所述集群终端上报的集群业务属性。
  35. 根据权利要求32～34任意一项所述的基站，其特征在于，所述集群业务属性包括但不限于群组无线网络临时标识G-RNTI。
  36. 根据权利要求35所述的基站，其特征在于，所述MAC CE是G-RNTI MAC CE。
  37. 一种集群业务属性处理的系统，其特征在于，包括如权利要求19～31任意一项所述的集群终端和如权利要求32～36任意一项所述的 基站。
PCT/CN2014/094477 2013-12-23 2014-12-22 集群业务属性上报和接收的方法、装置和系统 WO2015096673A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/309,484 US20170150529A1 (en) 2013-12-23 2014-12-22 Method, Device and System for Reporting and Receiving Trunked Service Attribute

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310716929.X 2013-12-23
CN201310716929.XA CN104735627A (zh) 2013-12-23 2013-12-23 集群业务属性上报和接收的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2015096673A1 true WO2015096673A1 (zh) 2015-07-02

Family

ID=53458973

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/094477 WO2015096673A1 (zh) 2013-12-23 2014-12-22 集群业务属性上报和接收的方法、装置和系统

Country Status (3)

Country Link
US (1) US20170150529A1 (zh)
CN (1) CN104735627A (zh)
WO (1) WO2015096673A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104703145B (zh) * 2013-12-09 2018-05-11 北京信威通信技术股份有限公司 集群组呼盲检能力处理方法、装置和系统
US11659563B2 (en) * 2017-01-04 2023-05-23 Huawei Technologies Co., Ltd. System and method for user equipment identifier configuration
CN110139226B (zh) * 2018-02-09 2021-07-16 成都鼎桥通信技术有限公司 一种基于B-TrunC的群组状态处理方法和设备
WO2019161545A1 (zh) * 2018-02-23 2019-08-29 Oppo广东移动通信有限公司 完整性校验方法、网络设备、终端设备及计算机存储介质
WO2020088498A1 (en) * 2018-10-30 2020-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Methods and devices for random access
WO2020181408A1 (en) * 2019-03-08 2020-09-17 Qualcomm Incorporated Interference management for two-step random access
CN113872736B (zh) * 2020-06-30 2023-08-18 成都鼎桥通信技术有限公司 数据传输方法、装置、设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102264052A (zh) * 2010-05-28 2011-11-30 中国移动通信集团公司 网络侧触发终端通信的方法、装置及系统
CN103067880A (zh) * 2013-01-09 2013-04-24 中兴通讯股份有限公司 一种发送集群消息的方法和网络侧设备、终端设备
CN103078704A (zh) * 2012-12-28 2013-05-01 中兴通讯股份有限公司 一种管理调制编码方式的方法和系统
CN103220632A (zh) * 2012-01-20 2013-07-24 鼎桥通信技术有限公司 集群系统下行覆盖自适应调整方法、基站及群组用户设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102111839B (zh) * 2009-12-25 2013-07-31 普天信息技术研究院有限公司 一种实现切换的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102264052A (zh) * 2010-05-28 2011-11-30 中国移动通信集团公司 网络侧触发终端通信的方法、装置及系统
CN103220632A (zh) * 2012-01-20 2013-07-24 鼎桥通信技术有限公司 集群系统下行覆盖自适应调整方法、基站及群组用户设备
CN103078704A (zh) * 2012-12-28 2013-05-01 中兴通讯股份有限公司 一种管理调制编码方式的方法和系统
CN103067880A (zh) * 2013-01-09 2013-04-24 中兴通讯股份有限公司 一种发送集群消息的方法和网络侧设备、终端设备

Also Published As

Publication number Publication date
US20170150529A1 (en) 2017-05-25
CN104735627A (zh) 2015-06-24

Similar Documents

Publication Publication Date Title
JP7185697B2 (ja) 補助アップリンクによるアップリンクキャリア構成および選択
WO2021093431A1 (zh) 非连接态ue的数据传输、接收方法及装置、终端、基站
US11457431B2 (en) Sidelink radio resource allocation
US10149339B2 (en) Base station, user equipment and methods for random access
JP6590030B2 (ja) ユーザ装置、基地局、及び制御方法
JP7066736B2 (ja) 無線アクセスネットワーク更新手順に参加するユーザ機器および基地局
WO2015096673A1 (zh) 集群业务属性上报和接收的方法、装置和系统
US20200373992A1 (en) Contention based random access for beam failure recovery
US10785808B2 (en) Random access method and equipment
US20180160454A1 (en) Data Transmission Method, Device and System
WO2016144084A1 (en) Method for operating a fast random access procedure in a wireless communication system and a device therefor
WO2010127520A1 (zh) 随机接入方法以及基站
WO2021170110A1 (zh) 一种通信方法及装置
CN116546573A (zh) 网络切片信息处理方法、终端设备和网络设备
WO2022183970A1 (zh) 一种通信方法及设备
US20240214862A1 (en) Method, device and computer storage medium of communication
CN106341896B (zh) 一种数据传输方法和设备、系统
WO2021148053A1 (zh) 一种信息传输方法、装置及相关设备
TWI824322B (zh) 小資料傳輸程序至隨機存取程序回退
TW202318906A (zh) 用於小資料傳輸之排程請求及隨機接取觸發技術
WO2018227510A1 (zh) 接入控制方法及相关产品
CN116347651A (zh) 无线通信方法、终端设备和网络设备
WO2024051523A1 (zh) 切换方法及装置
RU2791244C1 (ru) Способ и устройство произвольного доступа
US20240267860A1 (en) Methods performed by nodes, and nodes

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15309484

Country of ref document: US

122 Ep: pct application non-entry in european phase

Ref document number: 14873880

Country of ref document: EP

Kind code of ref document: A1