Network entity and method for a wireless network system for determining time information
阅读说明：本技术 用于确定时间信息的无线网络系统的网络实体和方法 (Network entity and method for a wireless network system for determining time information ) 是由 曹瀚文 桑迪普·甘卡克黑卡尔 韦庆 于 2019-03-21 设计创作，主要内容包括：本发明提供了一种用于无线网络系统的网络实体。所述网络实体用于获取接收的报文的入口时间,所述入口时间指示所述报文进入所述网络系统的时间,基于所述入口时间确定关于所述报文的时间信息,并且将所述时间信息提供给另一网络实体。用于无线网络系统的另一网络实体用于获取关于从另一网络实体接收的报文的时间信息,并获取所述报文的出口时间,所述出口时间基于所述时间信息指示所述报文离开所述网络系统的时间。本发明还涉及用于使在网络实体处有效的内部时间与在外部网络实体处有效的外部时间同步的网络实体。(The invention provides a network entity for a wireless network system. The network entity is configured to obtain an entry time of a received packet, the entry time indicating a time when the packet enters the network system, determine time information about the packet based on the entry time, and provide the time information to another network entity. Another network entity for a wireless network system is configured to obtain time information about a packet received from another network entity, and obtain an egress time of the packet, the egress time indicating a time at which the packet leaves the network system based on the time information. The invention also relates to a network entity for synchronizing an internal time valid at the network entity with an external time valid at an external network entity.)
1. A network entity (100) for a wireless network system (1), the network entity (100) being configured to:
obtaining an entry time (t) of a received message (101)0) Said entry time (t)0) Indicating the time at which the message (101) enters the network system (1),
based on the entry time (t)0) Determining time information (102) about the message (101), an
Providing the time information (102) to another network entity (110).
2. The network entity (100) of claim 1, wherein:
the time information (102) comprises an entry time (t) of the message (101)0)。
3. The network entity (100) of claim 1, further configured to:
based on an entry time (t) of the message (101) in the network system (1)0) And a predetermined dwell time (T)R)，
Calculating an exit time (t) of the message (101)1) Said exit time (t)1) Indicating the time at which the message (101) leaves the network system (1),
wherein the time information (102) comprises the exit time (t)1)。
4. The network entity (100) of claim 3, further configured to:
-retrieving a synchronization message associated with the message (101),
according to said predetermined residence time (T)R) To modify the synchronization message, in particular to modify the correction field of the synchronization message, and
providing the modified synchronization message to the other network entity (110).
5. The network entity (100) of one of claims 1 to 3, configured to:
determining whether the message (101) belongs to a group of messages that periodically enter the network system (1),
if the message (101) belongs to such a group of messages, determining an interval, and
providing information indicating periodicity to the other network entity (110), wherein the information indicating periodicity is based on the interval.
6. The network entity (100) of one of claims 1 to 5, further configured to:
merging the time information (102) into a timestamp bit format, an
Truncating the timestamp bit format by removing at least one most significant bit and/or at least one least significant bit.
7. The network entity (100) of one of claims 1 to 6, further configured to:
providing the time information (102) to the other network entity (110) by at least one of:
-concatenating the time information (102) with the message (101),
-including the time information (102) in a payload of the message (101),
-including the time information (102) in a header of the message (101),
-generating a further message comprising the time information (102),
-transmitting said time information using a control message.
8. Network entity (110) for a wireless network system (1), the network entity (110) being configured to:
obtaining time information (102) about a message (101) received from another network entity (100), an
Obtaining an exit time (t) of the message (101) based on the time information (102)1) Said exit time (t)1) Indicating the time at which the message (101) leaves the network system (1).
9. The network entity (110) of claim 8, wherein:
the time information (102) comprises an entry time (t) of the message (101)0) The entry time (t)0) Indicating the entry of the message (101) into the networkTime of the network system (1), and
the network entity (110) is configured to base the entry time (t) on0) Determining the exit time (t)1)。
10. The network entity (110) of claim 9, further configured to:
entry time (t) based on the message (101)0) And exit time (t)1) Determining the residence time (T) of the message (101) in the network system (1)R)。
11. The network entity (110) of claim 9, configured to:
based on an entry time (t) of the message (101) in the network system (1)0) And a predetermined dwell time (T)R) To determine an exit time (t) of the message (101)1)。
12. The network entity (110) of claim 8, wherein:
the time information (102) comprises the exit time (t)1) And an
The network entity (110) is configured to extract the exit time (t) from the time information (102)1)。
13. The network entity (110) of claim 12, further configured to:
obtaining a predetermined residence time (T) of the message (101) in the network system (1)R)。
14. The network entity (110) of one of claims 10, 11 and 13, further configured to:
will include an indication of the residence time (T) of the message (101) in the network system (1)R) Is provided to an external network entity (502).
15. The network entity (110) of claim 14, configured to:
by depending on said dwell time (T)R) -modifying a synchronization message received from the other network entity (100), in particular modifying a correction field of the synchronization message, to generate the synchronization message.
16. The network entity (110) according to one of claims 8 to 15, further configured to:
buffering the message (101) until the egress time (t) is reached1) And an
At the exit time (t)1) Providing the message (101) to an external network entity (502).
17. The network entity (110) according to one of claims 8 to 16, further configured to:
obtaining information indicating a periodicity of a group of messages periodically entering the network system (1), to which the message (101) belongs, and
determining an exit time (t) of the message (101) based on the periodicity1)。
18. The network entity (100, 110) according to one of claims 1 to 17, further configured to:
synchronizing time with the other network entity (110, 100), wherein the other network entity (110, 100) is within the wireless network system (1).
19. A network entity (200) for a wireless network system (1), the network entity (200) being configured to:
internal time (t) validated at the network entity (200)s) With an external time (E) valid at an external network entity (201)k(ts) In a synchronous manner) are synchronized with each other,
providing time information (102) to another network entity (210), wherein the time information (102) comprisesThe internal time (t)s) To the external time (E)k(ts) ) of the data.
20. The network entity (200) of claim 19, wherein the time information (102) further comprises an indication of the external time (E)k(ts) A domain number of a clock domain of).
21. A network entity (210) for a network system (1), the network entity (210) being configured to:
obtaining time information (102) from another network entity (200), wherein the time information (102) comprises an internal time (t) at which the other network entity (200) is valids) And an external time (E) valid at the first external network entity (201)k(ts) A mapping of) and
based on a mapping in the time information (102), an internal time (t) valid at the network entity (210)s) With an external time (E) valid at a second external network entity (202)k(ts) ) synchronization.
22. A method (1800) performed by a network entity (100) for a wireless network system (1), the method (1800) comprising:
obtaining (1801) an entry time (t) of a received message (101)0) Said entry time (t)0) Indicating the time at which the message (101) enters the network system (1),
based on the entry time (t)0) Determining (1802) time information (102) about the message (101), an
Providing (1803) the time information (102) to another network entity (110).
23. A method (1900) performed by a network entity (110) for a wireless network system (1), the method (1900) comprising:
obtaining (1901) time information (102) about the received message (101) from another network entity (100), an
-obtaining (1902), based on the time information (102), an exit time (t) of the message (101)1) Said exit time (t)1) Indicating the time at which the message (101) leaves the network system (1).
24. A method (2000) performed by a network entity (200) for a wireless network system (1), the method (2000) comprising:
internal time (t) validated at the network entity (200)s) With an external time (E) valid at an external network entity (201)k(ts) -synchronizing (2001),
providing (2002) time information (102) to another network entity (210), wherein the time information (102) comprises the internal time ((t)s) To the external time (E)k(ts) ) of the data.
25. A method (2100) performed by a network entity (210) for a network system (1), the method (2100) comprising:
obtaining (2101) time information (102) from another network entity (200), wherein the time information (102) comprises an internal time (t) valid at the other network entity (200)s) With an external time (E) valid at a first external network entity (201)k(ts) A mapping of) and
based on a mapping in the time information (102), an internal time (t) valid at the network entity (210)s) With an external time (E) valid at a second external network entity (202)k(ts) Synchronization (2102).
26. A computer program product comprising program code for controlling a network entity according to one of claims 1 to 21 or for performing a method according to one of claims 22 to 25 when implemented on a processor.
Technical Field
The present invention relates generally to the field of wireless mobile communications, and more particularly to determining time information in a cellular communication system having external applications with precise timing requirements.
To this end, the invention proposes a network entity for determining time information and providing the time information to another network entity. The invention also proposes a network entity which synchronizes an internal time valid at the network entity with an external time valid at an external network entity. In addition, the invention provides a corresponding method.
Background
Accurate time reference synchronization within multiple clock domains and deterministic data transfer over 5G systems (5G systems, 5GS) are desirable for applications in different vertical industries, such as smart factories, programming and Special Events (PMSE), autopilot and its underlying V2X communications, etc.
FIG. 22 schematically illustrates the prior art provided operational clock domain interactions including "Merge" 2201 and "separate" 2202 in one smart plant scenario. In 3GPP S1-183329: CyberCAV-5G in Industrial Automation: the interaction between the working clock domains is schematically discussed in 2018, 11 months 12-16, a number of different time domains for synchronization, span, washington, city, bokan, usa.
In conventional mobile communication systems, synchronization is generally accomplished by simple broadcasting of time information, and there is no strict control over communication delay. As a result, the time synchronization bias and data transfer jitter become uncontrollable, which cannot meet the above-mentioned requirements from different vertical industries.
Disclosure of Invention
In view of the above problems and disadvantages, embodiments of the present invention are directed to improving conventional apparatuses and methods. It is therefore an object of embodiments of the present invention to provide a network entity for a wireless network system (e.g. in a core network) and a method performed by the network entity. In some embodiments of the invention, delay measurement and jitter control may be provided, for example, in a cellular communication system.
The solution provided in the appended independent claims achieves an object. Advantageous embodiments of the invention are further defined in the dependent claims.
Furthermore, it is another object of embodiments of the present invention to support multiple clock domains for a 5G system acting as a time-aware repeater and enable time-sensitive deterministic transmission with fixed delay/low jitter.
This can be achieved by End-to-End (E2E) synchronization within the 5 GS. For example, the two ends of the 5GS may be a User Plane Function (UPF) and a User Equipment (UE), or two UEs. Efficient transfer of ingress/egress timestamps may be used to measure dwell time (delay within 5GS) and/or to implement adaptive buffering until a fixed dwell time before egress is reached.
A first aspect of the present invention provides a network entity for a wireless network system, wherein the network entity is configured to obtain an entry time of a received packet, where the entry time indicates a time when the packet enters the network system; determining time information about the packet based on the entry time; and provide the time information to another network entity.
The network entity may be, for example, a network node, such as a User Equipment (UE) or a User Plane Function (UPF). The UPF may also be a network node, or it may be implemented as a function in a network node. The wireless network system may be a Long Term Evolution (LTE) network system, a fifth generation (5G) network system, or the like.
In some embodiments, the network entity may be in a core network, e.g., the radio network system may be a 5G network system, and the network entity may be a UPF in the core network of the 5G network system.
A network entity (e.g., UE or UPF) is configured to obtain an entry time of a received packet. The received message may be received from an entity or node in the external network. The network entity (e.g., UE or UPF) may also determine and provide the time information to another network entity, which may be, for example, another UE or another UPF (as located in the core network of the wireless network system).
In one implementation form of the first aspect, the time information includes an entry time of the packet.
In another implementation form of the first aspect, the network entity is further configured to calculate an egress time of the packet based on an ingress time of the packet in a network system and a predetermined residence time, the egress time indicating a time when the packet leaves the network system, wherein the time information includes the egress time.
In another implementation form of the first aspect, the network entity is further configured to obtain a synchronization message associated with the packet, modify the synchronization message, in particular, modify a correction field of the synchronization message, according to the predetermined residence time, and provide the modified synchronization message to the other network entity.
In another implementation form of the first aspect, the network entity is further configured to determine whether the packet belongs to a group of packets that periodically enter the network system, determine an interval such as a time interval if the packet belongs to the group of packets, and provide information indicating the periodicity to the other network entity, wherein the information indicating the periodicity is based on the interval.
In one embodiment, the time interval indicates a periodicity of the set of messages. Based on the knowledge of the time interval, the network entity may determine an egress time. As an example, the network entity determines an egress time for a packet in the set of packets based on the time interval and an egress time for a first packet in the set of packets. In particular, the network entity may add a time interval to the egress time of a message to obtain the egress time of the next message.
In another implementation form of the first aspect, the network entity is further configured to incorporate the time information into the timestamp bit format and truncate the timestamp bit format by removing at least one most significant bit and/or at least one least significant bit.
In another implementation form of the first aspect, the network entity is further configured to provide the time information to the other network entity by at least one of:
-concatenating the time information with the message;
-including the time information in a payload of the packet;
-including the time information in a header of the message;
-generating a further message comprising said time information;
-transmitting time information using the control message.
Furthermore, in some embodiments, a first portion of the time information (i.e., the time information after truncation) may be carried in the data plane and a second portion of the time information (i.e., the truncated portion of the time information) may be carried in the control plane.
A second aspect of the present invention provides a network entity for a wireless network system, wherein the network entity is configured to obtain time information about a packet received from another network entity; and acquiring the exit time of the message, wherein the exit time indicates the time for the message to leave the network system based on the time information.
The network entity (i.e. the network entity of the second aspect) may be, for example, a UE or a UPF. The network entity is configured to obtain time information about the received message from another network entity, which may be, for example, an entity within the network system, in particular an entity from another UE or UPF.
In one implementation form of the second aspect, the time information includes an entry time of the packet, the entry time indicating a time when the packet enters the network system, and the network entity is configured to determine the exit time based on the entry time.
In another implementation form of the second aspect, the network entity is further configured to determine a residence time of the packet in the network system based on an ingress time and an egress time of the packet.
In another implementation form of the second aspect, the network entity is further configured to determine an egress time of the packet based on an ingress time of the packet in the network system and a predetermined residence time.
In another implementation form of the second aspect, the time information includes an exit time, and the network entity is configured to extract the exit time from the time information.
In another implementation form of the second aspect, the network entity is further configured to obtain a predetermined residence time of the packet in the network system.
In another implementation form of the second aspect, the network entity is further configured to provide a synchronization message to an external network entity, where the synchronization message includes information indicating a residence time of the packet in the network system.
In another implementation form of the second aspect, the network entity is further configured to generate the synchronization message by modifying the synchronization message received from the other network entity according to the dwell time, in particular by modifying a correction field of the synchronization message.
In another implementation form of the second aspect, the network entity is further configured to buffer the message until an egress time is reached, and to provide the message to the external network entity at the egress time.
In another implementation form of the second aspect, the network entity is further configured to obtain information indicating a periodicity of a group of packets that periodically enter the network system, wherein the packets belong to the group of packets, and determine an egress time of the packets based on the periodicity.
In another implementation form of the second aspect, the network entity is further configured to synchronize time with the other network entity, wherein the other network entity is within the wireless network system.
For example, the network entity (e.g., UE or UPF) may synchronize time with an internal network entity. In some embodiments, no synchronization of the UE or UPF with external network entities is required.
A third aspect of the present invention provides a network entity for a wireless network system, wherein the network entity is configured to synchronize an internal time valid at the network entity with an external time valid at an external network entity, to provide time information to another network entity, wherein the time information comprises a mapping of the internal time to the external time.
The network entity (e.g. of the third aspect) may be a UE or a UPF. Furthermore, the time information may be provided to another network entity, which may be an entity in the network system, e.g. another UE or another UPF.
In an implementation form of the third aspect, the time information further comprises a domain number of a clock domain indicating the external time.
For example, the clock domains may include different operational clock domains and global clock domains.
A fourth aspect of the present invention provides a network entity for a network system, wherein the network entity is configured to obtain time information from another network entity, wherein the time information comprises a mapping of an internal time valid at the other network entity and an internal time valid at a first external network entity, and to synchronize the internal time valid at the network entity with an external time valid at a second external network entity based on the mapping in the time information.
The network entity (i.e. the network entity of the fourth aspect) may be a UE or a UPF. The network entity, e.g., a UE or a UPF, may obtain time information from another network entity, which may be another UE or another UPF.
A fifth aspect of the present invention provides a method performed by a network entity for a wireless network system, wherein the method comprises: acquiring entry time of a received message, wherein the entry time indicates the time for the message to enter the network system; determining time information about the packet based on the entry time; and providing the time information to another network entity.
In an implementation form of the fifth aspect, the time information includes an entry time of the packet.
In another implementation form of the fifth aspect, the method further includes calculating an egress time of the packet based on an ingress time of the packet in the network system and a predetermined residence time, the egress time indicating a time when the packet left the network system, wherein the time information includes the egress time.
In another implementation form of the fifth aspect, the method further comprises: acquiring a synchronous message associated with the message; modifying the synchronization message, in particular modifying a correction field of the synchronization message, in dependence of the predetermined dwell time; and providing the modified synchronization message to the other network entity.
In another implementation form of the fifth aspect, the method further comprises: determining whether the message belongs to a group of messages which periodically enter the network system; if the message belongs to the group of messages, determining a time interval; and providing information indicative of the periodicity to the other network entity, wherein the information indicative of the periodicity is based on the interval.
In one embodiment, the time interval indicates a periodicity of the set of messages. Based on the knowledge of the time interval, the network entity may determine an egress time. As an example, the network entity determines an egress time for a packet in the set of packets based on the time interval and an egress time for a first packet in the set of packets. In particular, the network entity may add a time interval to the egress time of a message to obtain the egress time of the next message.
In another implementation form of the fifth aspect, the method further comprises incorporating the time information into a timestamp bit format and truncating the timestamp bit format by removing at least one most significant bit and/or at least one least significant bit.
In another implementation form of the fifth aspect, the method further comprises providing the time information to the other network entity by at least one of:
-concatenating the time information with the message;
-including the time information in a payload of the packet;
-including the time information in a header of the message;
-generating a further message comprising said time information;
-transmitting said time information using a control message.
A sixth aspect of the present invention provides a method performed by a network entity (e.g., the network entity of the second aspect) for a wireless network system, wherein the method comprises: obtaining time information about the received message from another network entity; and acquiring the exit time of the message based on the time information, wherein the exit time indicates the time when the message leaves the network system.
In an implementation form of the sixth aspect, the time information includes an ingress time of the packet, the ingress time indicating a time when the packet entered the network system, and the method further includes determining the egress time based on the ingress time.
In another implementation form of the sixth aspect, the method further includes determining a residence time of the packet in the network system based on an ingress time and an egress time of the packet.
In another implementation form of the sixth aspect, the method further includes determining an egress time of the packet based on an ingress time of the packet in the network system and a predetermined residence time.
In another implementation form of the sixth aspect, the time information includes the exit time, and the method further includes extracting the exit time from the time information.
In another implementation form of the sixth aspect, the method further includes acquiring a predetermined residence time of the packet in the network system.
In another implementation form of the sixth aspect, the method further comprises providing a synchronization message to an external network entity, the synchronization message comprising information indicating a residence time of the packet in the network system.
In another implementation form of the sixth aspect, the method further comprises generating the synchronization message by modifying the synchronization message received from the other network entity in dependence of the dwell time, in particular modifying a correction field of the synchronization message.
In another implementation form of the sixth aspect, the method further comprises buffering the packet until the egress time is reached, and providing the packet to an external network entity at the egress time.
In another implementation form of the sixth aspect, the method further comprises: obtaining periodic information indicating a group of messages periodically entering the network system, wherein the messages belong to the group of messages; and determining an egress time of the packet based on the periodicity.
In another implementation form of the sixth aspect, the method further comprises synchronizing time with the other network entity, wherein the other network entity is within the wireless network system.
A seventh aspect of the present invention provides a method performed by a network entity for a wireless network system, wherein the method comprises: synchronizing an internal time valid at the network entity with an external time valid at an external network entity; providing time information to another network entity, wherein the time information comprises a mapping of the internal time to the external time.
In an implementation form of the seventh aspect, the time information further comprises a domain number of a clock domain indicating the external time.
An eighth aspect of the present invention provides a method performed by a network entity for a network system, wherein the method comprises obtaining time information from another network entity, wherein the time information comprises a mapping of an internal time valid at the other network entity and an external time valid at a first external network entity; and synchronizing an internal time valid at the network entity with an external time valid at a second external network entity based on a mapping in the time information.
A ninth aspect of the invention provides a computer program product comprising program code for controlling a network entity according to one of the first to fourth aspects or for performing a method according to one of the fifth to eighth aspects when implemented on a processor.
It has to be noted that all devices, elements, units and components described in the present application may be implemented in software or hardware elements or any kind of combination thereof. All steps performed by the various entities described in the present application and the functions described to be performed by the various entities are intended to indicate that the respective entities are adapted or arranged to perform the respective steps and functions. Although in the following description of specific embodiments specific functions or steps performed by an external entity are not reflected in the description of specific elements of the entity performing the specific steps or functions, it should be clear to a skilled person that these methods and functions may be implemented in respective hardware or software elements or any combination thereof.
Drawings
The foregoing aspects and many of the attendant aspects of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
fig. 1 is a diagram illustrating network entities of a wireless network system for determining time information according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a network entity of a wireless network system for synchronizing an internal time with an external time according to an embodiment of the present invention;
fig. 3 is an exemplary scheme diagram of timing in a wireless communication system;
FIG. 4 is an exemplary schema diagram of an architectural view;
FIG. 5 is a schematic diagram of a process for real-time measurement and correction of dwell time based on signaling of entry time;
FIG. 6 is a schematic diagram of a process for real-time measurement and correction of dwell time based on signaling a target exit time;
FIG. 7 is a schematic diagram of a process for adaptive buffering based on signaling an entry time;
FIG. 8 is a schematic diagram of a process for adaptive buffering based on signaling a target exit time;
FIG. 9 is a schematic diagram of a process for implementing a fixed residence time for a periodic or predictable traffic model based on signaling ingress timestamps;
FIG. 10 is a schematic diagram of a process for implementing a fixed residence time for a periodic or predictable traffic model based on signaling an egress timestamp;
FIG. 11 is a schematic diagram of a synchronization message format including a large amount of data in an IEEE 1588 timestamp;
FIG. 12 is a schematic diagram of truncation of timestamps to save overhead;
FIG. 13 is a schematic diagram of a signaling method for timestamps between an entry point and an exit point;
FIG. 14 is a schematic diagram of the use of reserved data fields to communicate ingress/egress timestamps;
FIG. 15 is a schematic diagram of the reference architecture in the 5 GS;
fig. 16 is an exemplary scheme for communicating static time assistance information using Control Plane (CP) signaling;
FIG. 17 is an exemplary scheme for boundary clock based transparent-less messaging synchronization propagation;
fig. 18 is a schematic diagram of a method for a network entity of a wireless network system according to the present invention;
fig. 19 is a schematic diagram of a method for a network entity of a wireless network system according to the present invention;
fig. 20 is a schematic diagram of a method for a network entity of a wireless network system according to the present invention;
fig. 21 is a schematic diagram of a method for a network entity of a wireless network system according to the present invention;
FIG. 22 is a schematic diagram of operational clock domain interaction "merging" and "splitting" according to the prior art.
Detailed Description
Fig. 1 is a schematic diagram of a network entity 100 of a wireless network system 1 for determining time information 102 according to an embodiment of the present invention.
The network entity 100 and/or the network entity 110 may be a UE or a UPF and the radio network system 1 may be a 5G network system. For example, the network entity 100 may be a UPF in the core network of a 5G network system, and the further network entity 110 may be a UE (or UPF) in the 5G network system.
The network entity 100 (e.g., UE or UPF) is configured to obtain an entry time t of the received packet 1010The entry time t0Indicating the time at which the message 101 entered the network system 1.
The network entity 100 is further configured to base the entry time t on0Time information 102 about the message 101 is determined and the time information 102 is provided to the further network entity 110.
Fig. 1 is a schematic diagram of a network entity 110 for a wireless network system 1, wherein the network entity 110 is configured to obtain time information 102 about a message 101 received from another network entity 100 based on the time information 102, and to obtain an exit time t of the message 1011Time of exit t1Indicating the time at which the message 101 left the network system 1.
For example, in some embodiments, a new type of UE or UPF may be provided, which may record the entry timestamp and may also signal the timestamp to another UE or another UPF at the other end. In this case, the time stamp is an example of the time information 102. It may also use the measured delay between the ingress and egress times to correct the correction field based on the specified egress time egress message, and so on.
Furthermore, the signaling of a timestamp for or generally time information between an entry point and an exit point may be based on, for example:
concatenating the ingress/egress timestamps directly with the original data packets to form a PDU message, which can be transmitted between the UE and the UPF within a PDU session.
Use reserved data field to transmit ingress/egress timestamp.
Optional fields using GTP header and PDCP header
Generating additional PDUs after the PDU carrying the PTP message
Using control messaging timestamps
And any combination of these options.
In some embodiments, measurements of E2E delay (dwell time) within the 5GS and corrections in the synchronization messages may be provided, for example:
a first network entity (ingress node) that receives incoming packets, measures and formats ingress time, and signals the formatted ingress time to a second network entity.
The first network entity may also signal a target exit time to the second network entity based on the measured entry time.
The format may be based on a predetermined maximum expected delay between the first network entity and the second network entity.
It is also possible to provide a monitoring function, for example, for periodically incoming messages, the interval between successive messages can be determined at a first time, and can then be signaled at a first time only if the interval deviates from the theory by a predetermined threshold.
In some embodiments, adaptive buffering may be provided until a fixed E2E delay (dwell time) within 5GS is reached, such as:
the second network entity (egress node) buffers packets received from the first network entity (ingress node) for a hold time equal to the time difference between the predetermined or signalled dwell time and the signalled ingress time from the first network entity.
For periodic or predictable data traffic models, special schemes for significantly reducing signaling overhead may also be provided.
In some embodiments, a format for representing timestamps may be provided in order to reduce overhead, e.g., it may be based on:
truncating the most significant digit directly according to the maximum dwell time requirement.
Truncate the least significant bits according to the precision requirement.
Receive accuracy requirements and/or dwell time from an entity (PCF) in the 5G core network.
FIG. 2 is a block diagram for timing internal times t according to various embodiments of the present inventionsAnd external time Ek(ts) A schematic illustration of a network entity 200 of a synchronized wireless network system.
The network entity 200 is arranged for validating the internal time t at the network entity 200sWith an external time E valid at the external network entity 201k(ts) And (6) synchronizing.
The network entity 200 is further configured to provide the time information 102 to another network entity 210, wherein the time information 102 comprises an internal time tsTo the external time Ek(ts) To (3) is performed.
Fig. 2 is also a schematic diagram of a network entity 210 for a network system 1, wherein the network entity 210 is configured to obtain time information 102 from another network entity 200, wherein the time information 102 comprises an internal time t valid at said other network entity 200sAnd an external time E valid at the first external network entity 201k(ts) And based on the mapping in the time information 102, an internal time t to be valid at the network entity 210sWith an external time E valid at the second external network entity 202k(ts) And (6) synchronizing.
Network entity 100 and network entity 200 may be the same network entity or may be based on the same type of network entity. For example, both network entities 100 and 200 may be UEs or UPFs. Similarly, network entity 110 and network entity 210 may be the same network entity or may be based on the same type of network entity. For example, both network entities 110 and 210 may be other UEs or other UPFs without limiting the disclosure to this particular configuration.
Furthermore, the time information 102 may comprise an internal time t valid at the further network entity 200sAnd at the first external network entity 201Effective external time Ek(ts) To (3) is performed. For example, the mapping may be to the internal time tsAnd external time Ek(t) comparing, wherein k is the number of clock domains; and measures the frequency offset delta between the internal time (i.e. the internal clock) and the external time (i.e. the external clock)k。
Fig. 3 is an exemplary scheme of timing in the wireless communication system 1, which may be performed by an embodiment of the present invention including the wireless communication system 1 described in fig. 1 and 2.
For example, the entry time of the user data is variable. Further, the Tx/Rx processing time period is implementation specific and may be variably implemented.
Further, the radio transmission time starts at the beginning of a particular slot or symbol (mini-slot). Thus, for example, the Tx hold time may be obtained by the network entity 100 by implementing a predetermined fixed delay and/or measuring a variable delay.
For example, to support multiple clock domains with time-aware delays, the exact residence time of a packet residing in the 5GS may be measured and added to the "correction field" of TSN Sync and Follow _ Up messages. The delay measured in real time can then be provided to the TSN's synchronization protocol to optimize its accuracy.
FIG. 4 is an exemplary schema diagram of an architectural view. As an example, the architecture diagram in fig. 4 illustrates a wireless network system 1, which is a 5G network system comprising one or more network entities. The network entity may be or may include network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210. Without limiting the present disclosure, the scheme of the architecture view is discussed below based on the UPF100 in the core network (i.e., the network entity 100) and the UE110 as the other network entity (the other network entity).
Furthermore, network entity 100 (and/or network entity 110 and/or network entity 200 and/or network entity 210) may also synchronize the internal time with an external time of external network entity 201 as the TSN of the 5G network system.
The architectural view contains the core network (illustratively shown as a logical bridge or link with 5GS) that performs internal E2E synchronization between UE110 and UPF100 and between UE110 and UE410 (via Uu or sidelink). Furthermore, with 5GS internal synchronization, delay measurements between any pair of N60 or between any pair of N6 interfaces can be achieved.
FIG. 5 is a schematic diagram of a process 500 for real-time measurement and correction of dwell time based on signaling of entry time; process 500 may be performed (e.g., in whole or in part) by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
In the following, part of the process 500 is exemplarily discussed as being performed by a network entity 100 (e.g., UE or UPF) located at an entry point and a network entity 110 (e.g., UE or UPF) located at an exit point of the wireless network system 1.
In process 500, a network entity 100 (e.g., a UE or UPF) acquires a synchronization message from an upstream node 501. The network entity 100 also obtains an entry time t0And will include t0To another network entity 110 (another UE or another UPF).
Furthermore, the further network entity 110 (the further UE or the further UPF) may determine the exit time t1The "correction field" is related to the dwell time TR＝t1-t0And (4) adding. Furthermore, the further network entity 110 may further wait until time t1Until time t, and at time t1Sends the synchronization message with the correction to the downstream node 502.
The process 500 for measuring and correcting the dwell time in real time based on signaling the entry time may be applied to variable delays in the 5 GS. Process 500 may be used in applications with limited delay requirements. Furthermore, the process 500 does not require a change to the 5G Quality of Service (QoS) framework.
FIG. 6 is a schematic diagram of a process 600 for real-time measurement and correction of dwell time based on signaling a target exit time; process 600 may be performed (e.g., in whole or in part) by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
In the following, part of the process 600 is exemplarily discussed as being performed by a network entity 100 (e.g. a UE or a UPF) located at an entry point and a network entity 110 (e.g. a UE or a UPF) located at an exit point of the wireless network system 1.
In process 600, a network entity 100 (e.g., a UE or UPF) acquires a synchronization message from an upstream node 501. The network entity 100 also obtains an entry time t0. Network entity 100 may also determine a target egress time t1And the 'correction field' is compared with the dwell time t1＝t0+TRAnd (4) adding. The network entity 100 may also send an include t to another network entity 110 (another UE or another UPF)1Signaling of (2).
Another network entity 110 may wait until time t1And at time t1The synchronization message with the correction is sent to the downstream node 502.
The process 600 for real-time measurement and correction of residence time based on signaling target exit time may be applied to fixed delays in 5 GS. The process 600 may be used in applications with fixed delay/bounded jitter requirements.
In some embodiments, adaptive buffering may be provided, for example, until a fixed dwell time is reached.
FIG. 7 is a schematic diagram of a process 700 for adaptive buffering based on signaling an entry time; process 700 may be performed (e.g., in whole or in part) by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
In the following, part of the process 700 is exemplarily discussed as being performed by a network entity 100 (e.g., a UE or a UPF) located at an entry point and a network entity 110 (e.g., a UE or a UPF) located at an exit point of the wireless network system 1.
Further, FIG. 8 is a schematic diagram of a process 800 for adaptive buffering based on signaling a target exit time; process 800 may be performed (e.g., in whole or in part) by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
In the following, part of the process 800 is exemplarily discussed as being performed by a network entity 100 (e.g., a UE or a UPF) located at an entry point and a network entity 110 (e.g., a UE or a UPF) located at an exit point of the wireless network system 1.
Adaptive buffering at the egress node may ensure that the exact residence time in the 5GS is maintained.
Further, the buffering time may be determined based on any of:
1) a predetermined dwell time and an ingress time of the signaled egress,
2) a predetermined dwell time and a target exit time for signaling egress.
Furthermore, adaptive buffering may rely on 5GS inter-synchronization in the user plane, e.g.:
1) the 5GS internal synchronization delay can be compensated by adjusting the dwell time or target exit time.
2) The estimated 5GS internal synchronization error may be signaled as a subsequent message from the entry point to the exit point.
In the process 700 of fig. 7, with traffic based on random arrival times signaling ingress times, the network entity 100 (e.g., a UE or UPF) acquires a data packet from the upstream node 501. The network entity 100 also obtains an entry time t0And will include t0To another network entity 110 (another UE or another UPF). Furthermore, another network entity 110 (another UE or another UPF) may determine the exit time t1＝t0+TRAnd wait until time t1. At the exit time t1Another network entity 110 may send a data packet to downstream node 502.
In the process 800 of fig. 8, a network entity 100 (e.g., a UE or UPF) acquires a data packet from an upstream node 501 with traffic based on a random arrival time that signals a target egress time. Network entity 100 obtains entry time t0And a target exit time t may be determined1＝t0+TR. Further, the network entity 100 sends an indication comprising t to another network entity 110 (another UE or another UPF)1Signaling of (2). Another network entity 110 (another UE110 or another UPF110) may wait until time t1. At the exit time t1The other network entity 110 sends the data packet to the downstream node 502.
In some embodiments, a fixed residence time may be achieved.
FIG. 9 is a schematic diagram of a process 900 for implementing a fixed residence time for a periodic or predictable traffic model based on a signaled ingress timestamp; process 900 may be performed (e.g., in whole or in part) by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
In the following, part of the process 900 is exemplarily discussed as being performed by a network entity 100 (e.g., a UE or a UPF) located at an entry point and a network entity 110 (e.g., a UE or a UPF) located at an exit point of the wireless network system 1.
In process 900, a fixed residence time of a periodic or predictable traffic model may be implemented based on signaling an ingress timestamp, for example, by:
for isochronous data traffic, which is very common in IA, the ingress time is periodic or has a predictable pattern.
Ingress/egress time becomes predictable and signaling of ingress/egress timestamp for each packet becomes unnecessary within the 5GS, for example according to:
o inlet: t is t0(n)＝t0(n-1)+Tintv.＝t0(0)+n·Tintv.
And o, outlet: t is t1(n)＝t1(n-1)+Tintv.＝t1(0)+n·Tintv.
Consider clock mismatches between 5GS and multiple external nodes.
o can continuously measure the message interval byAnd (4) showing.
o may timestamp t0(n) and interval of measurementThe exit point is signaled for correcting the exit time.
o due to the periodicity of the data traffic, timestamp t0(n) intervals of signalling and measurementsIs not attached to every packet but to multiple packets, which may save most of the signaling overhead.
Further, only the change in the measured interval may be signaled to the egress node.
Further, fig. 10 is a schematic diagram of a process 1000 for implementing a fixed residence time for a periodic or predictable traffic model based on signaling an egress timestamp. Process 1000 may be performed (e.g., in whole or in part) by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
In the following, part of the process 1000 is exemplarily discussed as being performed by a network entity 100 (e.g. a UE or a UPF) located at an entry point and a network entity 110 (e.g. a UE or a UPF) located at an exit point of the wireless network system 1.
For isochronous data traffic, which is very common in IA, the entry time is periodic or has a predictable pattern.
Ingress/egress time becomes predictable, and it is not necessary to signal ingress/egress timestamps for each packet, according to:
o inlet: t is t0(n)＝t0(n-1)+Tintv.＝t0(0)+n·Tintv.
And o, outlet: t is t1(n)＝t1(n-1)+Tintv.＝t1(0)+n·Tintv.
Consider the clock mismatch between 5GS and the external node.
o can continuously measure the message interval byAnd (4) showing.
o may timestamp t0(n) or t1(n) and interval of measurementThe exit point is signaled for correcting the exit time.
For periodic flows (3C/3D), a monitoring function at the egress node may be proposed to monitor for changes in the ingress time interval and therefore signal the changes to the egress node as corrective. This may further reduce signaling overhead.
In some embodiments, timestamp compression may be provided. Fig. 11 is a schematic diagram of a synchronization message format including a large amount of data in an IEEE 1588 timestamp. The compression may be performed by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
As shown in fig. 11, a large amount of data in an existing timestamp scheme may be compressed (e.g., by network entity 100), such as:
in the IEEE 1588 and 802.1AS protocols:10 octets, 80 bits.
Furthermore, since residence times are typically small (<10ms), timestamp data may be further truncated to save overhead, for example by:
truncating a set of most significant digits according to the maximum dwell time.
Truncate a set of least significant digits according to precision requirements.
Fig. 12 is a schematic diagram of truncation of timestamps to save overhead. The truncation of the timestamp may be performed by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entity in this regard. For example, assuming an original timestamp precision of 1ns of 10 octets (80 bits), a maximum dwell time of 16.8ms of precision of 128ns can be handled by truncating bits #0-6 and #24-79 (reserved bits #7- # 23). In addition, the PCF may specify the accuracy requirement for truncation of the most/least significant digits based on (1) the maximum dwell time (delay) and (2).
In some embodiments, a method of signaling a timestamp between an entry point and an exit point may be provided. Fig. 13 is a schematic diagram of a method of signaling a timestamp between an entry point (e.g., which may be performed by network entity 100 or network entity 200 at the entry point) and an exit point (e.g., which may be performed by network entity 110 or network entity 210 at the exit point).
The entry time and/or exit time and/or residence time may be signaled out between the entry point and the exit point in various ways, such as:
concatenating the ingress/egress timestamps directly with the original data packets to form a PDU message, which can be transmitted between the UE and the UPF within a PDU session.
Use reserved data field to transmit ingress/egress timestamp.
Optional fields using GTP header and PDCP header.
Additional PDUs are generated after the PDU carrying the PTP message.
Use control messaging timestamps.
Fig. 14 is a schematic diagram of transmitting ingress/egress timestamps using reserved data fields. In fig. 14, the reserved data field is used to convey an ingress timestamp (e.g., it may be performed by network entity 100 or network entity 200 at the ingress point) and an egress timestamp (e.g., it may be performed by network entity 110 or network entity 210 at the egress point). Furthermore, a reserved field of 32 bits in the PTP header is sufficient to accommodate timestamps with nanosecond precision and in the range of one hundred milliseconds.
In some embodiments, reference architecture and signaling within a 5G system may be provided. Fig. 15 is a schematic diagram of the reference architecture in 5 GS. In fig. 15, a wireless network system 1 which becomes a 5G network system is exemplarily discussed. Further, network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 may be a UE or a UPF in a 5G network system.
A reference architecture for configuring a network to achieve high precision time synchronization may be provided, e.g., based on:
1. the Point Coordination Function (PCF) is consistent with the Application Function (AF) in terms of dwell time and traffic templates (e.g., interval of time measurements, granularity, etc.).
PCF will request delivery to a service Session Management Function (SMF).
SMF configuration UPF (ingress/egress) does time dependent processing.
Retrieve timestamp.
Processing timestamps (compression, calculation, etc.).
Apply the computation results (e.g., buffer control, modify/add packets, report to SMF, etc.).
Further, a reference architecture for communicating time assistance information through the CP may also be provided, e.g., based on:
1. quasi-static time assistance information may be conveyed by the CP.
Truncating the most and least significant digits of the timestamp.
Periodic synchronization errors.
1. The process may be as follows:
the SMF may decide on static time assistance information with the help of ingress/egress UPFs following policies defined by the PCF (e.g., based on TSN QoS templates).
The SMF may communicate the relevant assistance information to the ingress UPF and egress UPF via N4.
1. Fig. 16 is an exemplary scheme for communicating static time assistance signaling using CP signaling. Process 1600 may be performed (e.g., in whole or in part) by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
2. In the following, parts of the process 1600 are exemplarily discussed as being performed by a network entity 100 (e.g., a UPF) located at an entry point of the wireless network system 1 and a network entity 110 (e.g., a UPF) located at an exit point of the wireless network system 1.
3. An example of using CP signaling to convey static time assistance information is as follows:
in step 1: PCF 1601 triggers SMF 1602 for PDU session setup or modification.
In step 2: the SMF 1602 obtains the TSN-related policy from the PCF 1601 (e.g., whether the session requires UP synchronization, accuracy of UP synchronization, etc.).
In step 3: the SMF 1602 selects a UPF based on a number of synchronization requirements from the PCF 1601 and the UPF's synchronization capabilities. In this step, the SMF may optionally decide on static time assistance information with the help of ingress/egress UPFs following PCF-defined policies (e.g., based on TSN QoS templates).
In steps 4 to 5: the SMF configures the ingress UPF100 or egress UPF110 with static time assistance information.
4. Note that steps 4 through 5 may be triggered by SMF 1602 using the N2 session modification procedure to update the static time assistance information whenever needed. Steps 4 through 5 may also be used by SMF 1602 to configure the UPF for time-dependent processing.
5. Fig. 17 is an exemplary scheme 1700 for boundary clock based transparent-less messaging synchronization propagation. Process 1700 may be performed (e.g., in whole or in part) by network entity 100 and/or network entity 110 and/or network entity 200 and/or network entity 210 without limiting the disclosure to the particular network entities in this regard.
6. In the following, parts of the process 1700 are exemplarily discussed as being performed by a network entity 200 (e.g., a UE or UPF) performing a slave function and a network entity 210 (e.g., a UE or UPF) performing a master function.
7. In some embodiments, the transmission of the timestamp within the 5GS may not be triggered by an external synchronization message, but autonomously by the slave function 100 within the 5 GS. In some embodiments, not only the internal timestamp tsAnd its corresponding external time Ek(ts) Domain number k and optional external to internal frequency offset ΔkCan be used forIn one or more messages ts,Ek(ts),ΔkK to the main function 110.
8. Fig. 18 shows a method 1800 for the network entity 100 of the wireless network system 1 according to an embodiment of the invention. As described above, method 1800 may be performed by device 100.
9. Method 1800 includes obtaining an entry time t for a received message 1010Step 1801, entry time t0Indicating the time at which the message 101 entered the network system 1.
10. Method 1800 also includes basing entry time t on0Step 1802 of determining time information 102 about the message 101.
11. The method 1800 further comprises a step 1803 of providing the time information 102 to the further network entity 110.
12. Fig. 19 shows a method 1900 for the network entity 110 of the wireless network system 1 according to an embodiment of the invention. As described above, method 1900 may be performed by device 110.
13. The method 1900 comprises a step 1901 of obtaining time information 102 about a received message 101 from another network entity 100.
14. Method 1900 further includes obtaining an exit time t of message 101 based on time information 1021Step 1902, exit time t1Indicating the time at which the message 101 left the network system 1.
15. Fig. 20 shows a method 2000 for a network entity of the wireless network system 1 of the present invention. As described above, method 2000 may be performed by device 200.
16. The method 2000 includes an internal time t to be active at the network entity 200sExternal time E valid with external network entity 201k(ts) Step 2001 of synchronization.
17. The method 2000 further comprises a step 2002 of providing the time information 102 to the further network entity 210, wherein the time information 102 comprises the internal time tsTo the external time Ek(ts) To (3) is performed.
18. Fig. 21 shows a method 2100 for a network entity of the wireless network system 1 according to an embodiment of the invention. As described above, method 2100 may be performed by device 210.
19. The method 2100 comprises a step 2101 of obtaining time information 102 from another network entity 200, wherein the time information 102 comprises an internal time t valid at said other network entity 200sAnd an external time E valid at the first external network entity 201k(ts) To (3) is performed.
20. The method 2100 further comprises a step 2102 of validating the internal time t at the network entity 210 based on the mapping in the time information 102sWith an external time E valid at the second external network entity 202k(ts) And (6) synchronizing.
21. For example, the mapping may be to the internal time tsAnd external time Ek(t) comparing, where k is the number of clock domains, and measuring the frequency offset Δ between the internal time (i.e., the internal clock) and the external time (i.e., the external clock)k。
22. The invention has been described in connection with various embodiments and implementations as examples. Other variations will be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure, and the independent claims. In the claims and in the description, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single element or other unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.