<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.github

I refer to your implementation of the structure in <a href="https://github.com/wmnsk/g

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Please refer to <a href="https://github.com/wmnsk/go-pfcp/blob/a5d43d8c8eb7f8d56612064

Encapsulate user-plane-ip-resource-information IE about go-pfcp HOT 8 CLOSED

wmnsk commented on May 26, 2024 1

Encapsulate user-plane-ip-resource-information IE

from go-pfcp.

Comments (8)

w910820618 commented on May 26, 2024 1

thank you!!!

from go-pfcp.

w910820618 commented on May 26, 2024

I refer to your implementation of the structure in f-seid --->

go-pfcp/ie/f-seid.go

Lines 40 to 46 in e45192e

 type FSEIDFields struct { 

 Flags uint8 

 SEID uint64 

 IPv4Address net.IP 

 IPv6Address net.IP 

 ChooseID []byte 

 }

.
Are Flags in the structure used to control Octets5?

go-pfcp/ie/f-seid.go

Lines 113 to 115 in e45192e

 func (f *FSEIDFields) SetIPv6Flag() { 

 f.Flags |= 0x01 

 }

go-pfcp/ie/f-seid.go

Lines 103 to 105 in e45192e

 func (f *FSEIDFields) SetIPv4Flag() { 

 f.Flags |= 0x02 

 }

Are these two methods used to assign values to Octet5?

from go-pfcp.

w910820618 commented on May 26, 2024

Take a look, is my understanding correct?How do you think TEIDRIFlags should be assigned?

from go-pfcp.

w910820618 commented on May 26, 2024

Octets "k to l", if present, shall contain a Network Instance value as encoded in octet "5 to n+4" of the Figure 8.2.4-1 in clause 8.2.4, identifying a Network Instance with which the IP address or TEID Range is associated.
Octet r, if present, shall contain a Source Interface value as encoded in octet 5 of the Figure 8.2.2-1 in clause 8.2.2, identifying the Source Interface with which the IP address or TEID Range is associated.

The meaning of the two sentences is to put the value encoded by Network Instance and Source Interface into user-plane-ip-resource-information?

from go-pfcp.

wmnsk commented on May 26, 2024

@w910820618
Did you solve it?

from go-pfcp.

w910820618 commented on May 26, 2024

@wmnsk I did not solve this problem

from go-pfcp.

wmnsk commented on May 26, 2024

Please refer to the implementation I've just pushed and find the answer by yourself, as there are too many things to explain.

The specification by 3GPP is sometimes(or often) not so kind to us. We need to supplement some parts with our consideration made as reasonable as possible.

from go-pfcp.

wmnsk commented on May 26, 2024

Closing, as it seems there's no questions.

from go-pfcp.

Recommend Projects