CN107580372B - Random access method in V2X network - Google Patents
Random access method in V2X network Download PDFInfo
- Publication number
- CN107580372B CN107580372B CN201610518489.0A CN201610518489A CN107580372B CN 107580372 B CN107580372 B CN 107580372B CN 201610518489 A CN201610518489 A CN 201610518489A CN 107580372 B CN107580372 B CN 107580372B
- Authority
- CN
- China
- Prior art keywords
- random access
- service
- rrc connection
- terminal
- vehicle
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The application discloses a random access method in a V2X network, which comprises the following steps: when the contention-based random access is performed, the Vehicle-UE or UE-type RSU carries a terminal indication identifier in the Msg3 sent to the network side, and the terminal indication identifier is used for indicating whether the UE subjected to the random access is the Vehicle-UE or the UE-type RSU; the eNodeB selects an accessed terminal according to the terminal indication identifier; wherein, the vessel-UE or the UE-type RSU takes priority over the standard terminal to perform access processing. By the application, the time delay of the V2X service can be reduced.
Description
Technical Field
The present application relates to an access technology in a communication system, and in particular, to a random access method in a V2X network.
Background
V2X (Vehicle to X), namely information exchange between a Vehicle and the outside, is a key technology of a future intelligent transportation system. V2X was approved at 3GPP RAN #68 conference, mainly studying vehicle data transmission schemes based on 3GPP communication protocols. V2X communication includes V2V communication (vehicle-to-vehicle communication), V2I communication (vehicle-to-roadside infrastructure communication), and V2P communication (vehicle-to-pedestrian communication). The application of V2X will improve driving safety, reduce congestion and vehicle energy consumption, improve traffic efficiency and vehicle-mounted entertainment information, etc.
In the prior art, a Dedicated Short Range Communications (DSRC) technology is usually adopted to transmit the V2X service, but the transmission index (such as communication distance, delay or reliability) of the DSRC technology cannot meet the technical requirement of the V2X service on the transmission index. In particular, the delay problem of the current V2X service is more prominent.
Disclosure of Invention
The application provides a random access method in a V2X network, which can reduce the time delay of V2X service.
In order to achieve the purpose, the following technical scheme is adopted in the application:
a random access method in a V2X network, comprising:
when the contention-based random access is performed, the Vehicle-UE or UE-type RSU carries a terminal indication identifier in the Msg3 sent to the network side, and the terminal indication identifier is used for indicating whether the UE subjected to the random access is the Vehicle-UE or the UE-type RSU;
the eNodeB selects an accessed terminal according to the terminal indication identifier; wherein, the vessel-UE or the UE-type RSU takes priority over the standard terminal to perform access processing.
Preferably, the method further comprises: and carrying a service indication identifier in the Msg3, wherein the service indication identifier is used for indicating whether random access is related to V2X.
Preferably, the Msg3 sent to the network side carries a terminal indicator and/or a service indicator, including: for the competitive random access performed due to the initial access, the terminal indication identifier is carried in the RRC connection establishment request message, or the terminal indication identifier and the service indication identifier are carried in the RRC connection establishment request message; for the contention-based random access due to connection reestablishment, the terminal indication identifier is carried in the RRC connection reestablishment message, or the terminal indication identifier and the service indication identifier are carried in the RRC connection reestablishment message.
Preferably, the carrying of the terminal indication identifier in the RRC connection establishment request message includes:
the RRC connection establishment request message carries a Vehicle-mounted terminal identification which is used for indicating whether the UE which is randomly accessed is a Vehicle-UE; and when the UE-type RSU exists in the system, adding a reason value of the UE-type RSU in the establishment reason information element of the RRC connection establishment request message for indicating that the UE with random access is the UE-type RSU.
Preferably, the carrying of the terminal indication identifier in the RRC connection establishment request message includes:
the RRC connection establishment request message carries a UE type identification which is used for indicating that the UE of random access is a standard terminal, a vessel-UE or a UE-type RSU.
Preferably, the carrying of the service indication identifier in the RRC connection setup request message includes: when the randomly accessed Vehicle-UE carries out the emergency V2X service, setting the establishment reason information element of the RRC connection establishment request message as the emergency; and when the randomly accessed Vehicle-UE carries out non-emergency V2X service, setting the establishment cause information element of the RRC connection establishment request message as highPriorityAccess.
Preferably, the carrying of the terminal indicator and the service indicator in the RRC connection setup request message includes:
the RRC connection establishment request message carries a UE-type RSU identifier which is used for indicating whether the UE which is randomly accessed is the UE-type RSU or not;
and when the UE with random access is a Vehicle-UE and the random access is triggered by the V2X service, setting the establishment reason information element of the RRC connection establishment request message as V2 XAccess.
Preferably, the carrying of the terminal indication identifier in the RRC connection reestablishment message includes:
carrying a vehicle-mounted terminal identification and a UE-type RSU identification in the RRC connection reestablishment message; the Vehicle-mounted terminal identification is used for indicating whether the UE subjected to random access is a Vehicle-UE, and the UE-type RSU identification is used for indicating whether the UE subjected to random access is a UE-type RSU.
Preferably, the carrying of the service indication identifier in the RRC connection reestablishment message includes:
when the UE of the random access is the random access triggered by the service failure of V2X, the reestablishment reason information element of the RRC connection reestablishment message is set to be failed in V2X.
Preferably, the carrying of the terminal indication identifier in the RRC connection establishment request message includes:
the RRC connection establishment request message carries a UE type identification which is used for indicating that the UE of random access is a standard terminal, a vessel-UE or a UE-type RSU.
Preferably, before performing the random access, the method further includes: triggering a vessel-UE or a UE-type RSU to initiate the random access through a service request SR process; the RRC establishment cause of the SR process is set to be highprioritylaccess or emergency, or the RRC establishment cause is set to be a self-defined cause value, which is used to indicate that the random access is for the V2X service.
Preferably, the SR procedure is triggered when a RRC idle state mean-UE requests resources for a V2X service.
Preferably, when the resource request triggering the SR procedure is for non-emergency V2X service, the RRC establishment cause of the SR procedure is set to highprioritylaccess; and/or when the resource request triggering the SR process is for the emergency V2X service, setting the RRC establishment reason of the SR process as the emergency.
According to the technical scheme, when the contention-based random access is performed, the Vehicle-UE or UE-type RSU carries a terminal indication identifier in the Msg3 sent to the network side for indicating whether the randomly-accessed UE is the Vehicle-UE or UE-type RSU; the eNodeB selects an accessed terminal according to the terminal indication identifier; wherein, the vessel-UE or UE-typeRSU takes precedence over the standard terminal to carry out the access processing. Through the processing, the vessel-UE or the UE-type RSU has higher priority than the standard terminal to access the eNodeB, so that the random access delay of the V2X service can be reduced, and further the V2X service delay can be reduced.
Drawings
Fig. 1 is a flowchart illustrating a random access method in a V2X network according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical means and advantages of the present application more apparent, the present application will be described in further detail with reference to the accompanying drawings.
The random access technology is an important technology for media access control in a communication system, and is a necessary process for establishing a radio link between User Equipment (UE) and a network. For V2X service, the delay of the whole V2X service is reduced by reducing the delay of the V2X service random access process.
Next, the problem that the delay of the random access process of the V2X service is large at present is analyzed as follows: for the random access process in the existing 3GPP protocol, the network side is a random access process that cannot identify the UE type and distinguish whether the UE type is triggered by the V2X service. When the UE performs the contention-based random access procedure in the initial access or connection reestablishment scenario, the eNode B cannot know the UE type, nor the random access triggered by the V2X service. Therefore, when the cell load is large, random access triggered by a Vehicle-mounted terminal (Vehicle-UE) or a UE type road side unit (UE-type RSU), particularly random access triggered by the Vehicle-mounted terminal (Vehicle-UE) and the RSU due to emergency V2X service, cannot be specially processed, the success rate of random access of the Vehicle-UE and the RSU under the same condition cannot be guaranteed, extra time delay is introduced in the random access process, and further V2X service delay is increased.
Based on the above analysis, the present application provides a random access method in a V2X network, which specifically includes: when the contention-based random access is performed, the Vehicle-UE or UE-type RSU carries a terminal indication identifier in the Msg3 sent to the network side, and the terminal indication identifier is used for indicating whether the UE subjected to the random access is the Vehicle-UE or the UE-type RSU; the eNodeB selects an accessed terminal according to the terminal indication identifier; wherein, the vessel-UE or the UE-type RSU takes priority over the standard terminal to perform access processing.
The above is the basic method for performing random access for the Vehicle-UE or UE-type RSU provided in this application. For how to trigger the vessel-UE or UE-type RSU for random access, the following method may be adopted: triggering a random access procedure through a Service Request (SR) procedure; the RRC establishment cause of the SR procedure is set to be highprioritylaccess or emergency, or set to be a newly added cause value, which is used to indicate that the triggered random access is for the V2X service.
The following describes a specific implementation of the random access method in the present application by using a specific embodiment shown in fig. 1.
When the emm (eps Mobility management) requests NAS signaling connection establishment, the UE may select an RRC establishment cause according to the NAS procedure. In this embodiment, the method for triggering the random access procedure is to add a trigger scenario of a Service Request (SR) procedure, and when a RRC idle-UE requests resources for a V2X service, trigger the SR procedure and set an RRC establishment cause value to a corresponding RRC establishment cause value.
Specifically, the existing value of the RRC establishment cause may be used to indicate that, when the RRC idle-state vessel-UE requests resources for the non-emergency V2X service, the SR procedure is triggered, and the RRC establishment cause is set to highritylaccess, and when the RRC idle-state vessel-UE requests resources for the emergency V2X service, the SR procedure is triggered, and the RRC establishment cause is set to emergency. And triggering the Vehicle-UE to carry out random access through an SR process, so that the Vehicle-UE enters an RRC connection state. Or expanding the RRC establishment cause value, adding a V2X service access cause value, triggering an SR process when the RRC idle state vessel-UE requests resources for the V2X service, and setting the RRC establishment cause as V2 XAccess.
There are standard terminals and Vehicle-UEs in the system, and even UE-type RSUs. In this embodiment, the UE type of the random access is notified to the network side through the terminal indicator. In this way, the network side can preferentially guarantee the access of the RSU and the vessel-UE, especially the access of the vessel-UE and the RSU of the emergency V2X service.
Specifically, in the V2X network, for a legacy-UE and a UE-type RSU, modifying the content carrying information in the Msg3 in the contention-based random access process; for standard terminals, no changes are made according to the LTE-a protocol specifications. Thus, after receiving the Msg3, the eNode B can determine whether the UE is a legacy-UE or a UE-type RSU through the content of the information carried in the Msg3, and further, when the Msg3 carries the service indicator, can determine whether the random access is related to the V2X service.
In practical application, for a contention-based random access procedure performed due to initial access, an RRC connection request message (RRCConnectionRequest) generated by an RRC layer is carried in Msg 3; for the contention based random access procedure due to connection reestablishment, the Msg3 carries an RRC connection reestablishment request message (rrcconnectionrequest request) generated by the RRC layer. Preferably, the transmission of the terminal indicator and the service indicator can be realized by the extension of the two messages. Specifically, the reserved bits in the RRCConnectionRequest and rrcconnectionrequestabstaining request messages may be used as the terminal indication identifier and the service indication identifier.
The following describes a modification manner of the RRC connection request message and the RRC connection reestablishment request message sent by the Vehicle-UE and the UE-type RSU by taking the LTE Rel-13 protocol as an example. For standard terminals, the RRC connection request message and the RRC connection reestablishment request message are not changed.
Modification of RRC connection request message
There are three ways to add the terminal indicator and the service indicator in the RRC connection request message (RRCConnectionRequest):
in a first manner, when the terminal indication identifier is added, a vehicle-mounted terminal identifier may be added to indicate whether the UE is a vehicle-mounted terminal. Meanwhile, if a UE-type RSU exists in the system, a cause value can be newly added in an estabilishment cause cell: UE-type RSU for indicating that the UE is UE-type RSU. If it is necessary to further know whether the vehicle-mounted terminal establishes the triggered random access due to the V2X service, the vehicle-mounted terminal may further carry a service indication identifier, for example, it may be specified that when the vehicle-mounted terminal performs the emergency V2X service, the estabilishment cause is set as emergency; when the vehicle-mounted terminal performs the non-emergency V2X service, the estabilishment cause is set to highloadylaccess.
Table 1 RRCConnectionRequest message
In the second mode, when the terminal indication identifier is added, the UE-type RSU identifier may be added to indicate whether the UE is a UE-type RSU, and if the UE is a UE-type RSU, the RSU identifier is indicated as true. If it is further required to know whether the Vehicle-UE establishes the triggered random access due to the V2X service, the UE may also carry a service indication identifier, for example, a cause value of a new V2X service access (V2XAccess) in the establishment cause estabilishment cause, as shown in table 2, if the UE is a Vehicle-UE and the random access is triggered due to the V2X service, the estabilishment cause is set to be V2 XAccess.
Table 2 RRCConnectionRequest message
And thirdly, when the terminal indication identifier is added, the UE type can be added, and the UE used for indicating the access is a standard terminal, a vessel-UE or a UE-type RSU. Further, the vehicle-mounted terminal can be subdivided into a common vehicle-mounted terminal (such as a private car, etc.), a public transportation vehicle-mounted terminal (such as a bus, a long-distance bus, etc.), and a high-priority vehicle-mounted terminal (such as an ambulance, a fire truck, etc.). As shown in table 3. If it is necessary to further know whether the vehicle-mounted terminal establishes the triggered random access due to the V2X service, the vehicle-mounted terminal may further carry a service indication identifier, for example, it may be specified that when the vehicle-mounted terminal performs the emergency V2X service, the estabilishment cause is set as emergency; when the vehicle-mounted terminal performs the non-emergency V2X service, the estabilishment cause is set to highloadylaccess.
Table 3 RRCConnectionRequest message
(II) modification of RRC connection reestablishment request message
As for the manner of adding the terminal indicator and the service indicator in the RRC connection reestablishment request message (rrcconnectionrequest request), there may be two types:
in a first manner, when the terminal indication identifier is added, a vehicle-mounted terminal identifier may be added to indicate whether the UE is a vehicle-mounted terminal, and a UE-type RSU identifier is added to indicate whether the UE is a UE-type RSU, as shown in table 4. If it is necessary to further know whether the random access triggered by the UE is related to the V2X service, the UE may also carry a service indication identifier, for example, when the UE is the random access triggered by the service failure of V2X, a reestablishment reason of V2XFailure needs to be added to the reestablishment cause of the rrcconnectionresestopablisterequest cell, and the reestablishment cause is set to be V2 XFailure.
TABLE 4 RRCConnectionrequestrequest cell
In the second mode, when the terminal indication identifier is added, the UE type may be added, and the UE for indicating the access is a standard terminal, a vessel-UE, or a UE-type RSU. Further, the in-vehicle terminals may be subdivided into general in-vehicle terminals (e.g., private cars, etc.) and high-priority in-vehicle terminals (e.g., ambulances, fire engines, etc.), as shown in table 5.
TABLE 5 RRCConnectionrequestrequest cell
And 103, the eNodeB selects an accessed terminal according to the terminal indication identifier.
Wherein, the vessel-UE or the UE-type RSU takes priority over the standard terminal to perform access processing.
After receiving msgs 3 sent by a plurality of UEs on the same subframe, the eNode B learns whether a user belongs to an on-board terminal or a UE-type RSU and whether the terminal initiates random access due to accessing of the V2X service or not according to the content of information carried in the Msg3, and even can learn whether the V2X service is urgent. According to the types of the users and the establishment reasons, the users are prioritized, and the access of the vehicle-mounted terminal and/or the RSU, particularly the vehicle-mounted terminal of the V2X service, is preferentially ensured. The specific principle of priority ranking can be made according to the requirements of different customers. When the cell load is large, other standard terminals, except for the standard terminal whose establishment cause is an emergency, refuse access.
The method flow in this embodiment is ended.
By the random access method, the access of the Vehicle-UE or the UE-type RSU to the V2X network can be preferentially ensured, the random access time delay is reduced, and the time delay of the whole V2X service is further reduced.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (7)
1. A random access method in a V2X network, comprising:
when the contention-based random access is carried out, a Vehicle-UE or UE-type RSU carries a terminal indication identifier and/or a service indication identifier in the Msg3 sent to the network side; the terminal indication mark is used for indicating whether the UE of the random access is a vessel-UE or a UE-type RSU, and the service indication mark is used for indicating whether the random access is related to V2X;
the eNodeB selects an accessed terminal according to the terminal indication identifier; wherein, the vessel-UE or UE-type RSU takes precedence over the standard terminal to carry out the access processing;
the Msg3 sent to the network side carries a terminal indicator and/or a service indicator, including: for the competitive random access performed due to the initial access, the terminal indication identifier is carried in the RRC connection establishment request message, or the terminal indication identifier and the service indication identifier are carried in the RRC connection establishment request message; for the competitive random access due to connection reestablishment, the terminal indication identifier is carried in the RRC connection reestablishment message, or the terminal indication identifier and the service indication identifier are carried in the RRC connection reestablishment message;
the carrying of the terminal indication identifier in the RRC connection establishment request message includes: the RRC connection establishment request message carries a Vehicle-mounted terminal identification which is used for indicating whether the UE which is randomly accessed is a Vehicle-UE; when UE-type RSU exists in the system, increasing the cause value of the UE-type RSU in the establishment cause cell of the RRC connection establishment request message, wherein the cause value is used for indicating that the UE which is accessed randomly is the UE-type RSU;
the carrying of the terminal indication identifier and the service indication identifier in the RRC connection establishment request message includes:
the RRC connection establishment request message carries a UE-type RSU identifier which is used for indicating whether the UE which is randomly accessed is the UE-type RSU or not;
and when the UE with random access is a Vehicle-UE and the random access is triggered by the V2X service, setting the establishment reason information element of the RRC connection establishment request message as V2 XAccess.
2. The method of claim 1, wherein the carrying the traffic indication identifier in the RRC connection setup request message comprises: when the randomly accessed Vehicle-UE carries out the emergency V2X service, setting the establishment reason information element of the RRC connection establishment request message as the emergency; and when the randomly accessed Vehicle-UE carries out non-emergency V2X service, setting the establishment cause information element of the RRC connection establishment request message as highPriorityAccess.
3. The method according to claim 1, wherein the carrying the terminal indication identifier in the RRC connection reestablishment message comprises:
carrying a vehicle-mounted terminal identification and a UE-type RSU identification in the RRC connection reestablishment message; the Vehicle-mounted terminal identification is used for indicating whether the UE subjected to random access is a Vehicle-UE, and the UE-type RSU identification is used for indicating whether the UE subjected to random access is a UE-type RSU.
4. The method according to claim 1 or 3, wherein the carrying of the traffic indication identifier in the RRC connection reestablishment message comprises:
when the UE of the random access is the random access triggered by the service failure of V2X, the reestablishment reason information element of the RRC connection reestablishment message is set to be failed in V2X.
5. The method of claim 1, wherein prior to performing the random access, the method further comprises: triggering a vessel-UE or a UE-type RSU to initiate the random access through a service request SR process; the RRC establishment cause of the SR process is set to be highprioritylaccess or emergency, or the RRC establishment cause is set to be a self-defined cause value, which is used to indicate that the random access is for the V2X service.
6. The method of claim 5, wherein the SR process is triggered when a RRC idle state Vehicle-UE requests resources for V2X traffic.
7. The method of claim 6, wherein when the resource request triggering the SR process is for non-emergency V2X traffic, the RRC establishment cause of the SR process is set to highPrioritityAccess; and/or when the resource request triggering the SR process is for the emergency V2X service, setting the RRC establishment reason of the SR process as the emergency.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610518489.0A CN107580372B (en) | 2016-07-04 | 2016-07-04 | Random access method in V2X network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610518489.0A CN107580372B (en) | 2016-07-04 | 2016-07-04 | Random access method in V2X network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107580372A CN107580372A (en) | 2018-01-12 |
| CN107580372B true CN107580372B (en) | 2020-01-24 |
Family
ID=61049813
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610518489.0A Active CN107580372B (en) | 2016-07-04 | 2016-07-04 | Random access method in V2X network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107580372B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108898824B (en) * | 2018-07-25 | 2021-06-29 | 公安部交通管理科学研究所 | Intersection bus signal priority control system and control method based on C-V2X |
| CN111818618B (en) * | 2019-04-12 | 2022-03-08 | 华为云计算技术有限公司 | Communication network determination method, device and system |
| CN112840738B (en) * | 2019-06-18 | 2023-05-12 | Oppo广东移动通信有限公司 | Wireless communication method and communication device |
| EP3979754A1 (en) * | 2020-10-02 | 2022-04-06 | Nokia Technologies Oy | Initial access |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546981A (en) * | 2012-07-16 | 2014-01-29 | 普天信息技术研究院有限公司 | Method and device for realizing competition-type random access |
| CN105128816A (en) * | 2015-09-14 | 2015-12-09 | 广东顺德车联管家科技有限公司 | Vehicle control method and vehicle-mounted terminal |
| CN105592512A (en) * | 2016-03-08 | 2016-05-18 | 中国联合网络通信集团有限公司 | RRC connection establishing method, terminal and base station |
-
2016
- 2016-07-04 CN CN201610518489.0A patent/CN107580372B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546981A (en) * | 2012-07-16 | 2014-01-29 | 普天信息技术研究院有限公司 | Method and device for realizing competition-type random access |
| CN105128816A (en) * | 2015-09-14 | 2015-12-09 | 广东顺德车联管家科技有限公司 | Vehicle control method and vehicle-mounted terminal |
| CN105592512A (en) * | 2016-03-08 | 2016-05-18 | 中国联合网络通信集团有限公司 | RRC connection establishing method, terminal and base station |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107580372A (en) | 2018-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107040972B (en) | Path selection method and device | |
| EP3592025B1 (en) | Method and device for configuring radio resource, and storage medium | |
| CN109152076B (en) | Method, device and system for scheduling communication resources | |
| WO2018166508A1 (en) | Resource allocation method and apparatus, resource reservation method and apparatus, and storage medium | |
| US9942879B2 (en) | Method and apparatus for avoiding resource collision in mobile communication system | |
| CN108174438B (en) | Signal transmission method of P-UE | |
| WO2018177109A1 (en) | Data transmission method and device, terminal, and storage medium | |
| WO2017041355A1 (en) | Method and device for controlling v2x service transmission | |
| US20180160418A1 (en) | Method and device for resource allocation | |
| WO2017028699A1 (en) | Resource occupation method, device, and user equipment | |
| CN107580372B (en) | Random access method in V2X network | |
| WO2016176970A1 (en) | Method and device for resource configuration | |
| WO2016206464A1 (en) | Method and apparatus for processing internet of vehicles services | |
| EP3537802A1 (en) | Subframe configuration method and device | |
| WO2016206458A1 (en) | Method and apparatus for processing alarm information in internet of vehicles | |
| EP3277048B1 (en) | Data transmission and resource scheduling methods and devices and computer program product | |
| CN106162924B (en) | Method, device and system for accessing network | |
| KR20180054785A (en) | Control signaling processing method, apparatus, and device | |
| CN107113819B (en) | Communication equipment, network equipment and equipment-to-equipment data transmission method | |
| CN111149400B (en) | Method for directly connecting link data transmission, terminal equipment and network equipment | |
| CN110178432B (en) | Service data transmission method and device | |
| US11277722B2 (en) | Method for operating a roadside network unit and roadside network unit | |
| US20240015703A1 (en) | User equipment and resource monitoring method in sidelink communication | |
| US10278195B2 (en) | Serving node establishment method and device | |
| US20230224983A1 (en) | Broadcast-based unicast session method and apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |