WO2021241259A1 - Système de communication, procédé de communication et programme - Google Patents

Système de communication, procédé de communication et programme Download PDF

Info

Publication number
WO2021241259A1
WO2021241259A1 PCT/JP2021/018330 JP2021018330W WO2021241259A1 WO 2021241259 A1 WO2021241259 A1 WO 2021241259A1 JP 2021018330 W JP2021018330 W JP 2021018330W WO 2021241259 A1 WO2021241259 A1 WO 2021241259A1
Authority
WO
WIPO (PCT)
Prior art keywords
media
packet
application server
transition
upf
Prior art date
Application number
PCT/JP2021/018330
Other languages
English (en)
Japanese (ja)
Inventor
靖明 山岸
和彦 高林
義行 小林
Original Assignee
ソニーグループ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ソニーグループ株式会社 filed Critical ソニーグループ株式会社
Publication of WO2021241259A1 publication Critical patent/WO2021241259A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node

Definitions

  • the present disclosure relates to a communication system, a communication method, and a program, and more particularly to a communication system, a communication method, and a program capable of optimally switching a packet transfer path.
  • 5G systems 5th generation mobile communication systems
  • AI Artificial Intelligence
  • edge data network technology low latency for images transferred at high speed from automobiles and the like. Attention is being paid to use cases such as performing image recognition processing of the above on an edge AI server and reflecting it in automatic driving control.
  • various capture devices that implement a stream uplink function via a network are implemented in an automatic driving system or the like. Then, the capture device may move at high speed and perform a handover across the coverage range of the base station (hereinafter, also referred to as a cell).
  • the base station hereinafter, also referred to as a cell.
  • the computing that is bound to the cell after the transition together with the transfer destination application due to the limitation of processing delay etc.
  • the server side is functionally moved and is different in terms of application instance.
  • seamless handover is an inevitable task because a problem in automatic operation control may occur if there is a lack in stream acquisition. Further, the coverage by the base station of the 5G system is limited to 100 meters or less. Therefore, to take full advantage of the 5G system platform's ability to minimize the delay between the client and the edge, the frequency of high-speed handovers for uplink sources and applications is likely to increase. However, in such cases, it is necessary to ensure the reliability of the seamless uplink.
  • the boundaries of media processing include the boundaries of baseband image frames and the boundaries of GOP of encoded streams.
  • 3GPP the 3rd Generation Partnership Project proposes a system architecture for a 5G system.
  • This disclosure has been made in view of such a situation, and is intended to enable optimal switching of packet forwarding routes.
  • the communication system of one aspect of the present disclosure is before the transition until the media boundary marker indicating the media boundary is detected when the transfer of the media packet is switched according to the server transition of the application server to which the stream is destination. It is provided with a transfer route control unit that continues to transfer the media packet to the application server and starts transferring the media packet to the application server after the transition when the media boundary marker is detected.
  • a communication method or program of one aspect of the present disclosure transitions when switching media packet forwarding with a server transition of a stream destination application server until a media boundary marker indicating the media boundary is detected.
  • the media packet is continuously transferred to the previous application server, and when the media boundary marker is detected, the transfer of the media packet to the application server after the transition is started.
  • the application server before the transition is detected until the media boundary marker indicating the media boundary is detected.
  • the transfer of the media packet to the application server after the transition is started.
  • FIG. 1 It is a block diagram which shows the structural example of the 1st Embodiment of the stream uplink system to which this technique is applied. It is a figure explaining that the discontinuity of stream media processing occurs. It is a figure explaining that the traffic is copied in order to avoid discontinuity of streaming media processing.
  • FIG. 1 is a block diagram showing a configuration example of a first embodiment of a communication system to which the present technology is applied.
  • a UE User Equipment
  • a cloud 12 composed of a plurality of servers to provide various services on the network.
  • the access network 13 includes a wired access network (AN) and a radio access network (RAN) in a 5G system.
  • the UE 14 executes an application client (AC: Application Client) 15 for conducting a media streaming session with the application server 24 at the edge of the cloud 12.
  • AC Application Client
  • AS-Orchestrator 21 and UPF (User Plane Function) 22 are mounted on the cloud 12, and a plurality of data networks (DN: Data Network) 23 are arranged on the edge of the cloud 12.
  • An application server (AS: Application Server) 24 for executing various applications is provided on each data network 23.
  • AS-Orchestrator 21 is a management processing unit that executes processing for managing the life cycle and execution environment of media applications.
  • the UPF 22 is composed of a plurality of routers, switches, and the like, and is a forwarding route control unit that controls a forwarding route for forwarding media packets transmitted from the application client 15 to the application server 24 via the access network 13. ..
  • the UPF 22 transfers the media packet to the application server 24-1 on the data network 23-1.
  • the server transition is performed as the UE 14 moves to the cell of the data network 23-2, the application server 24-2 is started on the data network 23-2, and the instance of the application server 24-1 is duplicated. Will be done.
  • the UPF 22 switches the transfer route so that the media packet transferred to the application server 24-1 on the data network 23-1 is transferred to the application server 24-2 on the data network 23-2.
  • server transitions of the application server 24 are required due to overload or failure in the edge or cloud environment. It is also expected to become. Even in such a case, the transfer route is switched by the UPF22.
  • the UPF 22 can be provided with a function of executing a transfer route control process in which packet switching for switching the transfer of media packets is performed at the media boundary.
  • FIG. 2 is a diagram illustrating that discontinuity in stream media processing occurs.
  • the server transition (instance replication) is performed at the timing when it is determined that the transition of the edge environment is necessary. ..
  • the server transition is performed at the timing indicated by the white arrow in FIG. 2, a route control command for changing the route from the next media packet to the new destination application server 24-2 is issued. Therefore, in the conventional route control function, the transfer route is transferred from the media packet next to the timing when it is determined that the transition of the edge environment is necessary to the application server 24-1 before the transition to the application server 24-2 after the transition. Switching is done.
  • any next packet at the time when the route switch function of the network is turned on is transferred to the application server 24-2 after the transition, it is transferred from the packet that is not the media processing boundary depending on the application. There is a possibility. Therefore, the packet sequence between the media processing boundaries before and after the time when the route switch function of the network is turned on cannot be handled correctly and is missing in the media processing, resulting in streaming media processing. There is a possibility of discontinuity.
  • the route control function is the same for both the application server 24-1 before the transition and the application server 24-2 after the transition even after the timing when the traffic (packet route) should be changed due to the transition of the application server 24. Executes the transfer route control process to copy and transfer the stream packet.
  • both the application server 24-1 before the transition and the application server 24-2 after the transition perform the same stream acquisition process. After that, the application server 24-1 before the transition continues the media processing until the media processing boundary is found, and the application server 24-2 after the transition waits until the media processing boundary is found and starts the media processing.
  • the application server 24-1 before the transition notifies the application server 24-2 after the transition of the packet position up to a certain media processing boundary that it has processed, and instructs the UPF 22 to stop copying the traffic.
  • the application server 24-2 after the transition enables processing from the next packet (media processing boundary) at the packet position notified from the application server 24-1 before the transition.
  • FIG. 4 is a flowchart illustrating a transfer route control process as described with reference to FIG.
  • uplink streaming is performed from the application client 15 on the UE 14 to the application server 24-1 before the transition via the access network 13.
  • the AS-Orchestrator 21 monitors the movement status of the UE 14, the traffic status of the network, and the operating status of the application server 24-1.
  • the AS-Orchestrator 21 is in the server environment bound to the cell after the transition that the UE 14 has handed over in step S12. Start the optimum application server 24-2 newly.
  • step S13 the AS-Orchestrator 21 copies the packet streamed from the application client 15 on the UE 14 to the application server 24-1 before the transition to the UPF22, and copies the packet streamed from the application server 24-1 after the transition. Instruct to transfer to 2.
  • step S14 the application server 24-1 before the transition analyzes the contents of the stream packet and checks the media boundary.
  • step S15 the application server 24-2 after the transition also checks the media boundary.
  • step S16 when the application server 24-1 before the transition finds the media boundary, in step S16, the application server 24-1 after the transition is notified to which media boundary it has processed. In response to this notification, the application server 24-2 after the transition starts the media processing following the media boundary. Thereby, it is possible to determine to what extent the application server 24-1 before the transition has performed the stream processing and from where the stream processing performed by the application server 24-2 after the transition is effective.
  • step S17 the application server 24-1 before the transition makes a traffic change request to UPF22 so as to stop copying the packet and stop the traffic to itself.
  • the 4G EPS Evolved Packet System
  • EPS Evolved Packet System
  • PDU Protocol Data Unit
  • Session Equivalent
  • FIG. 5 shows how the uplink session from the UE 14 is connected to the two data networks 23-1 and 23-2 via a plurality of Anchor UPF (User Plane Function).
  • the UPF that provides the N6 interface to the data network 23 is called the PDU Session Anchor, and the UPF function that separates the PDU packets transferred from the UE 14 to these PDU Session Anchors according to the filter rules is Uplink Classifier: UL-. Called CL.
  • the UPF 22 is composed of a plurality of UPFs.
  • the UPF having the UL-CL function will be described as the UPF (ULCL) 22U
  • the UPF that will be the PDU Session Anchor will be referred to as the UPF (PSA) 22P.
  • the conventional UL-CL function can specify the UPF (PSA) 22P of the transfer destination according to the value of the header of the packet.
  • the conventional UL-CL function can transfer up to a certain packet to UPF (PSA) 22P-1 and the subsequent packets to UPF (PSA) 22P-2 as described above. There wasn't.
  • the function of this UL-CL is expanded to the function of recognizing the media processing boundary of the stream inserted in the application layer and switching the UPF (PSA) 22P of the destination to be separated and transferred, and the API of UPF is extended. It can be mounted on UPF (ULCL) 22U. As a result, it becomes possible to make the network side route the packet in consideration of the media processing boundary, and it is possible to eliminate unnecessary copying of traffic.
  • the UPF (ULCL) 22U has a function of performing packet switching on the uplink streaming path of the PDU session. Then, the UPF (ULCL) 22U divides the stream before and after the next media boundary when the route change (switch, blanching, etc.) of the stream whose ordering is guaranteed is specified, and after the division point. Makes the stream packet forward to the specified routing destination.
  • an API will be added that allows the UPF (ULCL) 22U packet transfer control rule to be dynamically registered and turned on / off from the application client 15 side. That is, the application client 15 can control the UPF (ULCL) 22U via the SMF (Session Management Function).
  • the media in the application client 15 only when a packet switch conscious of the media boundary is required. Insert the boundary identification of the processing unit into the stream.
  • a switching rule based on the UPF (ULCL) 22U of the PDU Session is also registered, and the DPI (Deep Packet Inspection) in the UPF is made to function to guarantee media-aware switching.
  • the UPF (ULCL) 22U forwards the packet to the destination as it is until the next media boundary marker is detected, and after the media boundary marker is detected, it is thereafter.
  • a PFR Packet Forwarding Rule
  • a PFR Packet Forwarding Rule
  • the PDU Session of the 5G system represents a transport session between the application client 15 on the UE 14 and the application server 24 on the data network 23.
  • the PDU Session is an abstraction of the connection between the UE 14, the access network 13, the core network (CN), and the data network 23.
  • the PDU Session is terminated by the UPF (PSA) 22P which is the PDU Session Anchor when connecting to the data network 23.
  • PSA UPF
  • the IP address of the UE 14 is maintained even if it transitions to a different access network 13, and the PDU Session is maintained.
  • the UPF (ULCL) 22U defines a PFR (Packet Forwarding Rule) that recognizes the media boundary described later and changes the destination of the packet before the boundary and the packet after the boundary.
  • PFR Packet Forwarding Rule
  • the UPF (ULCL) 22U recognizes the media processing boundary and changes the destination as shown in the lower side of C in FIG.
  • UPF (ULCL) 22U and UPF (PSA) 22P-1 are deleted from the PDU Session as shown in D of FIG. 7 because only the connection with the application server 24-2 after the transition is made.
  • UPF22 is a virtual router / switch on the core network, the local data networks 23-1 and 23, respectively, where the UE 14 and the nearest servers connected to the access networks 13-1 and 13-2 reside. Make a connection with -2.
  • the UPF22 also connects to the Central DN on the cloud, which is connected from them via the backhaul.
  • FIG. 8 is a diagram showing details of the PDU Session corresponding to A in FIG. 7 and an example of the IP address described in the packet.
  • the PDU Session layer which is a layer above the GTP (GPRS (General Packet Radio Service) Tunneling Protocol) -U (User Plane) layer, before the transition from the application client 15 on the UE 14 to the edge.
  • the packet is forwarded to the application server 24-1.
  • the application client 15 on the UE 14 is specified by the IP address of the UE 14, and the application server 24-1 before the transition is the IP address of the application server 24-1 before the transition (Application-ID of the application server 24 described later). It is specified by the IP address determined from).
  • FIG. 9 is a diagram showing details of the PDU Session corresponding to B in FIG. 7 and an example of the IP address described in the packet.
  • a transition occurs at the edge environment boundary of the UE 14, and the UE 14 transitions to a new edge environment while maintaining its own IP address (PDU (upper layer) layer).
  • the source IP address of the GTP-U packet carrying each IP packet of the PDU Session layer is the IP address corresponding to RAN2-gNB (next generation Node B) corresponding to the transitioned destination UE 14.
  • the IP address of UPF (PSA) 22P-1 corresponding to the application server 24-1 before the transition remains as the destination.
  • FIG. 10 is a diagram showing details of the PDU Session corresponding to C in FIG. 7 and an example of the IP address described in the packet.
  • FIG. 11 is a diagram showing details of the PDU Session corresponding to D in FIG. 7 and an example of the IP address described in the packet.
  • FIG. 12 shows an example of the format of the media boundary marker.
  • the media boundary marker is inserted in the transport layer packet header that fits in the IP packet contained within the MTU size.
  • a media boundary marker using the Marker-Scheme-ID described in the RTP (Real Time Transport Protocol) header extension (LCT (Layered Coding Transport) header extension, etc.) that can be inserted arbitrarily by the application. can.
  • RTP Real Time Transport Protocol
  • LCT Lane Coding Transport
  • Marker-Scheme-ID is a frame marker bit or sample boundary identification of the existing standard RTP header, and indicates what type of boundary it is.
  • the Marker-Scheme-ID is used to indicate whether it is a frame boundary, a GOP boundary, a VR coding processing boundary, a processing unit of a rendering command set, and the like.
  • the session for which the media boundary marker is inserted can be specified by, for example, IP address and UDP port, and the definition is based on the presence or absence of the RTP (LCT) extended header type (Marker-Scheme-ID) in the SDP entry. show.
  • RTP RTP
  • Marker-Scheme-ID RTP extended header type
  • the user plane PDU Session established between the application server 24 on the edge data network 23E and the application client 15 implemented on the UE 14 via the access network 13 of the 5G system is a two-point chain. It is represented by.
  • the broken line shown in FIG. 13 represents the control flow.
  • 5G-NF (5G core network system function group) 16 includes AMF (Access and Mobility Management Function), SMF (Session Management Function), UDM (Unified Data Management), PCF (Policy Control Function), NEF. It is composed of (NetworkExposureFunction), AUSF (AuthenticationServerFunction), and NRF (NetworkRepositoryFunction).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UDM Unified Data Management
  • PCF Policy Control Function
  • NEF NetworkExposureFunction
  • AUSF AuthenticationServerFunction
  • NRF NetworkRepositoryFunction
  • step S21 the UE 14 transmits a PDU Session establishment request to the AMF of the 5G-NF16 on the N1 interface.
  • step S22 in 5G-NF16, PDU Session establishment processing is performed between the AMF and the subsequent network function.
  • step S23 in this PDU Session establishment process UPF selection and UPF parameter setting are performed between the SMF and UPF of the 5G-NF16.
  • step S24 the PDU Session is established by returning the PDU Session establishment response from the AMF of the 5G-NF16 to the UE 14.
  • step S31 the application client 15 and the application server 24 perform an Application-Session establishment process for establishing an Application-Session by exchanging Session Properties on the PDU-Session.
  • step S32 in this Application-Session establishment process, Session Properties (Session attributes such as SDP (Session Description Protocol)) are exchanged.
  • Session Properties Session attributes such as SDP (Session Description Protocol)
  • Session Properties stores SDP, which is information that specifies the protocol, format, etc. used in the uplink streaming session from the application client 15 to the application server 24.
  • step S41 the application client 15 on the UE 14 makes a PDU Session establishment request to the 5G-NF16.
  • the PDU Session establishment process is performed as described with reference to FIG. 14 described above.
  • step S42 the 5G-NF16 makes a PDU Session establishment response to the application client 15 on the UE 14.
  • step S43 the application client 15 on the UE 14 notifies the application server 24-1 of Session Properties (SDP, etc.) and makes an Application-Session establishment request.
  • the application server 24-1 performs the Application-Session establishment process with the application client 15 as described with reference to FIG. 15 described above.
  • step S44 the application server 24-1 notifies the 5G-NF16 of the Session Properties (SDP, etc.) determined in the Application-Session establishment process.
  • step S45 the application server 24-1 makes a PDU Session establishment response to the application client 15 on the UE 14.
  • step S46 the application client 15 on the UE 14 starts inserting the media boundary marker.
  • urn x-lct-hdrext: ⁇ Marker-Scheme-ID>.
  • Maker-Scheme-ID that can support the markers defined in the existing standard, for example, the case where the frame boundary is indicated by the M bit in the RTP header defined in RFC-4175. To be able to support.
  • Marker-Scheme-ID is "VideoFrameBaundary" when the media boundary of the video baseband stream is the frame, "GOP" when the media boundary of the video encode stream is GOP, and so on.
  • the application can freely define the types of media boundaries, and multiple SDPs can describe the types of these media boundaries.
  • the application server 24 can change the handling method based on this media boundary type.
  • the RTP extension header is Identifier: 16 bits, 0xBEDE (indicates the RTP extension method defined in RFC 5285, A General Mechanism for RTP Header Extensions) length: 16 bits, the length of the header extensions part that stores each extension header (in 32-bit units) Is said to be.
  • each extension header starts from 1 byte and starts from 1 byte.
  • id 4 bits
  • value "1" fixed len 4 bits
  • number of bytes of the extension header-1 Is said to be.
  • this RTP extension header is stored in the IP packet that stores RTP, and then is stored in the IP packet that stores GTP-U.
  • FIG. 21 is a flowchart illustrating a transfer route control process to which the present technology is applied.
  • step S51 the application client 15 on the UE 14 starts inserting the media boundary marker into the uplink stream.
  • step S52 the AS-Orchestrator 21 monitors the movement status of the UE 14 through an API such as the Location Server of the UE 14 provided through the 5G-NF16. At the same time, the AS-Orchestrator 21 monitors the operating status of the pre-transition application server 24-1 on the pre-transition data network 23-1 that has established a session with the application client 15 on the UE 14.
  • an API such as the Location Server of the UE 14 provided through the 5G-NF16.
  • the AS-Orchestrator 21 monitors the operating status of the pre-transition application server 24-1 on the pre-transition data network 23-1 that has established a session with the application client 15 on the UE 14.
  • the AS-Orchestrator 21 is placed on the data network 23-2 after the transition in step S53. Start the application server 24-2 after the transition.
  • step S54 the AS-Orchestrator 21 determines the timing of the server transition.
  • the AS-Orchestrator 21 sets the UPF (ULCL) 22U in the network through the SMF of the 5G-NF16 together with the PFR in the step S55, and makes a traffic change request to the network in the step S56.
  • the AS-Orchestrator 21 determines the timing of changing the application server 24 (server transition) and network. (Step S56), and UPF (ULCL) 22U with PFR is set (step S55).
  • the AS-Orchestrator 21 if the AS-Orchestrator 21 is started after the transition of the application server 24-2 to the application server 24-2 after the transition of the UE 14, the AS-Orchestrator 21 immediately requests the network to change the traffic. (Step S56), UPF (ULCL) 22U with PFR is set (step S55).
  • step S57 the UPF (ULCL) 22U starts DPI, waits until it detects the media boundary marker, and transfers the actual traffic from the packet that detected the media boundary marker to the application server 24-2 after the transition. Perform the traffic change processing to be changed.
  • UPF (ULCL) 22U forwarding rule setting can be used for the 5G-CN route control setting API.
  • UPF (UL CL) is set by PFR (Packet Forwarding Rule) that executes a media-aware stream switch.
  • the media application of the UE 14 assumes that the ordering of the packet sequences constituting the stream is guaranteed (packet division in the MTU size range and restrictions on reordering), and the media of the stream is on the layer above the transport. Insert a marker to detect the boundary.
  • the packet until the next media boundary marker is detected is the destination as it is.
  • the rule is that packets after the packet containing the next media boundary marker are forwarded to the change destination.
  • the current destination is UPF (PSA) 22P-1 corresponding to the application server 24-1 before the transition
  • the change destination is the UPF (PSA) corresponding to the application server 24-2 after the transition. It is 22P-2.
  • FIG. 22 shows the parameters used for the IP Filter that can be set in the UPF in the current specifications (3GPP-TS23.501).
  • the forwarding PSA is defined for the packet having a specific value of the parameter shown in FIG. 22, and as described above, the packet is forwarded to a certain PSA until a certain marker appears, and after the marker appears, it is forwarded to a certain PSA.
  • the procedural forwarding rule with the state of changing the destination PSA and stopping the DPI itself at the same time is not considered.
  • FIG. 23 is a flowchart illustrating the traffic change process performed in step S57 of FIG. 21 described above.
  • step S61 enable UPF (ULCL) 22U. At this time, packet inspection is also enabled.
  • step S62 UPF (ULCL) 22U analyzes the SDP expressing the existence of the media processing boundary marker.
  • step S63 UPF (ULCL) 22U performs packet inspection.
  • step S64 UPF (ULCL) 22U determines whether or not there is a media processing boundary marker as a result of performing packet inspection in step S63.
  • step S64 If the UPF (ULCL) 22U determines in step S64 that there is no media processing boundary marker, the process proceeds to step S65.
  • step S65 the UPF (ULCL) 22U transfers the packet to the UPF (PSA) 22P-1 corresponding to the application server 24-1 before the transition, and then the process returns to step S63, and the same process is performed thereafter. Is repeated.
  • step S64 if the UPF (ULCL) 22U determines in step S64 that there is a media processing boundary marker, the process proceeds to step S66.
  • step S66 the UPF (ULCL) 22U transfers the packet to the UPF (PSA) 22P-2 corresponding to the application server 24-2 after the transition.
  • step S67 UPF (PSA) 22P-1 and UPF (ULCL) 22U are released, and the process is terminated.
  • FIG. 24 is a block diagram showing a configuration example of the UPF 22.
  • the UPF 22 includes a PDR Lookup processing unit 31, a switch 32, a setting holding unit 33, and a FAR processing unit 34.
  • the PDR Lookup processing unit 31 searches the setting holding unit 33 for the PDR (Packet Detection Rule) set and activated by the API for UPF22. Then, the PDR Lookup processing unit 31 filters the packet and supplies it to the switch 32 based on the filter rule defined in the PDI (Packet Detection Information) described in the PDR.
  • PDR Packet Detection Rule
  • the FAR processing unit 34 switches the switch 32 so that the packet is transferred to the target UPF (PSA) 22P according to the FAR (Forward Action Rule).
  • the filtering parameters in the UPF 22 are stored in the address of the UE 14 of the uplink stream source, the Application-ID assigned to the application server 24, and the packet of the transport layer of the (Inner) IP layer or higher.
  • This extended SDF-Filter stores an extended SDP that expresses the existence of a packet in which the above-mentioned media processing marker is inserted.
  • the PDR Lookup processing unit 31 analyzes the contents of the corresponding transport layer packet header. Then, the FAR processing unit 34 starts checking for the presence or absence of the media processing boundary marker, executes FAR to transfer to the application server 24-1 before the current transition until the marker is detected, and always transitions when the marker is detected. Execute FAR to transfer to the later application server 24-2.
  • the UPF 22 recognizes the boundary of the media and enables switching of the application server 24 which is the transfer destination of the packet, and the continuity of the media processing is guaranteed. Further, in the communication system 11, it is possible to eliminate the useless copying of traffic as described above, so that it is possible to avoid an excessive load on the network side.
  • the packet group of the media processing unit targeted in the above-described embodiment targets one uplink stream from the application client 15 on one UE 14.
  • one image is created by a plurality of cameras, and a stream from each camera is transmitted independently and stitched by an application server 24 on a 5G system. ..
  • the frames of the stream from each camera should be stitched together for those captured at the same time, that is, for a group of frames spanning multiple streams with the same frame time. It is assumed that the clocks of the cameras that generate such related frames are time-synchronized by some method (for example, NTP, PTP, side links between cameras, etc.).
  • the related frame group is received by the application server 24 as an independent PDU session from each camera via the UPF22 consisting of multi-stage switches / routers in the route.
  • the application server 24 performs reception buffering and waits until the packets of the related frame group are once prepared before being passed to the stitcher processing.
  • the processing of the multi-stage switch / router on the route may cause variations in the forwarding of the packet sequence.
  • this variation for example, it is conceivable to draw a special leased line from each camera to the application server 24, but since the leased line is expensive, a solution that can be substituted by a general public network is required.
  • the UPF (ULCL) 22U is composed of a plurality of stages of route control units 22S / R composed of switches / routers, and in the example shown in FIG. 25, N-stage route control units 22S / R-1 to 22S / R. -Consists of N. Then, the edge environment transition is performed from the application server 24-1 to the application server 24-2 due to the overload of the edge environment, the handover of the UEs 14-1 and 14-2, and the like. In this case, the temporal arrangement of the packet groups constituting the related frames, which were aligned at the time of stream transmission from the UEs 14-1 and 14-2, causes the N-stage route control units 22S / R-1 to 22S / RN. The variation may increase as you go through.
  • packet blocks having the same packet number (for example, # 1, # 2, # 3) connected by a broken line must be originally processed (Stitching) together. That is, a packet block (for example, # 2-1 and # 2-2) output from the UE 14-1 and transferred in the upper PDU session, and a packet output from the UE 14-2 and transferred in the lower PDU session. Blocks (eg, # 2-1 and # 2-2) need to be processed by the same application server 24.
  • packet blocks with the same packet number may be generated. It may reach a different application server 24.
  • media boundary detection occurs in the packet block of packet number (# 1), and the last packet of the packet block of packet number (# 1) is sent to the application server 24-1 before the transition. Transferred. Then, the packet at the beginning of the packet block of the packet number (# 2) is transferred to the application server 24-2 after the transition.
  • media boundary detection occurs in the packet block of packet number (# 2), and the last packet of the packet block of packet number (# 2) is transferred to the application server 24-1 before the transition. Will be done. Then, the packet at the beginning of the packet block of the packet number (# 3) is transferred to the application server 24-2 after the transition.
  • the packet block of the packet number (# 2) that should be processed together is distributed to the application server 24-1 before the transition and the application server 24-2 after the transition. Therefore, the packet block of the packet number (# 2) cannot be processed because it cannot be received by the same application server 24, and a group of packets missing in the media processing will occur.
  • the packet processing rules of the current 5G system have an essential restriction that the rules applied across multiple PDU sessions cannot be applied, so it is not possible to avoid the occurrence of missing packets in media processing. It was difficult.
  • the packet groups of a plurality of PDU sessions in the User Plane are associated with each other "in time” and arranged on the transfer path, and the route control units 22S / R-1 to 22S / R constituting the UPF (ULCL) 22U are arranged. -Allow synchronization and transfer between N.
  • FIG. 26 is a block diagram showing a configuration example of a second embodiment of a communication system to which the present technology is applied.
  • the UPF (ULCL) 22U can synchronize the grouped PDU Sessions at the time of output of the route control units 22S / R-1 to 22S / RN composed of switches / routers. ..
  • Each route control unit 22S / R constituting the UPF (ULCL) 22U includes a synchronization buffer 51 for synchronously outputting the grouped PDU session group.
  • the UPF (PSA) 22P also includes a similar synchronization buffer 52.
  • a packet processing rule that can be shared among new PDU sessions that specify grouping of PDU sessions and synchronously transfer a plurality of PDU session groups belonging to the group is introduced. Then, the group definition of the PDU session shall be notified by the extended SDP, and the PFR (Packet Forwarding Rule) for storing the extended SDP is set in the UPF (ULCL) 22U via the SMF of the 5G-NF16.
  • PFR Packet Forwarding Rule
  • UEs 14-1 to 14-3 send packets to their respective PDU sessions with time stamps according to wall clocks 53-1 to 53-3, respectively.
  • each route control unit 22S / R can group a plurality of PDU session groups and handle the reference time stamp of one of the streams as a source.
  • the reference time stamp of the stream output from the UE 14-2 is treated as a source.
  • the UPF rule setting is expanded so that buffering, jitter absorption, phase or period adjustment, and the like are performed for other streams at the time of output of each route control unit 22S / R.
  • the AS-Orchestrator 21 instructs each route control unit 22S / R to synchronize a plurality of PDU sessions with respect to the PDU session group connected to the source having the same reference clock.
  • the individual routing units 22S / R apply de-jittering of PDU session packets belonging to the PDU session group and phase or period adjustment.
  • extended SDP can be used to specify the grouping of multiple PDU sessions including packets of related frames.
  • a line as shown in the first line in bold in FIG. 28 is added to the SDP.
  • a line as shown in the second line in bold in FIG. 28 is added to the SDP of the PDU session to be transferred in time synchronization with other PDU sessions having related frames.
  • Add an attribute line that starts with a extmap.
  • urn: x-rtp-hdrext: ⁇ Session-Group-ID> identifier indicating the session group to be inserted in the RTP header extension part)
  • LCT packets for transport define as urn: x-lct-hdrext: ⁇ Session-Group-ID>.
  • ⁇ Session-Group-ID> is, for example, "ReferenceTimeSharedSessionGroup" indicating that a plurality of PDU sessions having related frame groups are grouped.
  • the RTP extension header is identifier: 16-bit, 0xBEDE (indicates the RTP extension scheme defined in RFC 5285, A General Mechanism for RTP Header Extensions) length: 16 bits, the length of the header extensions part that stores each extension header (in 32-bit units) Is said to be.
  • each extension header starts from 1 byte. id: 4 bits, fixed value "2" len: 4 bits, number of bytes of the extension header-1 Is said to be.
  • the UE 14 is provided with a wall clock 53 and a pre-transfer buffer 54.
  • the wall clock 53 has appropriate accuracy, such as via a network between the UE 14 and an access point (base station, etc.) or via a 5G side link between the UEs 14 (a network that does not pass through a base station between UEs 14). Then, the time is set based on the reference wall clock.
  • the reference wall clock is a highly accurate clock that can be synchronized with a clock source provided by a GPS system or the like at a base station or the like.
  • the wall clock 53 can synchronize its own system clock with this reference clock via a PTP (Precision Time Protocol (IEEE 1588-2008) or the like) network.
  • PTP Precision Time Protocol
  • each UE 14 the image is captured in one frame cycle (for example, 20 msec), and at the same time, the frame time (t1 or t2, etc.) is determined based on the wall clock 53.
  • These frame data and frame time are divided into RTP (LCT packet in another example) packets in the local pre-transfer buffer 54 of the UE 14 in consideration of the MTU (Maximum Transmission Unit) size of the network to be transferred. Stored.
  • RTP LCT packet in another example
  • Each packet is time-stamped when it is sent from the transport protocol stack of UE 14 to the network, and is stored in the Time stamp of the RTP header.
  • the time stamps are t1.1, t1.2, t1.3, t2.1, t2.2, t2.3, etc. as shown in the figure, and t1.1 to 3 and t2.1 to 3 are. , Each is evenly spaced.
  • the frame time (t1, t2, etc.) is stored in the PTP Sync Timestamp of Annex.
  • RTP mapping of the identity and timing information for example, when using the stack configuration specified by AMWA's MIMO.
  • the time interval of t1.1 to t1.3 and the time interval of t2.1 to t2.3 are not always the same, and the interval is adjusted according to the degree of network traffic congestion. For example, depending on how busy the traffic is, the time interval of each packet may be long (bit rate: large), or the time interval of each packet may be short (bit rate: small).
  • This adjustment is made by taking into consideration the traffic congestion / delay by the receiver report sent from the receiving application such as RTCP.
  • the same RTCP message is sent to the UE 14 group having the related frame.
  • these related UE14 groups exchange messages about when to transfer via the side link between UE14, and based on the wall clock, time stamps are set at the same intervals. It shall be granted and sent.
  • the intervals of t1.1 to t1.3 of UE14-1 and the intervals of t1.1 to t1.3 of UE14-2 are the same, and the intervals of t2.1 to t2.3 of UE14-1 are the same.
  • Time stamps are added so that the respective intervals of UE14-2 and the respective intervals of t2.1 to t2.3 of UE14-2 are the same.
  • the packet group of the stream group having the related frame is UE14 as much as possible on the time axis based on the time of this transport time stamp. It is arranged and adjusted so that the timing when it is sent from is maintained.
  • FIG. 31 is a diagram illustrating packet variation adjustment inside the route control unit 22S / R.
  • the packets of the two related streams are input to the route control unit 22S / R, they are input in a scattered manner. Then, the interval between the packet groups of the stream that arrived earlier than the two streams is slightly buffered in the synchronization buffer 51 according to the arrival condition of the packet group of the stream that arrived later. Then, the transmission start timing (t11 in the example of FIG. 31) is determined on the clock 55 of the route control unit 22S / R, and the variation is adjusted and output according to the time interval of the transport time stamp of the RTP from that timing. do.
  • the reference time stamp described later is a packet time interval starting from the timing on the clock 55 of the route control unit 22S / R.
  • the reference time stamp of a stream (representing Ref-PDU-Session described below) in multiple streams with this related frame group is shared or referenced among multiple streams with related frame groups. It shall be.
  • a PFR Packet Forwarding Rule for storing the above-mentioned extended SDP is set via the SMF of the 5G-NF16.
  • FIG. 32 is a block diagram showing a configuration example of UPF 22 having a function of performing synchronization processing based on a shared reference time stamp.
  • the same reference numerals are given to the configurations common to the UPF 22 in FIG. 24.
  • the UPF 22 is common to the UPF 22 in FIG. 24 in that it includes a PDR Lookup processing unit 31, a switch 32, and a setting holding unit 33. Further, the UPF 22 is configured to include a synchronization buffer 51 and a BAR processing unit 35.
  • the PDR Lookup processing unit 31 searches the setting holding unit 33 for the PDR (Packet Detection Rule) set and activated by the API for UPF22. Then, the PDR Lookup processing unit 31 filters the packet and supplies it to the synchronization buffer 51 based on the filter rule defined in the PDI (Packet Detection Information) described in the PDR.
  • PDR Packet Detection Rule
  • the BAR processing unit 35 processes the packets buffered in the synchronization buffer 51 according to the BAR (BufferingActionRule). That is, the BAR processing unit 35 arranges the related packet group of another PDU session having the related frame group on the transfer time axis so that the transport time stamps are close to each other, and then supplies the packet from the synchronization buffer 51 to the switch 32. Let me.
  • the FAR processing unit 34 switches the switch 32 so that the packet is transferred to the target UPF (PSA) 22P according to the FAR (Forward Action Rule).
  • the filtering parameters in the UPF 22 are stored in the address of the UE 14 of the uplink stream source, the Application-ID assigned to the application server 24, and the packet of the transport layer of the (Inner) IP layer or higher.
  • This extended SDF-Filter stores an extended SDP that expresses the existence of a packet into which the above-mentioned media processing marker is inserted and specifies a group of other PDU sessions having related frames.
  • the PDR Lookup processing unit 31 analyzes the contents of the corresponding transport layer packet header.
  • the BAR processing unit 35 is arranged on the transfer time axis so that it is output from the UPF at substantially the same time as the packets of other PDU sessions having the related frame group according to the value of the transport time stamp.
  • the FAR processing unit 34 starts checking for the presence or absence of the media processing boundary marker, executes FAR to transfer to the application server 24-1 before the current transition until the marker is detected, and always transitions when the marker is detected. Execute FAR to transfer to the later application server 24-2.
  • FIG. 33 is a flowchart illustrating a communication process for synchronous communication in a plurality of PDU sessions.
  • step S101 the SMF and UPF (PSA) 22P-1 corresponding to the application client 15-1 establish a PDU session of the application client 15-1 and the application server 24.
  • step S102 the SMF and UPF (PSA) 22P-2 corresponding to the application client 15-2 establish a PDU session for the application client 15-2 and the application server 24.
  • step S103 the SMF and UPF (PSA) 22P-3 corresponding to the application client 15-3 establish a PDU session for the application client 15-3 and the application server 24.
  • steps S101 to S103 a plurality of streams having related frames that must be collectively (synchronized) processed by the application server 24 are transferred from the application clients 15-1 to 15-3 to the application server 24, respectively. PDU session is established for.
  • step S104 the AS-Orchestrator 21 sets a PFR (Packet Forwarding Rule) instructing each of UPF (PSA) 22P-1 to 22P-3, which is a group of PDU sessions, to move in cooperation with each other.
  • PFR Packet Forwarding Rule
  • step S105 the application client 15-1 sends source streaming to UPF (PSA) 22P-1.
  • step S106 application client 15-2 sends source streaming to UPF (PSA) 22P-2
  • step S107 application client 15-3 sends source streaming to UPF (PSA) 22P-3. Send.
  • step S108 the UPFs (PSA) 22P-1 to 22P-3 for which PFR is set in step S104 determine the reference PDU session in cooperation with each other. Then, as described above, UPF (PSA) 22P-1 to 22P-3 perform synchronous output of each PDU session in synchronization with the time stamp of the reference PDU session, and send those packets on the transfer time axis. Deploy.
  • FIG. 34 shows an example in which a part of a plurality of application clients 15 hands over the access network 13 and performs uplink streaming to an application server 24 in an edge environment bound to a different access network 13. There is.
  • the application client 15-3 is handed over from the access network 13-1 to the access network 13-2, and then the application client 15-2 is transferred from the access network 13-1 to the access network 13-. Handover to 2. Finally, the application client 15-1 hands over from the access network 13-1 to the access network 13-2, and all of the application clients 15-1 to 15-3 move to the access network 13-2. ing.
  • the route control unit 22S / R-1 of the access network 13-1 before the transition and the access network 13-2 after the transition It is possible to synchronize the grouped PDU Session by referring to the time stamp of the related packet across the route control unit 22S / R-2 of the above.
  • FIG. 35 is a flowchart illustrating a process of handing over the access network 13. The description will be given with reference to FIG. 36.
  • both application clients 15-1 and 15-2 PDU to UPF (PSA) 22P-1 in the vicinity of application server 24-1 via access network 13-1. Session is in the established state. Then, in step S111, the application client 15-1 is streamed to the UPF (PSA) 22P-1 in which the application client 15-1 and the PDU Session are established. Similarly, in step S112, the application client 15-2 streams out to the UPF (PSA) 22P-1 in which the application client 15-2 and the PDU Session are established.
  • step S113 of FIG. 35 the AS-Orchestrator 21 attaches the UPF with the above-mentioned G (Group) PFR to the UPF (PSA) 22P-1 in which the application clients 15-1 and 15-2 and the PDU Session are established. Make settings.
  • step S114 the UPF (PSA) 22P-1 in which the PDU Session is established with each of the application clients 15-1 and 15-2 synchronizes with the Ref-PDU-Session and sends the PDU-Session to the application server 24-1. Synchronous output of.
  • step S115 the AS-Orchestrator 21 monitors the movement status of the UE 14-2 and the operating status of the application server 24-1.
  • the AS-Orchestrator 21 predicts the event when one of the application clients 15-1 and 15-2 hands over to the new access network 13. For example, the AS-Orchestrator 21 is in the server environment bound to the transitioned cell that the UE 14 has handed over in step S116 when the application server 24-1 needs to transition to the physical server environment. Start a new application server 24-2 of the optimum.
  • the AS-Orchestrator 21 determines the server transition timing in step S117, and in step S118, the PDU session of the application client 15-2 passing through the access network 13-2 after the transition with the above-mentioned G (Group) PFR.
  • UPF (ULCL) 22U-2 and UPF (PSA) 22P-2 are newly set in. That is, as shown in B of FIG. 36, UPF (ULCL) 22U-2 and UPF (PSA) 22P-2 in which the application client 15-2 and the PDU Session are established are set. It is streamed from ULCL) 22U-2 to UPF (PSA) 22P-1.
  • step S119 of FIG. 35 the application client 15-1 continuously performs streaming transmission to the UPF (PSA) 22P-1 in which the application client 15-1 and the PDU Session are established.
  • step S120 the application client 15-2 continuously transmits streaming to the UPF (PSA) 22P-1 via the UPF (ULCL) 22U-2 set in step S118.
  • step S121 the UPF (PSA) 22P-1 in which the PDU Session is established with each of the application clients 15-1 and 15-2 synchronizes with the Ref-PDU-Session and sends the PDU-Session to the application server 24-1. Synchronous output of.
  • step S122 the AS-Orchestrator 21 monitors the movement status of the UE 14-1 and the operating status of the application server 24-1.
  • the AS-Orchestrator 21 determines the server transition timing in step S123, and in step S124, the PDU session of the application client 15-1 passing through the access network 13-2 after the transition with the above-mentioned G (Group) PFR.
  • UPF (ULCL) 22U-1 and UPF (PSA) 22P-2 are newly set in. That is, as shown in C of FIG. 36, UPF (ULCL) 22U-1 and UPF (PSA) 22P-2 in which the application client 15-1 and the PDU Session are established are set. It is streamed from ULCL) 22U-1 to UPF (PSA) 22P-1.
  • step S125 the application client 15-1 continuously transmits streaming to the UPF (PSA) 22P-1 via the UPF (ULCL) 22U-1 set in step S124.
  • step S126 the application client 15-2 continuously streams to the UPF (PSA) 22P-1 via the UPF (ULCL) 22U-2 in which the application client 15-2 and the PDU Session are established. Send out.
  • step S127 the UPF (PSA) 22P-1 in which the PDU Session is established with each of the application clients 15-1 and 15-2 synchronizes with the Ref-PDU-Session and sends the PDU-Session to the application server 24-1. Synchronous output of.
  • step S1208 AS-Orchestrator 21 makes a traffic change request to UPF (ULCL) 22U-1 and 22U-2. After that, when the media boundary is detected and the traffic is changed, the AS-Orchestrator 21 releases UPF (ULCL) 22U-1 and 22U-2, and UPF (PSA) 22P-1. As a result, as shown in D of FIG. 36, both the application clients 15-1 and 15-2 are only UPF (PSA) 22P-2 in the vicinity of the application server 24-2 via the access network 13-2. And PDU Session are established.
  • step S129 the application client 15-1 streams out to the UPF (PSA) 22P-2 in which the application client 15-1 and the PDU Session are established.
  • step S130 the application client 15-2 streams out to the UPF (PSA) 22P-2 in which the application client 15-2 and the PDU Session are established.
  • step S131 the UPF (PSA) 22P-2 in which the PDU Session is established with each of the application clients 15-1 and 15-2 synchronizes with the Ref-PDU-Session and sends the PDU-Session to the application server 24-2. Synchronous output of.
  • the application client 15-1 streams and sends to the UPF (PSA) 22P-1 via the access network 13-1.
  • the application client 15-2 streams to the UPF (PSA) 22P-1 via the access network 13-1. This state corresponds to the processing of steps S111 to S114 of FIG.
  • the packet group of the related frame of the stream from the application client 15-1 and the stream from the application client 15-2 passing through the access network 13-2 after the transition is one of the Refs. -Synchronized with PDU-Session and transferred to the application server 24-1 before the transition.
  • This state corresponds to the processing of steps S117 to S121 in FIG.
  • the UPF (PSA) 22P-1 in the access network 13-1 before the transition and the UPF (ULCL) 22U-2 in the access network 13-2 after the transition cooperate with each other to synchronize the packet group of the related frame. And output.
  • the AS-Orchestrator 21 predicts the event. Then, the AS-Orchestrator 21 determines the server transition timing, and with the same G (Group) PFR, a new UPF (ULCL) 22U- is added to the PDU session of the application client 15-1 passing through the access network 13-1 before the transition. Set to 1. This state corresponds to the processing of steps S123 to S127 of FIG.
  • both the stream from the application client 15-1 passing through the access network 13-1 before the transition and the stream from the application client 15-2 passing through the access network 13-2 after the transition are packet groups of related frames. Is synchronized with either Ref-PDU-Session and transferred to the application server 24-1 before the transition.
  • the AS-Orchestrator 21 applies the traffic change of the destination change from the application server 24-1 to the application server 24-2 to these UPF (ULCL) 22U-1 and 22U-2 at an appropriate timing.
  • both the streams of application clients 15-1 and 15-2 are synchronized with either Ref-PDU-Session and transferred to the application server 24-2 after the transition. Will be done.
  • This state corresponds to the process of steps S129 to 131 of FIG.
  • the transition of the application server 24 when the transition of the application server 24 occurs, it can be delivered to the application server 24 after the transition without being missed in units of packets related to the application before and after the transition. Furthermore, the total amount of receiving applications (the amount that must be temporarily secured) is small, and the variation can be adjusted for each of the multi-stage route control units 22S / R consisting of switches / routers. The total amount of can be reduced.
  • FIG. 37 is a block diagram showing a configuration example of an embodiment of a computer in which a program for executing the above-mentioned series of processes is installed.
  • the program can be recorded in advance on the hard disk 105 or ROM 103 as a recording medium built in the computer.
  • the program can be stored (recorded) in the removable recording medium 111 driven by the drive 109.
  • a removable recording medium 111 can be provided as so-called package software.
  • examples of the removable recording medium 111 include a flexible disc, a CD-ROM (Compact Disc Read Only Memory), an MO (Magneto Optical) disc, a DVD (Digital Versatile Disc), a magnetic disc, and a semiconductor memory.
  • the program can be downloaded to the computer via a communication network or a broadcasting network and installed on the built-in hard disk 105. That is, for example, the program transfers wirelessly from a download site to a computer via an artificial satellite for digital satellite broadcasting, or transfers to a computer by wire via a network such as LAN (Local Area Network) or the Internet. be able to.
  • LAN Local Area Network
  • the computer has a built-in CPU (Central Processing Unit) 102, and the input / output interface 110 is connected to the CPU 102 via the bus 101.
  • CPU Central Processing Unit
  • the CPU 102 executes a program stored in the ROM (Read Only Memory) 103 accordingly. .. Alternatively, the CPU 102 loads the program stored in the hard disk 105 into the RAM (Random Access Memory) 104 and executes it.
  • ROM Read Only Memory
  • the CPU 102 performs the processing according to the above-mentioned flowchart or the processing performed according to the above-mentioned block diagram configuration. Then, the CPU 102 outputs the processing result from the output unit 106, transmits it from the communication unit 108, and further records it on the hard disk 105, for example, via the input / output interface 110, if necessary.
  • the input unit 107 is composed of a keyboard, a mouse, a microphone, and the like. Further, the output unit 106 is composed of an LCD (Liquid Crystal Display), a speaker, or the like.
  • LCD Liquid Crystal Display
  • the processes performed by the computer according to the program do not necessarily have to be performed in chronological order in the order described as the flowchart. That is, the processing performed by the computer according to the program includes processing executed in parallel or individually (for example, processing by parallel processing or processing by an object).
  • the program may be processed by one computer (processor) or may be distributed processed by a plurality of computers. Further, the program may be transferred to a distant computer and executed.
  • the system means a set of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all the components are in the same housing. Therefore, a plurality of devices housed in separate housings and connected via a network, and a device in which a plurality of modules are housed in one housing are both systems. ..
  • the configuration described as one device (or processing unit) may be divided and configured as a plurality of devices (or processing units).
  • the configurations described above as a plurality of devices (or processing units) may be collectively configured as one device (or processing unit).
  • a part of the configuration of one device (or processing unit) may be included in the configuration of another device (or other processing unit). ..
  • this technology can have a cloud computing configuration in which one function is shared by a plurality of devices via a network and processed jointly.
  • the above-mentioned program can be executed in any device.
  • the device may have necessary functions (functional blocks, etc.) so that necessary information can be obtained.
  • each step described in the above flowchart can be executed by one device or can be shared and executed by a plurality of devices.
  • the plurality of processes included in the one step can be executed by one device or shared by a plurality of devices.
  • a plurality of processes included in one step can be executed as processes of a plurality of steps.
  • the processes described as a plurality of steps can be collectively executed as one step.
  • the processes of the steps for describing the program may be executed in chronological order in the order described in the present specification, or may be called in parallel or called. It may be executed individually at the required timing such as when. That is, as long as there is no contradiction, the processes of each step may be executed in an order different from the above-mentioned order. Further, the processing of the step for describing this program may be executed in parallel with the processing of another program, or may be executed in combination with the processing of another program.
  • the present technology can also have the following configurations.
  • (1) When switching the forwarding of media packets with the server transition of the application server that is the destination of the stream, the media packets are forwarded to the application server before the transition until the media boundary marker indicating the media boundary is detected. Subsequently, a communication system including a transfer route control unit that starts transferring the media packet to the application server after the transition when the media boundary marker is detected. (2) Further equipped with an application client that transmits the media packet to the transfer route control unit via the access network.
  • the communication system according to (1) above wherein the application client inserts the media boundary marker into the stream when the transfer route control unit needs to switch the transfer of the media packet.
  • the transfer route control unit is A PDR Lookup processing unit that filters the media packets based on the filter rules defined in the PDI (Packet Detection Information) described in the PDR (Packet Detection Rule).
  • the communication system according to any one of (1) to (5) above, which has a FAR processing unit that switches a forwarding destination of the media packet according to a FAR (Forward Action Rule).
  • the transfer route control unit is It has a synchronization buffer for synchronously outputting grouped PDU (Protocol Data Unit) sessions.
  • the communication system according to any one of (1) to (6) above, which refers to a time stamp of the media packet across a plurality of PDU sessions.
  • the transfer route control unit has a BAR processing unit that is arranged on the transfer time axis so that the transport time stamps of the related packet groups of other PDU sessions having the related frame group are close to each other in accordance with the BAR (Buffering Action Rule).
  • the communication system according to (7) above.
  • the communication system When switching the forwarding of media packets with the server transition of the application server that is the destination of the stream, the media packets are forwarded to the application server before the transition until the media boundary marker indicating the media boundary is detected. Subsequently, a communication method including starting the transfer of the media packet to the application server after the transition when the media boundary marker is detected.
  • 11 information system 12 cloud, 13 access network, 14 UE, 15 application client, 16 5G-NF, 21 AS-Orchestrator, 22 UPF, 22U UPF (ULCL) 22P UPF (PSA) 23 data network, 24 application server, 31 PDR Lookup processing unit, 32 switch, 33 setting holding unit, 34 FAR processing unit

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un système de communication, un procédé de communication et un programme qui permettent de réaliser de manière optimale une commutation de trajets de transmission de paquets. Une unité de commande de trajet de transmission, lors de la commutation de la transmission d'un paquet multimédia en réponse à une transition de serveur d'un serveur d'application (AS) qui est une destination de flux, continue à transmettre le paquet multimédia au serveur d'application avant la transition jusqu'à ce qu'un marqueur de limite multimédia indiquant une limite multimédia soit détecté, et commence à transmettre le paquet multimédia au serveur d'application après la transition une fois que le marqueur de limite multimédia est détecté. La présente invention peut être appliquée, par exemple, à un système de communication qui effectue une diffusion en continu par l'intermédiaire d'un réseau.
PCT/JP2021/018330 2020-05-27 2021-05-14 Système de communication, procédé de communication et programme WO2021241259A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020-091922 2020-05-27
JP2020091922 2020-05-27

Publications (1)

Publication Number Publication Date
WO2021241259A1 true WO2021241259A1 (fr) 2021-12-02

Family

ID=78744036

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/018330 WO2021241259A1 (fr) 2020-05-27 2021-05-14 Système de communication, procédé de communication et programme

Country Status (1)

Country Link
WO (1) WO2021241259A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005516483A (ja) * 2002-01-23 2005-06-02 ヒューレット・パッカード・カンパニー データセッションハンドオフ方法
US20120069751A1 (en) * 2010-09-09 2012-03-22 Chung-Ang University Industry-Academy Cooperation Foundation Mobile terminal and handover method of the mobile terminal
JP2014502829A (ja) * 2011-01-10 2014-02-03 アルカテル−ルーセント 無線アクセス技術間ハンドオーバー中のデータ・パス切替えの方法
CN110149166A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 传输控制方法、装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005516483A (ja) * 2002-01-23 2005-06-02 ヒューレット・パッカード・カンパニー データセッションハンドオフ方法
US20120069751A1 (en) * 2010-09-09 2012-03-22 Chung-Ang University Industry-Academy Cooperation Foundation Mobile terminal and handover method of the mobile terminal
JP2014502829A (ja) * 2011-01-10 2014-02-03 アルカテル−ルーセント 無線アクセス技術間ハンドオーバー中のデータ・パス切替えの方法
CN110149166A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 传输控制方法、装置和系统

Similar Documents

Publication Publication Date Title
US9198089B2 (en) Caching architecture for streaming data between base stations in mobile networks
JP4668990B2 (ja) 単一ベアラサービスを介したマルチキャストサービス／ブロードキャストサービスのための適応型かつスケーラブルなＱｏＳアーキテクチャ
JP2022163174A (ja) 複数のサイト間のデータ分割
US7430609B2 (en) Managing access to streams hosted on duplicating switches
TWI458295B (zh) 行動無線裝置中調適傳輸以提昇服務品質（ＱｏＳ）的技術
US8812673B2 (en) Content rate control for streaming media servers
JP6110443B2 (ja) 協調セッション中に移動局のメディアフローを同期化する方法および装置
US20090144424A1 (en) Network bandwidth detection and distribution
US20050207443A1 (en) Transmission apparatus and method, reception apparatus and method, communication system, recording medium, and program
CA2445869C (fr) Gestion de l'acces a des flots de donnees heberges dans des commutateurs de duplication
JP2013505612A (ja) モバイルネットワークにおけるキャッシング
WO2014127515A1 (fr) Système de fourniture de service, procédé, serveur d'application côté mobile et nœud de prise en charge
CN101069374A (zh) 网络连接设备
JP2021525015A (ja) セッション処理方法、装置及びコンピュータ記憶媒体
KR20090007439A (ko) 지터 버퍼를 이용하여 음성패킷망 패킷들을 통신하고 처리하기 위한 방법 및 시스템
KR20210094081A (ko) 미디어 스트림 발신 방법과 장치 및 디바이스
EP3202105B1 (fr) Gestion de communication transmise en continu
WO2006086691A2 (fr) Client de mandataire de reseau, systeme de communication et procede de fourniture de service entre un serveur et un client final
US20170289225A1 (en) Optimizing media bitrate with explicit network feedback on one client only
US8027305B1 (en) Communication network and method employing state information in providing communication services to a mobile device
US12063271B2 (en) Migration of remote data processing between servers
WO2021241259A1 (fr) Système de communication, procédé de communication et programme
WO2023213281A1 (fr) Procédé de transmission redondante multi-trajet, équipement utilisateur, entité de réseau et support de stockage
WO2014005525A1 (fr) Procédé et système pour réserver une porteuse de ressources
JP2023033600A (ja) コンテンツ配信システム、ユニキャストマルチキャスト変換装置、コンテンツ配信方法及びコンテンツ配信プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21813754

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21813754

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP