`
`Patentamt
`European
`Patent Office
`Office européen
`des brevets
`
`Bescheinigung
`
`Certificate
`
`Attestation
`
`Die angehefteten
`Unterlagen stimmen mit der
`als urspringlich eingereicht
`geltenden Fassung der auf
`dem nachsten Blatt
`bezeichneten europaischen
`Patentanmeldung Uberein.
`
`The attached documents are
`exact copies of the text in
`which the European patent
`application described on the
`following page is deemed to
`have been filed.
`
`Les documentsjoints a la
`présente attestation sont
`conformesautexte,
`considéré comme
`initialement déposé, de la
`demande de brevet
`européen qui est spécifiée a
`la page suivante.
`
`
`
`Patentanmeldung Nr.
`
`Patent application No.
`
`Demande de brevet n°
`
`18197357.9 / EP18197357
`
`The organisation code and number of your priority application, to be used for filing abroad under the Paris
`Convention, is EP18197357.
`
`Der Prasident des Europaischen Patentamts;
`Im Auftrag
`For the President of the European Patent Office
`Le President de l'Office européen des brevets
`p.o.
`
`EPA/EPO/OEB Form 1014
`
`05.17
`
`V. Joseph
`
`
`
`
`
`Anmeldung Nr:
`Application no.:
`Demande no :
`
`18197357.9
`
`Anmelder/ Applicant(s) / Demandeur(s):
`
`FRAUNHOFER-GESELLSCHAPFTzur Férderung
`der angewandten Forschung e.V.
`HansastraBe 27c
`80686 Miinchen/DE
`
`Anmeldetag:
`Date offiling:
`Date de dépét :
`
`27.09.18
`
`Bezeichnung der Erfindung / Title of the invention / Titre de I'invention:
`(Falls die Bezeichnung der Erfindung nicht angegeben ist, oderfalls die Anmeldung in einer Nicht-Amtssprache des EPA eingereicht
`wurde, siehe Beschreibung beziglich urspriinglicher Bezeichnung.
`If no title is shown, orif the application has been filed in a non-EPO language, please refer to the description for the originaltitle.
`Si aucun titre n'est indiqué, ou si la demande a été déposée dans une langue autre qu'une langue officielle de l'OEB, se référer ala
`description pour le titre original.)
`
`Groupcast / Group ID Management
`
`In Anspruch genommenePrioritat(en) / Priority(Priorities) claimed / Priorité(s) revendiquée(s)
`Staat/Tag/Aktenzeichen / State/Date/File no. / Pays/Date/Numéro de dépét:
`
`Am Anmeldetag benannte Vertragstaaten / Contracting States designated at date offiling / Etats contractants désignés lors du dépét:
`
`AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL
`PT RO RS SE SI SK SMTR
`
`EPA/EPO/OEB Form 1014
`
`05.17
`
`2
`
`
`
`1
`
`Document Overview
`
`1.1 Document Scope
`This documentdescribes low latency variants on how to assign group IDs / group internal IDs specifically
`for the newly introduced groupcast managementin Rel-16 for V2X using NR.
`
`1.2 References
`
`Reference Label
`(use Word bookmarks
`
`
`
`
`
`Details
`
`TR 36.885
`
`1.3 Abbreviations
`
`Cee
`
`
`
`Abbreviation
`
`| Meaning
`
`
`
`
`itrallzedEnvironmental Jo
`
`PhysiealSidelink Control Channel
`
` DENM|
`
`Dedicated Short Range Communication
`
`
`
`h?
`
`
`
`o?
`
`1.4 Table of Contents
`
`Document Overview
`
`Document Scope
`References
`
`Abbreviations
`
`Table of Contents
`
`Detailed Description of the invention
`Technical Problem Statement(1)
`State of the Art, Related Patents (2)
`Assessment of the Invention
`Benefits of the Invention (4a)
`Solution / Approach(3)
`Workarounds
`Proof of Infringements
`Technical Application Area (5)
`Claims
`
`1 1
`
`4
`
`1.2
`
`1.3
`
`1.4
`
`2 2
`
`.4
`
`2.2
`
`2.3
`2.3.1
`
`2.4
`2.4.1
`2.4.2
`
`2.5
`
`
`
`2
`
`Detailed Description of the Invention
`
`2.4. Technical Problem Statement(1)
`
`including Rel-15 the LTE based V2X sidelink communication is using broadcast only. Only with Rel-16
`(using NR for the sidelink) the advanced use cases in NR such as the vehicle platooning and advanced
`driving need groupcast based sidelink communication [2]. This invention describes new solutions on “How
`to assign group (internal) IDs, especially required for low latency demanding use cases.”
`
`2.2 State of the Art, Related Patents (2)
`
`
`Current solutions are mostly solved at the application layer in the IEEE 802.a1p, which may be neither
`applicable norfulfill the latency requirements for 5G V2X use casesin Rel 16[1].
`The decision of who is the group or platoon head is usually been tackled in DSRC within the application
`layer by defining Group ID’s in the CAM messages. This is one possibility that can be adapted by the NR-
`Vax thatin the application layer a “Group ID “is defined within the CAM and DENM messages. Only the
`vehicles that can decode this Group ID become a member of the platoon. This solution however, willlead
`to a higher delay in decoding the messages and may notfit the stringent latency requirements as these are
`broadcasted every 100 ms[2]. This will also create issues when the platoon member wantsto leave the
`platoon. Then the information will reach only after 100 ms the remaining platoon members until when the
`platoon dynamics will have changed.
`
`2.3 Assessment of the Invention
`
`2.3.4 Benefits of the invention (4a)
`
`
`
`The solution proposesto use the lower layers for the group ID managementin order to fulfil the latency
`constraints.
`
`2.4 Solution / Approach (3)
`The solution is partly described for the platooning use case, which is seen as the most prominent use case
`for groupcast in V2X. However, the solution is neither limited to platooning nor to V2X, but is applicable to
`groupcast in 5G groupcast managementin general.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`
`
`A platoon consists of platoon head and platoon members. The platoon members follow the platoon head
`at a (pre-) defined or fixed or adapted distance and with a (pre-) defined or fixed or adapted speed (see
`figure 1 and figure 2).
`
`35~~For the following description of the solution, few groupcast related terms need to beinitially defined:
`
`®
`
`e
`
`The group ID identifies the group.. Each group member has to know the group ID of the group(s) it
`belongs to. One example of the group ID is the platoon ID.
`Each group consists of one or (usually) multiple group members:
`
`o Group head (GH): Per group there might be one group head taking over some controlling
`
`|;
`
`- 7
`a
`
`GroupMead
`
`Ne
`* —
`
`Grou mambert
`
`40
`
`. ne
`
`Centralized groupcast
`
`-
`
`“
`
`Figure 4
`
`45
`
`o Group without group head: No dedicated group head or controlling function is assigned. This
`type of group is referred to as decentralized / distributed group,figure 2.
`
`~,
`
`* s
`
`‘,
`/
`/
`em
`
`||
`
`”
`yf
`i
`\
`Ne
`on
`
`
`
`Group members
`
`sv
`
`ne
`
`De-centralized groupcast (all members are equal) ee
`
`Figure 2
`
`50~—_The 2 ideas below provide 3 variants of how to improve and accelated the group id assignment by using
`
`lower layers.
`
`
`
`
`
`Defintions
`
`Group ID refers to either of the options below
`
`eo@8@@
`
`Group Destination ID
`Group Source ID
`Group Destination and Source ID (combination of both)
`Common Group ID (unique identification)
`
`Sidelink (SL) refers to D2D sidelink, MaM sidelink, or V2X sidelink.
`
`55
`
`60
`
`Variant 1 to 3 represent different embodiments.
`
`a1. Variant:
`
`Make changesin the sidelink control channel PSCCH and the SCI format tosatisfy the latency
`requirements.
`
`65
`
`e Adda Group ID in the SCI format 1. There are reserved 32 information bits set to zero out of which
`all or sore (e.g. 8) bits can be used to define a Group ID, which could beconfigured / set by the
`application layer.
`
`79
`
`75
`
`80
`
`85
`
`go
`
`
`
`2. Variant (enhancementof x. variant):
`
`Scramble the SCI information, or part of the SCI information with the Group ID.
`
`3. Variant:
`For the Group ID a new RNTIis introduced, e.g. called “group sidelink (GSL)’-RNTI. It is defined during
`the group setup and has to be unique for a certain area (e.g. within a certain network,cell, or zone, ifin
`coverage).
`
`-
`
`Note1:
`-
`The, e.g., group RNTI or GSL-RNTI, has to be selected for a network connected group head or
`group-head and multiple members
` Inanincoverage scenario the RNTI, e.g., group RNTI or GSL-RNTI, and further invinted RNTI,e.g.,
`group RNTI or GSL-RNTI,
`in this document has to be mapped to the networkidentifiers
`- Once the GH is out of coverage, a temporary local RNTI, e.g., group RNTI or GSL-RNTI, has to be
`considered until the next in coverage.
`- Once the UEsare in coverage again, either this local RNTI, e.g., group RNTI or GSL-RNTI, has to be
`mapped to the network new RNTIor update the group RNTI, e.g., group RNTI or GSL-RNTI, once
`the RRC is connected.
`
`3-1 Scenario: Out-of-coverage /idle mode
`
`If the UE is out-of-coverage or in idle mode (NR mode 2-like)
`o
`aGSL-RNTIis generated by the group head and distributed to other group members
`(GMs). Hence, this can be a PN sequence number.
`
`G/
`
`
`
`o The (known) application layer group ID (e.g., as used in CAM and DENM messages)is
`used as a source for the generation of the, e.g., GSL-RNTI.
`
`95
`
`3.2 Scenario: Network/ tracking area change
`
`if the network and/or the tracking area changes, the GSL-RNTI may be updated by the current
`group head. The updating may be performed by the group head,the (resent) network controller or
`by a combination of both (e.g. by the head, while the network controller assists).
`
`100
`
`Embodiment Global group (member) ID
`A unique global group ID within one network uniquely identifies each group and group member within a
`network. It is composed of
`
`105
`
`110
`
`1. Cell/ zone/etc. ID: geographical reference of the group
`2. Group ID: unique ID of the group within the geographical area
`3. Group internal ID: unique identification of each GM within the group
`Within each group (same Group ID), each group member is identified by a group internal ID
`e
`For platoons(or any other group, where the position of the GM within the group is important), the
`group internal ID can represent the the sequenceof thevehicle in the platoon.This improvesthe fast
`and easy tracking of the vehicles within the platoon, e.g. first, middle, last position of the vehicle
`within the platoon.
`o Whenever the position of the vehicle within the platoon changes, the group internal ID is
`updated accordingly.
`- According to a further embodiment, the group member ID can be composedof:
`© The group ID and the member unique ID (C-RNTI, V-RNTI, V2X RNTI).
`o
`Ifthe network RNTI is not available (especially for out of coverage cases) the group
`memberID is composed of the group ID (e.g. selected from a PN-sequence generator)plus
`a unique identifier for each GM,e.g,., .
`«
`Example: one platoon groupcast (group ID x) with 3 group members (3 vehicles
`following each other) could have the following group member IDs:
`
`415
`
`120
`
`e
`
`e
`
`GH: group ID (XYZ) + group member internal ID (01) = XYZo1
`
`1°*GM: groupcast ID; x, group member internal ID (02) = XYZo2
`
`2°4 GM: groupcast ID; x, group member internal ID (03) = XYZo3
`e
`Note: The group memberinternal [Ds could represent the vehicle order in the platoon
`
`4125
`
`3.1.4 Workarounds
`
`No workaround currently known.
`
`3.2.2 Proof of Infringements
`
`be)
`
`
`
`If included in the TS, this invention has to be used to allow V2X groupcast to work in 5G NR.
`
`3.2 Technical Application Area (5)
`
`130
`
`V2X groupcastto allow efficient low-latency assignment and modificacation of the group ID andthe GM
`group internal ID.
`
`
`
`4
`
`Claims
`
`135
`
`A mobile device being a member of a communication group and configured to communicate with
`
`one or more other members of the communication group and to exchange control information with
`
`the one or more other members, wherein the mobile device is configured to create (complile) an
`
`identification information and to transmit (distribute) the identification information on a physical
`
`layer of the control
`
`information (on the physical
`
`layer in the control channel), wherein the
`
`140
`
`identification information assigns
`
`the communication group (enabling to identify the
`
`communication group and / or the individual member within the communication group. Note, the
`
`identification information may be adaptive to the application and scenario). (Claim 1 complies to
`
`variant 1 and covers the other variants).
`
`145
`
`The mobile device according to claim 1, wherein the mobile device is a group head of the
`
`communication group. (This claim refers to the embodimentof Fig. 1).
`
`The mobile device according to one of the previous claims, wherein the control information uses the
`
`SCI format; and / or
`
`150
`
`wherein the control information uses the SC! format and wherein the identification is inserted into
`
`one or more of reserved information bits. (This claim defines variant 1 in more detail).
`
`The mobile device according to one of the previous claims, wherein the identification information is
`
`455
`
`inserted into the control information by scrambling or multiplexing the control information with the
`
`identification information (e.g. SCI information with the group ID). (This claim refers to variant 2).
`
`The mobile device according to the one the previous claims, wherein the identification information
`is out of a group comprising a group destination ID, and a group source ID, and a group destination
`and group source ID in combination, and a common group ID; and/or
`
`160
`
`
`
`wherein the identification information is composed of a cell/zone/geographical reference of the
`
`group and/or a unique ID of the group within the geographical area. (This claim represents the
`
`possible definitions for the identification information).
`
`165
`
`The mobile device according to one of the previous claims, wherein radio /network temporary
`
`identification information is used as identification information; or
`
`wherein radio /network temporary identification information is used as identification information
`
`170
`
`and wherein the radio /network temporary identification information is dependent on a certain area
`
`or geographical reference; or
`
`wherein a side link identification information is used as identification information. (This claim is
`
`directed to variant 3).
`
`475
`
`The mobile device according to claim 6, wherein the mobile device is configured to define the radio
`
`/network temporary identification information or the side link identification information during a
`
`setup phase.
`
`180
`
`The mobile device according to claim 6 or 7, wherein the radio /network temporary identification
`
`information orside link identification information is generated by the mobile device as group head,
`
`if the communication group or at least a member of the communication group is out of coverage or
`
`in idle mode; and/or
`
`185
`
`wherein the radio /network temporary identification information or the side link identification
`
`information is generated based on an application group ID or a PN sequence number, (This claim
`
`refers to scenario 3.1).
`
`
`
`9.
`
`The mobile device according to one of claims 6 to 8, wherein the radio /network temporary
`
`190
`
`identification information or the side link communication information is updated, if the network
`
`and/or the tracking area changes. (This claim refers to scenario 3.2).
`
`10.
`
`The mobile device according to one of the previous claims, wherein the mobile device or each
`
`member is configured to generate an additional group member identification (e.g. according to the
`
`3195
`
`order of the platoon).
`
`a1.
`
`The mobile device according to claim 10, wherein the global group member identification is
`
`composed of a network reference, a cell/zone/geographical reference and/or a unique identification
`
`of the group within the geographical area and/or a unique identification of each group member
`
`200
`
`within the group.
`
`12.
`
`A method for identifying a communication group,
`
`the method being performed within a
`
`communication group within which a member communicates with one or more other members of
`
`the communication group and exchanges control information with one or more other members,
`
`205
`
`wherein the method comprises:
`
`creating an identification information and transmitting (distributing) the identification information
`ona physical layer of the control information (on the physical layer in the control channel) so as to
`
`assign the identification information to the communication group (enabling to identify the
`
`210
`
`communication group and / or the individual member within the communication group).
`
`13.
`
`A computer program for performing, when running on a computer the method according to claim
`12,
`
`245
`
`
`
`eke End of document ***
`
`4p
`
`

Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ ChargeStill Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.

This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.

One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site