WO2020259234A1 - 媒体服务在区域间的切换方法、服务器、系统及存储介质 - Google Patents

媒体服务在区域间的切换方法、服务器、系统及存储介质 Download PDF

Info

Publication number
WO2020259234A1
WO2020259234A1 PCT/CN2020/094069 CN2020094069W WO2020259234A1 WO 2020259234 A1 WO2020259234 A1 WO 2020259234A1 CN 2020094069 W CN2020094069 W CN 2020094069W WO 2020259234 A1 WO2020259234 A1 WO 2020259234A1
Authority
WO
WIPO (PCT)
Prior art keywords
mec
cdn node
cdn
user equipment
node
Prior art date
Application number
PCT/CN2020/094069
Other languages
English (en)
French (fr)
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 中兴通讯股份有限公司
Priority to EP20833614.9A priority Critical patent/EP3979671A4/en
Priority to KR1020227000596A priority patent/KR20220018034A/ko
Priority to US17/623,295 priority patent/US20220368730A1/en
Publication of WO2020259234A1 publication Critical patent/WO2020259234A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1021—Server selection for load balancing based on client or server locations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/21—Server components or server architectures
    • H04N21/222—Secondary servers, e.g. proxy server, cable television Head-end
    • H04N21/2225—Local VOD servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
    • H04N21/23106—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion involving caching operations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H04N21/25808—Management of client data
    • H04N21/25841—Management of client data involving the geographical location of the client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/414—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
    • H04N21/41407—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61—Network physical structure; Signal processing
    • H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
    • H04N21/6131—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via a mobile phone network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
    • H04N21/64707—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless for transferring content from a first network to a second network, e.g. between IP and wireless
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/025—Services making use of location information using location based information parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
    • 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
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems

Definitions

  • the present disclosure relates to but is not limited to the field of communication technology.
  • CDN Content Delivery Network
  • IPTV Internet Protocol Television
  • IPTV Internet Protocol Television
  • CDN Internet Protocol Television
  • IPTV Internet Protocol Television
  • the core idea of CDN is to push content to the nearest user
  • the use of CDN for media transmission can greatly improve the corresponding speed of users for obtaining media content, and also greatly reduce the bandwidth pressure of media content transmission on the backbone network.
  • various Internet services have entered a stage of rapid development, and the quality requirements for audio and video are constantly improving.
  • 4K, 8K, multi-view, and virtual reality (VR) video may all be online
  • the Internet is constantly launching various new services, many of which require CDN for accelerated services; therefore, CDN networks have gradually become an infrastructure for operators.
  • the edge nodes of CDN are generally deployed in places with higher network levels, such as the edge of the core network, which is required for traditional web pages and standard-definition multimedia content.
  • the response is applicable.
  • emerging services such as 4K, 8K, VR, Internet of Things, and Internet of Vehicles have extremely high requirements for the response between terminals and servers.
  • QoS Quality of Service
  • Guarantee requirements At this time, the service capabilities of traditional CDN edge nodes cannot meet the above-mentioned new service requirements.
  • An aspect of the embodiments of the present disclosure provides a method for switching media services between regions, including: a first MEC (Mobile-Edge Computing)-CDN node obtains mobile information of a user equipment from a core network; wherein, the user The device establishes a connection with the first MEC-CDN node, and obtains media services from the first MEC-CDN node; in response to determining that the user equipment pre-moves out of the coverage of the first MEC-CDN node according to the movement information, the first MEC-CDN node Determine the second MEC-CDN node and/or the second MEC platform to which the second MEC-CDN node is attached, and establish a connection with the second MEC-CDN node; the first MEC-CDN node migrates the state information of the user equipment to the second On the MEC-CDN node; and, in response to determining that the user equipment enters the coverage area of the second MEC-CDN node, the second MEC-CDN node
  • a first MEC-CDN server including a first processor, a first memory, and a first communication bus, where the first communication bus is configured to implement the first processor and the first communication bus.
  • a connection and communication between memories; and, the first processor is configured to execute one or more first programs stored in the first memory, so as to implement the method for switching media services between regions as described above.
  • a second MEC-CDN server including a second processor, a second memory, and a second communication bus.
  • the second communication bus is configured to implement the second processor and the second communication bus. Connection and communication between the two memories; and, the second processor is configured to execute one or more second programs stored in the second memory, so as to realize the reason for the method for switching media services between regions as described above At least one step implemented by the second MEC-CDN node.
  • a CDN system including a first MEC-CDN server, a second MEC-CDN server, a core network, and user equipment; wherein: the first MEC-CDN server includes the first MEC-CDN Node and the first MEC platform to which the first MEC-CDN node is attached; the second MEC-CDN server includes the second MEC-CDN node and the second MEC platform to which the second MEC-CDN node is attached; the first MEC-CDN server and the second MEC platform 2.
  • the MEC-CDN server has an intercommunication channel; the first MEC-CDN server obtains the mobile information of the user equipment from the core network; wherein the user equipment establishes a connection with the first MEC-CDN server and obtains media from the first MEC-CDN server Service; In response to determining that the user equipment is pre-moved out of the coverage of the first MEC-CDN server according to the mobile information, the first MEC-CDN server determines the second MEC-CDN server and establishes a connection with the second MEC-CDN server; the first MEC -The CDN server migrates the state information of the user equipment to the second MEC-CDN server; and, in response to determining that the user equipment enters the coverage area of the second MEC-CDN server, the second MEC-CDN server establishes a connection with the user equipment to Make the user equipment obtain the media service from the second MEC-CDN server.
  • Another aspect of the embodiments of the present disclosure provides a storage medium on which one or more programs are stored, and the one or more programs can be executed by one or more processors, so as to realize the above-mentioned media service between regions. At least one step of the switching method.
  • FIG. 1 is a schematic diagram of the networking of a CDN system including MEC-CDN nodes provided by an embodiment of the disclosure.
  • FIG. 2 is a schematic flowchart of a method for switching media services between regions provided by an embodiment of the disclosure.
  • FIG. 3 is a schematic diagram of a user equipment in a critical position of a service coverage area and/or a cross coverage area according to an embodiment of the disclosure.
  • FIG. 4 is a schematic flowchart of another method for switching media services between regions provided by an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart of another method for switching media services between regions provided by an embodiment of the disclosure.
  • Fig. 6 is a schematic structural diagram of an MEC-CDN server provided by an embodiment of the disclosure.
  • FIG. 7 is a schematic structural diagram of another MEC-CDN server provided by an embodiment of the disclosure.
  • FIG. 8 is a schematic diagram of a functional architecture of an MEC-CDN node provided by an embodiment of the disclosure.
  • FIG. 9 is a schematic structural diagram of a CDN system provided by an embodiment of the disclosure.
  • the service capabilities of traditional CDN edge nodes cannot meet the needs of emerging services such as 4K, 8K, VR, Internet of Things or Internet of Vehicles in the future. Therefore, the service node of CDN is further sinking, which is almost all CDN service providers.
  • the sinking of CDN service nodes on the one hand, means that the content is closer to users, and on the other hand, it means that the number of CDN nodes increases and node management becomes more difficult.
  • the embodiment of the present disclosure also provides a CDN edge node based on the MEC platform (ie, MEC-CDN node). As shown in FIG.
  • the CDN system may include a CDN management platform 101, a CDN central node 102, a CDN edge node 103, an MEC host (MEC host) 104, a core network 105 and a user terminal 106.
  • the MEC host machine 104 includes an MEC platform (MEC platform) 1041, and the MEC platform 1041 and the MEC host machine 104 can use the existing MEC system architecture.
  • the MEC-CDN node 1042 runs on the MEC platform 1041.
  • the MEC platform 1041 is loaded with the main application functions (CDN Application, CDN APP) of the traditional CDN node.
  • the MEC platform 1041 can also implement the local domain name system (service) protocol (Domain Name System, DNS). ) Analysis, the function of user request monitoring and analysis, and the function of monitoring domain name configuration. And an important function of the MEC platform 1041 is to guide the media link requested by the user to the local media service node, that is, the MEC-CDN node 1042, to provide the user with localized streaming media services.
  • service Domain Name System, DNS
  • the MEC platform 1041 can be deployed in a secondary level. In addition to being deployed near the base station, it can also be deployed at the core network node as the MEC management platform, responsible for the collaboration of the lower-level MEC platform. Of course, there are intercommunication channels between different MEC platforms 1041, which are used to exchange some service information of users between different platforms.
  • the MEC-CDN node 1042 may be a virtualized node, loaded by the MEC platform 1041, and deployed at the edge of the access network, which is closer to the user equipment than the edge node of the traditional CDN.
  • the MEC-CDN node 1042 is created/changed/withdrawn according to the requirements of the CDN operation and maintenance system.
  • the MEC-CDN node 1042 can be a complete service node function, or it can be a different combination of a specific CDN core function.
  • the MEC-CDN node 1042 can provide media services for user equipment, and can also provide a method for quickly responding to user equipment switching between different MEC coverage areas.
  • FIG. 2 it is a schematic flowchart of a method for switching media services between regions provided by an embodiment of the disclosure.
  • the method for switching media services between regions may include step S201 to step S204.
  • step S201 the user equipment establishes a connection with the first MEC-CDN node to obtain media services, and the first MEC-CDN node obtains the movement information of the user equipment from the core network.
  • the user equipment when the user sets to apply for a service to the first MEC-CDN node for the first time, please refer to the traditional service application procedure in the related technology for the service flow.
  • the user equipment establishes a connection with the first MEC-CDN node, and the user equipment Obtain the media service from the first MEC-CDN node, and continuously receive the media stream from the first MEC-CDN node while receiving the service.
  • the first MEC-CDN node may subscribe to the 5G core network (5GC) the movement information of the user equipment, which refers to the location movement information of the user equipment; for example, if the user equipment moves from location A to location B, the movement information is A to B.
  • the first MEC-CDN node specifically subscribes mobile information to the Access and Mobility Management Functions (AMF) module in the 5GC, and then adjusts and configures the media service of the user equipment according to the mobile information.
  • AMF Access and Mobility Management Functions
  • step S202 when it is determined that the user equipment pre-moves out of the coverage of the first MEC-CDN node according to the movement information, the second MEC-CDN node and/or the second MEC platform to which the second MEC-CDN node is attached is determined, and the second MEC platform is Two MEC-CDN nodes establish a connection.
  • the user equipment pre-moving out of the coverage of the first MEC-CDN node may refer to: the user equipment is about to leave the coverage of the first MEC-CDN node, but is currently still in the coverage of the first MEC-CDN node range.
  • the user equipment is in a critical position of the service coverage area of the first MEC-CDN node and/or a cross coverage area, it is determined that the user equipment is pre-moved out of the coverage area of the first MEC-CDN node.
  • FIG. 3 it is a schematic diagram of a user equipment in a critical position of a service coverage area and/or a cross coverage area provided by an embodiment of the present disclosure.
  • Putting the user equipment 301 in the critical position 3021 of the service coverage area of the first MEC-CDN node 302 indicates that the user equipment 301 is about to leave the coverage area of the first MEC-CDN node 302; or, the user equipment 302 is in the first MEC-CDN node 302 and When another MEC-CDN node 303 serves the cross coverage area 3022 of the coverage area, it indicates that the user equipment 302 will enter the coverage area of the other MEC-CDN node 302.
  • the second MEC-CDN node discovery mechanism when it is determined that the user equipment pre-moves out of the coverage of the first MEC-CDN node, the second MEC-CDN node discovery mechanism is activated.
  • the MEC management platform may receive the movement information sent by the first MEC-CDN node, and start the second MEC-CDN node discovery mechanism.
  • the MEC management platform selects the second MEC-CDN node and/or the second MEC-CDN platform according to the region of interest of the user equipment.
  • the first MEC-CDN node determines the second MEC-CDN node and/or the second MEC-CDN from the MEC management platform. CDN platform.
  • the area of interest of the user equipment includes but is not limited to the service coverage area that the user equipment is about to enter.
  • the user equipment is about to enter the coverage area of other MEC-CDN nodes 302, and the MEC management platform sets other MEC-CDN nodes 302 serves as the second MEC-CDN node.
  • the MEC management platform may also be based on the current connection of each other MEC-CDN node with other user equipment Select a MEC-CDN node with a small number of connections as the second MEC-CDN node.
  • the second MEC-CDN node and/or the second MEC-CDN platform can also be determined according to the management policy configured by the CDN node management platform where the first MEC-CDN node is located. That is, the first MEC-CDN node notifies the CDN node management platform of the movement information.
  • the CDN node management platform determines the second MEC-CDN node and/or the second MEC-CDN platform in combination with the mobile terminal and the pre-configured management strategy.
  • the management strategy can be to select an MEC-CDN node closest to the first MEC-CDN node according to the movement information; it can also be to select an MEC-CDN node to which the user frequently connects according to the movement information.
  • the second MEC-CDN node discovery mechanism when it is determined that the user equipment is pre-moved out of the coverage of the first MEC-CDN node, the second MEC-CDN node discovery mechanism is activated.
  • the second MEC platform needs to be Further judge to determine whether it has MEC-CDN node function.
  • the first MEC-CDN node discovers that there is no MEC-CDN node function on the second MEC platform after interacting with the MEC management platform, it can request the MEC management platform and/or MEC orchestrator to access the Create a second MEC-CDN node on the second MEC platform.
  • the newly created second MEC-CDN node may not have any application functions, or may be inconsistent with the application functions of the first MEC-CDN node; in order to ensure that the user equipment is migrated from the first MEC-CDN node to the second MEC -The reliability of the CDN node.
  • the first MEC-CDN node can transfer or synchronize its application functions and state to the second MEC-CDN node.
  • the application functions of the first MEC-CDN node may include but are not limited to CDN service functions (streaming media services, web services, etc.), user status monitoring, migration functions, etc., and the status of the first MEC-CDN node may include but is not limited to The first MEC-CDN node provides service status, connection status, and operating status for the user equipment.
  • the first MEC-CDN node After the second MEC-CDN node is determined, the first MEC-CDN node establishes a connection with the second MEC-CDN node.
  • Each MEC-CDN node can communicate with each other based on the MEC-CDN platform on which the MEC-CDN node runs, and the communication interface can use a standard-defined interface, such as the European Telecommunications Standards Institute (ETSI) MEC platform Interface Mp3.
  • ETSI European Telecommunications Standards Institute
  • step S203 the first MEC-CDN node migrates the state information of the user equipment to the second MEC-CDN node in advance.
  • the first MEC-CDN node migrates the current state information of the user equipment to the second MEC-CDN node in advance, so that the second MEC-CDN node is ready to provide media services.
  • the status information may include at least one of the following information: a user identity (Identity Document, ID), a media description file, or service status information.
  • the user ID can be the identity ID information of the user equipment
  • the media description file can be the media information accepted by the user equipment, which can include but is not limited to the media ID, or the uniform resource locator (URL) of the media back to the source
  • service status information It may be the service information provided by the first MEC-CDN node for the user equipment, such as the progress file in the media video currently provided by the first MEC-CDN node for the user equipment, or the interconnection protocol corresponding to the first MEC-CDN node ( Internet Protocol, IP) etc.
  • IP Internet Protocol
  • the second MEC-CDN node Before the second MEC-CDN node establishes a connection with the user equipment, the second MEC-CDN node prepares for providing media services according to the status information.
  • the second MEC-CDN node pre-establishes a signaling channel, a media data channel and/or buffers media data according to the status information.
  • the second MEC-CDN node establishes a signaling channel in advance to shorten the time for establishing a connection between the user equipment and the second MEC-CDN node; establishes a media data channel in advance to shorten the acquisition time for the second MEC-CDN node to obtain media data; Cache media data is to cache the media data according to the media ID and media return URL after the media data channel is established, so as to shorten the response time for the user equipment to obtain the media data from the second MEC-CDN node.
  • the second MEC-CDN node in order to enable the user equipment to quickly establish a connection with the second MEC-CDN node, may also be pre-configured with the same IP as the first MEC-CDN node.
  • the IP of the first MEC-CDN node is IP1
  • the IP of the second MEC-CDN node is IP2
  • the user equipment establishes a session with the first MEC-CDN node to obtain media services; when the user equipment switches to the second MEC-
  • the CDN node because the IP address of the object acquiring the media service changes, the user equipment needs to establish a connection with the second MEC-CDN node through the new session establishment information; when the IP of the second MEC-CDN node is configured as IP1
  • the object for obtaining the media service has not changed, and the user equipment and the second MEC-CDN node can quickly reconnect with the existing session information.
  • the media service function unit may also be pre-configured with the same IP as the first MEC-CDN node.
  • the media service function unit is used to provide media services, and may be the media service of the second MEC-CDN node.
  • the functional unit may also be the media service functional unit of the CDN system where the second MEC-CDN node is located.
  • step S204 when the user equipment enters the coverage area of the second MEC-CDN node, the second MEC-CDN node establishes a connection with the user equipment, so that the user equipment obtains media services from the second MEC-CDN node.
  • the second MEC-CDN node is ready to provide media services.
  • the second MEC-CDN node communicates with the first MEC-CDN node through the user equipment.
  • the signaling link information of the MEC-CDN node establishes a connection with the user equipment, and the signaling link information may be copied by the first MEC-CDN node to the second MEC-CDN node through state information.
  • the user equipment entering the coverage area of the second MEC-CDN node does not include the user equipment being located in the cross coverage area of the first MEC-CDN node and the second MEC-CDN node; because the IP of the second MEC-CDN node and the first MEC-CDN node The node IP is the same, the second MEC-CDN node can quickly reconnect with the user equipment through the existing signaling link information; wherein the signaling link information may include at least one of the following information: session ID, authentication information, or current media Connection information.
  • the second MEC-CDN node before the second MEC-CDN node establishes a connection with the user equipment, when the second MEC-CDN node determines according to the state information that there is no media segment that is the same as the first MEC-CDN node, it will start from the first MEC-CDN node in advance.
  • An MEC-CDN node or media returns to the source to obtain media fragments.
  • the media fragments may refer to a progress file fragment related to the media being played by the current user equipment. Since the second MEC-CDN node caches media data in advance, it is first judged whether the cached media data includes the same media fragments as the first MEC-CDN node.
  • the second The MEC-CDN node provides continuous media services for the user equipment; if the second MEC-CDN node does not have the same media fragments as the first MEC-CDN node, the second MEC-CDN node may obtain the media fragments from the media source.
  • the media source can be a traditional edge node in the core network, or it can be a media URL.
  • the second MEC-CDN node may also obtain media fragments from the first MEC-CDN node.
  • the method of obtaining may be that the first MEC-CDN node pushes the media fragments to the second MEC-CDN node, or the second MEC-CDN node.
  • the CDN node pulls media fragments from the first MEC-CDN node to the local.
  • the second MEC-CDN node pushes the media fragments to the user equipment, so that the user equipment can accept continuous media services;
  • the MEC-CDN node releases the connection with the user equipment. Since the second MEC-CDN pre-duplicates the status information of the first MEC-CDN node, the signaling channel and media data channel are pre-established and the same media data is cached, so that the user equipment can perform real-time operations between different MEC coverage areas. Fast business switching.
  • the second MEC-CDN node and the user equipment restart Transmission Control Protocol (Transmission Control Protocol, TCP) link. That is, when the migration time is greater than the preset time threshold, the second MEC-CDN node is connected to the user equipment through a traditional connection method, and the user equipment needs to disconnect from the first MEC-CDN node and reconnect with the second MEC-CDN node. Make a TCP connection.
  • the preset time threshold can be flexibly set according to the number of user equipments currently connected to the second MEC-CDN node. For example, when the number of user equipments currently connected to the second MEC-CDN node is small, the time preset threshold can be 3s ⁇ 10s.
  • the first MEC-CDN node when the user equipment moves in the coverage area of the first MEC-CDN, the first MEC-CDN node obtains user movement information from the wireless core network; when When the first MEC-CDN node determines that the user equipment is about to move out of the coverage area of the node, the first MEC-CDN searches for the neighboring second MEC-CDN node, and sends the user equipment information to the second MEC-CDN node through the platform intercommunication channel. Status information; the second MEC-CDN node is prepared to provide media services in advance.
  • the existing session information is used Perform a media link with the new second MEC-CDN node; the second MEC-CDN node pushes the cached media services to the user equipment, so that users can quickly switch between different MEC coverage areas when they consume video services , It can achieve less handover delay and improve user experience.
  • FIG. 4 it is a schematic diagram of another flow chart of a method for switching media services between regions provided by an embodiment of the present disclosure.
  • the method for switching media services between regions may include steps S401 to S4010.
  • step S401 the user equipment is connected to the MEC-CDN1 node and receives the local media streaming service.
  • step S402 the MEC-CDN1 node subscribes to the user movement event notification service provided by the AMF in the wireless core network.
  • step S403 the AMF of the wireless core network learns the movement information of the user equipment, and sends the movement information to the MEC-CDN1 node.
  • the movement information may include the location change information of the user equipment, and the AMF has learned the location change of the user equipment, and determined that the user equipment is at a critical location in the coverage area of the MEC-CDN1 node and/or the MEC-CDN1 node and other MEC-CDN nodes When the coverage area is crossed, the movement information is sent to the MEC-CDN1 node.
  • step S404 after receiving the movement information, the MEC-CDN1 determines that the destination serving node of the user equipment is MEC-CDN2.
  • MEC-CDN1 After the MEC-CDN1 node receives the mobile information, it feeds the mobile information back to the MEC management platform, and the MEC management layer learns the next MEC-CDN2 that the user equipment is expected to enter according to the mobile information of the user equipment and the area of interest of the user equipment; MEC The CDN1 node can also notify the Global Server Load Balance (GSLB) system in the CDN system to select a nearest MEC-CDN2 according to the mobile information of the user equipment.
  • GSLB Global Server Load Balance
  • MEC-CDN1 can also combine the two methods for comprehensive analysis to determine a MEC-CDN2 that is closest to the MEC-CDN1 node and conforms to the area of interest of the user equipment.
  • step S405 the MEC platform of the MEC-CDN1 communicates with the MEC platform where the MEC-CDN2 is located, and the status information of the service of the user equipment on the MEC-CDN1 is migrated.
  • MEC-CDN can be a virtual node running on the MEC platform, and MEC nodes can communicate with each other through a standard-defined communication interface, such as the interface Mp3 between ETSI MEC platforms.
  • MEC-CDN1 migrates/copies the status information of the user equipment to MEC-CDN2; the status information may include but is not limited to user name, media ID, media return URL, and/or service status information. At this time, the user media data is still provided by MEC-CDN1.
  • step S406 the MEC-CDN2 pre-starts the link with the media source according to the status information, buffers some media fragments, and modifies the service status information of the MEC-CDN2.
  • MEC-CDN2 can establish a media data channel with the media source in advance and cache some media fragments; meanwhile, MEC-CDN2 CDN2 configures its own IP to be the same as that of MEC-CDN1, so that MEC-CDN2 can establish a connection with the user equipment based on the signaling link information between the user equipment and MEC-CDN1.
  • step S407 when MEC-CDN2 does not have the same media segment as MEC-CDN1, it requests the same media segment from MEC-CDN1.
  • MEC-CDN2 detects the media source and media service parameters of the buffered media segments, and when it determines that there is no media segment that is the same as MEC-CDN1, it requests the same media segment from MEC-CDN1.
  • the same media segment refers to a progress file segment related to the media being played by the current user.
  • step S408 after the user equipment has completely moved to the coverage area of MEC-CDN2, it continues to request media content.
  • step S409 MEC-CDN2 establishes a connection with the user equipment, and in response to the user's request, pushes the previously cached fragments to the user equipment.
  • MEC-CDN2 Since the IP of MEC-CDN2 is configured to be the same as the IP of MEC-CDN1, MEC-CDN2 and user equipment can quickly establish a connection based on the existing signaling link information, which may include but is not limited to session ID and authentication Information, and/or current media connection information.
  • existing signaling link information which may include but is not limited to session ID and authentication Information, and/or current media connection information.
  • MEC-CDN2 When MEC-CDN2 requests media content, the user equipment’s request is directed to MEC-CDN2, and then MEC-CDN2 pushes the media fragments to the user equipment to ensure that the user equipment receives continuous media services.
  • step S4010 the user continuously receives the media stream from the MEC-CDN2, and at the same time the MEC-CDN1 releases the link resource with the user.
  • the user equipment first establishes a connection with MEC-CDN1 in region 1 to obtain media services.
  • MEC-CDN1 obtains the mobile information of the user equipment from the wireless core network, and communicates with the next MEC-CDN2 in advance to migrate the state information of the user equipment.
  • MEC-CDN2 advances Cache media data; when there is no media segment that is the same as MEC-CDN1, it can also be obtained from MEC-CDN1 or the source station in advance.
  • the user equipment moves to area 2, it uses the existing session information to connect with MEC-CDN2.
  • MEC-CDN2 when MEC-CDN2 is pre-configured with the same IP as MEC-CDN1, it can quickly reconnect through existing session information and disconnect the user equipment from MEC-CDN1 in area 1.
  • Real-time service switching can be realized quickly, and the response time of user equipment requests can be reduced through pre-cached media fragments.
  • FIG. 5 it is a schematic flow diagram of another method for switching media services between regions provided by an embodiment of the present disclosure.
  • the method for switching media services between regions may include steps S501 to S5011.
  • step S501 the user equipment is connected to the MEC-CDN1 node and receives the local media streaming service.
  • step S502 the MEC-CDN1 node subscribes to the user movement event notification service provided by the AMF in the wireless core network.
  • step S503 when the AMF of the wireless core network learns the movement information of the user equipment, it sends the movement information to the MEC-CDN1 node.
  • the movement information may include the location change information of the user equipment, and the AMF has learned the location change of the user equipment, and determined that the user equipment is at a critical location in the coverage area of the MEC-CDN1 node and/or the MEC-CDN1 node and other MEC-CDN nodes When the coverage area is crossed, the movement information is sent to the MEC-CDN1 node.
  • step S504 after receiving the movement information, the MEC-CDN1 determines that the destination serving node of the user equipment is the MEC platform 2, and the MEC platform 2 reports that the MEC-CDN node function is not currently activated. That is, there is no MEC-CDN node on the MEC platform 2.
  • step S505 after receiving the feedback information, the MEC-CDN1 sends a service request to the MEC management platform and/or the MEC orchestrator, requesting to create an MEC-CDN2 on the MEC platform 2.
  • step S506 the MEC platform 1 of the MEC-CDN1 communicates with the MEC platform 2 to migrate the status information of the service of the user equipment on the MEC-CDN1 and the CDN node function of the MEC-CDN1 itself.
  • MEC-CDN can be a virtual node, running on the MEC platform.
  • MEC platforms can communicate with each other through standard-defined communication interfaces, such as the interface Mp3 between ETSI MEC platforms, and then MEC-CDN1 will connect users Migrate/copy the status information of the equipment to MEC-CDN2.
  • the status information may include, but is not limited to, user name, media ID, media return URL, and/or service status information.
  • the user media data is still provided by MEC-CDN1.
  • MEC-CDN1 can choose to synchronize its own CDN node functions and status to migrate/copy to MEC-CDN2.
  • step S507 MEC-CDN2 pre-starts the link with the media source according to the status information, caches some media fragments, and modifies the service status information of MEC-CDN2.
  • MEC-CDN2 can establish a media data channel with the media source in advance, and cache some media fragments.
  • MEC-CDN2 configures its own IP to be the same as that of MEC-CDN1, so that MEC-CDN2 can establish a connection with the user equipment based on the signaling link information between the user equipment and MEC-CDN1.
  • step S508 when MEC-CDN2 does not have the same media segment as MEC-CDN1, it requests the source station for the same media segment.
  • MEC-CDN2 detects the media source and media service parameters of the cached media fragments, and when it determines that there is no media fragment that is the same as MEC-CDN1, it requests the same media fragment from the source station.
  • the same media fragment may refer to a progress file fragment related to the media being played by the current user, and the source station may be a traditional edge node of the core network.
  • step S509 after the user equipment has completely moved to the coverage area of MEC-CDN2, it continues to request media content.
  • step S5010 MEC-CDN2 establishes a connection with the user equipment, and in response to the user's request, pushes the previously cached fragments to the user equipment.
  • the signaling link information may include but is not limited to session ID, authentication information, and/or current media connection information.
  • MEC-CDN2 When MEC-CDN2 requests media content, the user equipment's request is directed to MEC-CDN2, and then MEC-CDN2 pushes media fragments to the user equipment to ensure that the user equipment receives continuous media services.
  • step S5011 the user continuously receives the media stream from the MEC-CDN2, and at the same time the MEC-CDN1 releases the link resource with the user.
  • the user equipment first establishes a connection with MEC-CDN1 in region 1 to obtain media services.
  • MEC-CDN1 obtains the mobile information of the user equipment from the wireless core network, determines the MEC-CDN platform 2, and when there is no MEC-CDN node in the MEC-CDN platform 2, Create MEC-CDN node 2 (ie, MEC-CDN2) through the MEC-CDN management platform, and communicate with MEC-CDN2 in advance to migrate the state information of the user equipment;
  • MEC-CDN2 pre-caches media data, when there is no MEC-CDN2
  • CDN1 has the same media segment, you can also obtain the same media segment as MEC-CDN1 from MEC-CDN1 or the source station in advance.
  • the existing session information can be used to connect with MEC-CDN2.
  • MEC-CDN2 when MEC-CDN2 is pre-configured to have the same IP as MEC-CDN1, it can quickly reconnect through the existing session information and disconnect the user equipment from MEC-CDN1 in area 1.
  • the user equipment can realize fast switching of real-time services, and the response time of user equipment requests can be reduced through pre-cached media fragments.
  • the embodiment of the present disclosure also provides an MEC-CDN server, as shown in FIG. 6, which is a schematic structural diagram of the MEC-CDN server provided by the embodiment of the present disclosure.
  • the first MEC-CDN server 60 may include a first processor 601, a first memory 602, and a first communication bus 603.
  • the first communication bus 603 may be configured to implement connection and communication between the first processor 601 and the first memory 602.
  • the first processor 601 may be configured to execute one or more programs stored in the first memory 602 to implement at least one step of the above-mentioned method for switching media services between regions implemented by the first MEC-CDN node.
  • the embodiment of the present disclosure also provides another second MEC-CDN server, as shown in FIG. 7, which is a schematic structural diagram of the other MEC-CDN server provided by the embodiment of the present disclosure.
  • the second MEC-CDN server 70 may include a second processor 701, a second memory 702, and a second communication bus 703.
  • the second communication bus 703 may be configured to implement connection and communication between the second processor 701 and the second memory 702.
  • the second processor 701 may be configured to execute one or more programs stored in the second memory 702 to implement at least one step of the method for switching media services between regions implemented by the second MEC-CDN node.
  • FIG. 8 it is a schematic diagram of a functional architecture of the MEC-CDN node provided by an embodiment of the disclosure.
  • the main logic function of the virtual MEC-CDN node is mainly composed of software running on one or more virtual machines (Virtual Machine, VM).
  • VM Virtual Machine
  • the MEC-CDN node can be further divided into two subsystems, namely the business management subsystem function and the media service function based on the MEC edge server.
  • the business management subsystem subscribes to the user's mobile information from 5GC (further the AMF module in 5GC), and adjusts and configures CDN media service functions based on this information.
  • the media service function provides media services for user equipment; the media service function can be virtual or physical nodes, controlled by the business management subsystem.
  • the MEC-CDN-based functions may mainly include but are not limited to: storage/caching functions, streaming media service functions, business management functions, and/or load balancing functions.
  • the MEC-CDN node APP runs on the MEC platform, which can also deploy other applications.
  • the MEC platform needs to deploy CDN service registration capabilities, traffic management policies, and/or local DNS (LDNS) capabilities. It is also necessary to deploy the user mobility event subscription monitoring function, specifically to subscribe to the AMF module in the 5GC, and the user equipment state migration function.
  • the MEC platform guides the media link requested by the user to the local media service MEC-CDN node to provide users with localized streaming media services.
  • MEC host and MEC platform (MEC platform) in Figure 8 are existing technologies and conform to the definition of the ETSI MEC specification, and the data plane channel/virtual underlying architecture in Figure 8 is an existing technology. It has the capability of MEC itself, so I won't repeat it here.
  • the hardware structure of the aforementioned MEC-CDN server may be an MEC host.
  • the CDN system may at least include a first MEC-CDN server 901, a second MEC-CDN server 902, a core network 903, and a user terminal (or user equipment) 904. It should be understood that any MEC-CDN server may include an MEC-CDN node and an MEC platform to which the MEC-CDN node is attached.
  • the first MEC-CDN server 901 and the second MEC-CDN server 902 have an intercommunication channel.
  • the user terminal 904 establishes a connection with the first MEC-CDN server 901 to obtain media services, and the first MEC-CDN server 901 obtains the movement information of the user terminal 904 from the core network 903.
  • the first MEC-CDN server 901 determines that the user terminal 904 pre-moves out of the coverage of the first MEC-CDN server 901 according to the movement information, it determines the second MEC-CDN server 902 and establishes a connection with the second MEC-CDN server 902.
  • the first MEC-CDN server 901 migrates the state information of the user terminal 904 to the second MEC-CDN server 902 in advance.
  • the second MEC-CDN server 902 When the user terminal 904 enters the coverage area of the second MEC-CDN server 902, the second MEC-CDN server 902 establishes a connection with the user terminal 904, so that the user terminal 904 obtains media services from the second MEC-CDN server 902.
  • the CDN system may include a management system and a distribution system.
  • the management system is responsible for node status management, and/or configuration, etc.
  • the management system can also generate an additional 5G AMF function, and can also copy some pre-configured management policies to the MEC node.
  • the distribution system can be divided into storage nodes and GSLB systems. Among them, GSLB is responsible for load balancing and selects the nearest MEC-CDN node for user equipment to serve.
  • Storage nodes may include traditional access nodes (Point of Presence, POP) or cache (cache) nodes, as well as MEC-CDN nodes.
  • Traditional POP nodes deploy edge nodes of physical nodes on the edge of the core network according to existing deployment methods.
  • the MEC-CDN node can be a virtualized node, loaded by the MEC server, and deployed at the edge of the access network, for example, a base station (BS) or a baseband unit (BBU).
  • BS base station
  • BBU
  • the embodiments of the present disclosure also provide a storage medium, which includes volatile or non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Volatile, removable or non-removable media.
  • Storage media includes but not limited to RAM (Random Access Memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory Or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or can be used Any other medium that can store desired information and can be accessed by a computer.
  • the storage medium provided in the embodiments of the present disclosure may be configured to store one or more computer programs, and the stored one or more computer programs may be executed by a processor to implement at least one step of the above-mentioned method for switching media services between regions .
  • communication media usually contain computer-readable instructions, data structures, computer program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. Therefore, the present disclosure is not limited to any specific hardware and software combination.

Abstract

本公开提供一种媒体服务在区域间的切换方法、服务器、系统及存储介质。第一MEC-CDN节点从核心网获取用户设备的移动信息；其中，用户设备与第一MEC-CDN节点建立了连接，并从第一MEC-CDN节点获取媒体服务；响应于根据移动信息确定用户设备预移出第一MEC-CDN节点的覆盖范围，第一MEC-CDN节点确定第二MEC-CDN节点和/或第二MEC-CDN节点依附的第二MEC平台，并与第二MEC-CDN节点建立连接；第一MEC-CDN节点将用户设备的状态信息迁移至第二MEC-CDN节点上；以及，响应于确定用户设备进入第二MEC-CDN节点的覆盖区域，第二MEC-CDN节点与用户设备建立连接，以使得用户设备从第二MEC-CDN节点获取媒体服务。

Description

媒体服务在区域间的切换方法、服务器、系统及存储介质 技术领域
本公开涉及但不限于通信技术领域。
背景技术
内容分发网络(Content Delivery Network，CDN)在互联网音视频传输、网络协议电视(Internet Protocol Television，IPTV)和网络媒体传输等领域已广泛应用，其中CDN的核心思想是将内容推送到离用户最近的服务节点上，使得用户就近访问内容。使用CDN进行媒体传输能够极大的提高用户对于媒体内容获取的相应速度，也极大的减少了媒体内容在骨干网络上传输的带宽压力。目前，互联网的各种业务都进入了高速发展的阶段，对于音视频的质量要求也在不断的提高，未来4K，8K，多视角，虚拟现实技术(Virtual Reality，VR)视频都可能是在网络上传输的主要内容。此外，互联网也在不断的推出各种新型的业务，其中很多业务都需要CDN进行加速服务；因此，CDN网络逐渐成为运营商的一项基础设施。
但是，无论是有线网络还是无线网络，由于传统业务的需求，CDN的边缘节点一般都部署在网络层次比较高的地方，例如，核心网的边缘部分，这对于传统的网页，标清多媒体内容的请求响应是适用的。未来4K，8K，VR，物联网以及车联网等新兴业务对于终端和服务器之间的响应有着极高的要求，对于服务质量提出了高通量，低延时，服务质量(Quality of Service，QoS)保障的要求。此时，传统的CDN边缘节点的服务能力就不能满足上述新业务的需求。
发明内容
本公开实施例的一个方面提供一种媒体服务在区域间的切换方法，包括：第一MEC(Mobile-Edge Computing，移动边缘计算)-CDN节点从核心网获取用户设备的移动信息；其中，用户设备与第一MEC-CDN节点建立了连接，并从第一MEC-CDN节点获取媒体服务；响 应于根据移动信息确定用户设备预移出第一MEC-CDN节点的覆盖范围，第一MEC-CDN节点确定第二MEC-CDN节点和/或第二MEC-CDN节点依附的第二MEC平台，并与第二MEC-CDN节点建立连接；第一MEC-CDN节点将用户设备的状态信息迁移至第二MEC-CDN节点上；以及，响应于确定用户设备进入第二MEC-CDN节点的覆盖区域，第二MEC-CDN节点与用户设备建立连接，以使得用户设备从第二MEC-CDN节点获取媒体服务。
本公开实施例的另一方面提供一种第一MEC-CDN服务器，包括第一处理器、第一存储器，以及第一通信总线，其中：第一通信总线被配置为实现第一处理器和第一存储器之间的连接通信；以及，第一处理器被配置为执行第一存储器中存储的一个或者多个第一程序，以实现如上所述的媒体服务在区域间的切换方法的由第一MEC-CDN节点实施的至少一个步骤。
本公开实施例的又一方面提供一种第二MEC-CDN服务器，包括第二处理器、第二存储器，以及第二通信总线，其中：第二通信总线被配置为实现第二处理器和第二存储器之间的连接通信；以及，第二处理器被配置为执行第二存储器中存储的一个或者多个第二程序，以实现如权上所述的媒体服务在区域间的切换方法的由第二MEC-CDN节点实施的至少一个步骤。
本公开实施例的再一方面提供一种CDN系统，包括第一MEC-CDN服务器、第二MEC-CDN服务器、核心网，以及用户设备；其中：第一MEC-CDN服务器包括第一MEC-CDN节点以及第一MEC-CDN节点依附的第一MEC平台；第二MEC-CDN服务器包括第二MEC-CDN节点以及第二MEC-CDN节点依附的第二MEC平台；第一MEC-CDN服务器与第二MEC-CDN服务器存在互通通道；第一MEC-CDN服务器从核心网获取用户设备的移动信息；其中，用户设备与第一MEC-CDN服务器建立了连接，并从第一MEC-CDN服务器获取媒体服务；响应于根据移动信息确定用户设备预移出第一MEC-CDN服务器的覆盖范围，第一MEC-CDN服务器确定第二MEC-CDN服务器，并与第二MEC-CDN服务器建立连接；第一MEC-CDN服务器将用户设备的状态信息迁移至第二MEC-CDN服务 器上；以及，响应于确定用户设备进入第二MEC-CDN服务器的覆盖区域，第二MEC-CDN服务器与用户设备建立连接，以使得用户设备从第二MEC-CDN服务器获取媒体服务。
本公开实施例的再一方面提供一种存储介质，其上存储有一个或者多个程序，一个或者多个程序可被一个或者多个处理器执行，以实现如上所述的媒体服务在区域间的切换方法的至少一个步骤。
附图说明
图1为本公开实施例提供的包括MEC-CDN节点的CDN系统的组网示意图。
图2为本公开实施例提供的媒体服务在区域间的切换方法的流程示意图。
图3为本公开实施例提供的用户设备处于服务覆盖区域临界位置和/或交叉覆盖区域的示意图。
图4为本公开实施例提供的媒体服务在区域间的切换方法的另一种流程示意图。
图5为本公开实施例提供的媒体服务在区域间的切换方法的又一种流程示意图。
图6为本公开实施例提供的MEC-CDN服务器的一种结构示意图。
图7为本公开实施例提供的另一种MEC-CDN服务器的一种结构示意图。
图8为本公开实施例提供的MEC-CDN节点的一种功能架构示意图。
图9为本公开实施例提供的CDN系统的一种结构示意图。
具体实施方式
为了使本公开的目的、技术方案及优点更加清楚明白，下面通过具体实施方式结合附图对本公开实施例作进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本公开，并不用于限定本公开。
在相关技术中，传统的CDN边缘节点的服务能力不能满足未来4K，8K，VR，物联网或者车联网等新兴业务的需求，因此，将CDN的服务节点进一步下沉，是几乎所有CDN服务商的一个普遍需求。但是CDN服务节点的下沉，一方面意味着内容离用户更近，另一方面却意味着CDN节点数量的增多，节点管理难度变大。而在无线通讯网络中，节点越是下沉，服务范围则越是缩小；尤其在5G场景下，一个基站的覆盖范围仅有500米左右，而无线网络中用户设备很多情况下是处于移动状态的，所以在多个节点的覆盖范围之间进行切换的需求比在有线网络中要多。而目前有线CDN的业务切换流程，对于这种情况下，用户切换的体验就无法保证。为了解决上述问题，本公开实施例中除了传统的CDN中心节点，边缘节点之外，还提供了一个基于MEC平台的CDN边缘节点(即，MEC-CDN节点)。如图1所示，其为本公开实施例提供的包括MEC-CDN节点的CDN系统的组网示意图。该CDN系统可包括CDN管理平台101，CDN中心节点102，CDN边缘节点103，MEC宿主机(MEC host)104，核心网105和用户终端106。MEC宿主机104包括MEC平台(MEC platform)1041，MEC平台1041和MEC宿主机104可以使用现有的MEC系统架构。MEC-CDN节点1042运行在MEC平台1041上，该MEC平台1041加载了传统CDN节点的主要应用功能(CDN Application，CDN APP)，另外也可以实现本地域名系统(服务)协议(Domain Name System，DNS)解析，用户请求监听分析的功能，以及监听域名配置功能。且MEC平台1041的一个重要功能是将用户请求的媒体链路引导到本地媒体服务节点，即MEC-CDN节点1042，为用户提供本地化的流媒体服务。
值得注意的是，MEC平台1041可以进行二级部署，除了部署在基站附近，也可以部署在核心网节点，作为MEC管理平台，负责下级MEC平台的协同。当然不同的MEC平台1041之间有互通通信通道，用于在不同的平台之间交换用户的一些业务信息。
根据本公开提供的实施例，MEC-CDN节点1042可以是虚拟化节点，由MEC平台1041加载，部署于接入网络的边缘，相比传统CDN的边缘节点更加接近用户设备。MEC-CDN节点1042受CDN运维系统 的需求而创建/改变/撤销，其中MEC-CDN节点1042可以是一个完整的服务节点功能，也可以是一组特定的CDN核心功能的不同组合。该MEC-CDN节点1042可为用户设备提供媒体服务，还可以提供一种快速响应用户设备在不同MEC覆盖区域之间切换的方法。
如图2所示，其为本公开实施例提供的媒体服务在区域间的切换方法的流程示意图。该媒体服务在区域间的切换方法可包括步骤S201～步骤S204。
在步骤S201中，用户设备与第一MEC-CDN节点建立连接，以获取媒体服务，且第一MEC-CDN节点从核心网获取用户设备的移动信息。
根据本公开提供的实施例，该当用户设置首次向第一MEC-CDN节点进行业务申请时，业务流程请参考相关技术中传统业务申请步骤，用户设备与第一MEC-CDN节点建立连接，用户设备从第一MEC-CDN节点获取媒体服务，并在接受服务中，持续不断的从第一MEC-CDN节点接受媒体流。第一MEC-CDN节点可以向5G核心网(5GC)订阅用户设备的移动信息，该移动信息指的是用户设备的位置移动信息；例如，用户设备从位置A移动到位置B，则移动信息为A到B。第一MEC-CDN节点具体向5GC中的接入和移动性管理功能(Access and Mobility Management Functions，AMF)模块订阅移动信息，进而根据该移动信息对用户设备的媒体服务进行调整和配置。
在步骤S202中，根据移动信息确定用户设备预移出第一MEC-CDN节点的覆盖范围时，确定第二MEC-CDN节点和/或第二MEC-CDN节点依附的第二MEC平台，并与第二MEC-CDN节点建立连接。
根据本公开提供的实施例，用户设备预移出第一MEC-CDN节点的覆盖范围可以指：用户设备将要离开第一MEC-CDN节点的覆盖范围，但当前仍然在第一MEC-CDN节点的覆盖范围。例如，当用户设备处于第一MEC-CDN节点服务覆盖区域临界位置和/或交叉覆盖区域时，确定用户设备预移出第一MEC-CDN节点的覆盖范围。如图3所示，其为本公开实施例提供的用户设备处于服务覆盖区域临界位置和/或交叉覆盖区域的示意图。将用户设备301处于第一MEC-CDN节点302服务覆盖区域临界位置3021，表示用户设备301将要离开第一MEC-CDN 节点302的覆盖范围；或，用户设备302处于第一MEC-CDN节点302与其他MEC-CDN节点303服务覆盖区域的交叉覆盖区域3022时，表示用户设备302将要进入其他MEC-CDN节点302的覆盖范围。
根据本公开提供的实施例，当确定用户设备预移出第一MEC-CDN节点的覆盖范围时，启动第二MEC-CDN节点发现机制。具体地，可以是MEC管理平台接收第一MEC-CDN节点发送的移动信息，启动第二MEC-CDN节点发现机制。MEC管理平台根据用户设备的兴趣区域选择第二MEC-CDN节点和/或第二MEC-CDN平台，第一MEC-CDN节点从MEC管理平台确定第二MEC-CDN节点和/或第二MEC-CDN平台。其中，用户设备的兴趣区域包括但不限于用户设备即将进入的服务覆盖区域，例如如图3所示，用户设备即将进入其他MEC-CDN节点302的覆盖范围，MEC管理平台将其他MEC-CDN节点302作为第二MEC-CDN节点。在一些示例性实例中，当用户设备即将进入的服务覆盖区域包括至少两个其他MEC-CDN节点的交叉覆盖区域，该MEC管理平台还可以根据各个其他MEC-CDN节点当前与其他用户设备的连接数，选择一个连接数较少的MEC-CDN节点作为第二MEC-CDN节点。
根据本公开提供的实施例，还可以根据第一MEC-CDN节点所在的CDN节点管理平台配置的管理策略，确定第二MEC-CDN节点和/或第二MEC-CDN平台。即第一MEC-CDN节点将移动信息告知CDN节点管理平台，该CDN节点管理平台结合移动终端和预先配置的管理策略，确定第二MEC-CDN节点和/或第二MEC-CDN平台。管理策略可以是根据移动信息选择一个离第一MEC-CDN节点最近的MEC-CDN节点；也可以是根据移动信息选择一个用户经常连接的MEC-CDN节点。
根据本公开提供的实施例，确定用户设备预移出第一MEC-CDN节点的覆盖范围时，启动第二MEC-CDN节点发现机制，当确定第二MEC平台时，还需要对第二MEC平台进行进一步判断，确定其是否存在MEC-CDN节点功能。具体地，当第一MEC-CDN节点通过和MEC管理平台的交互后发现第二MEC平台上没有MEC-CDN节点功能时，可以通过预先配置的策略请求MEC管理平台和/或MEC编排器来在第二MEC平台上创建第二MEC-CDN节点。可以理解的是，新创建的第二MEC-CDN 节点可能不存在任何应用功能，或与第一MEC-CDN节点的应用功能不一致；为了保证用户设备从第一MEC-CDN节点迁移到第二MEC-CDN节点的可靠性，在创建第二MEC-CDN的节点过程中，第一MEC-CDN节点可以将自身应用功能和状态迁移或者同步复制到第二MEC-CDN节点上。第一MEC-CDN节点的自身应用功能可包括但不限于CDN服务功能(流媒体服务、web服务等)、用户状态监测、迁移功能等，第一MEC-CDN节点自身的状态可包括但不限于第一MEC-CDN节点为用户设备提供的服务状态、连接状态，以及运行状态等。
在确定第二MEC-CDN节点后，第一MEC-CDN节点与第二MEC-CDN节点建立连接。各个MEC-CDN节点可以基于其上运行MEC-CDN节点的MEC-CDN平台进行相互通信，通信接口可以使用标准定义的接口，例如欧洲电信标准化协会(European Telecommunications Standards Institute，ETSI)MEC平台之间的接口Mp3。
在步骤S203中，第一MEC-CDN节点将用户设备的状态信息预先迁移在第二MEC-CDN节点上。
根据本公开提供的实施例，第一MEC-CDN节点将当前用户设备的状态信息预先迁移到第二MEC-CDN节点上，以便于第二MEC-CDN节点做好提供媒体服务的准备。状态信息可包括以下信息中的至少一种：用户身份标识(Identity Document，ID)、媒体描述文件，或服务状态信息。用户ID可以是用户设备的身份ID信息；媒体描述文件可以是用户设备接受的媒体信息，可包括但不限于媒体ID，或媒体回源统一资源定位符(Uniform Resource Locator，URL)；服务状态信息可以是第一MEC-CDN节点为用户设备提供的服务信息，例如第一MEC-CDN节点当前为用户设备提供的媒体视频中的进度文件，或者第一MEC-CDN节点所对应的互连协议(Internet Protocol，IP)等。
在第二MEC-CDN节点与用户设备建立连接之前，第二MEC-CDN节点根据状态信息为提供媒体服务进行准备。第二MEC-CDN节点根据状态信息预先建立信令通道、媒体数据通道和/或缓存媒体数据。第二MEC-CDN节点预先建立信令通道，以缩短用户设备与第二MEC-CDN 节点连接的建立时间；预先建立媒体数据通道，以缩短第二MEC-CDN节点获取媒体数据的获取时间；预先缓存媒体数据是在建立媒体数据通道后，根据媒体ID和媒体回源URL缓存媒体数据，以缩短用户设备从第二MEC-CDN节点获取媒体数据的响应时间。
根据本公开提供的实施例，为了使得用户设备与第二MEC-CDN节点快速建立连接，第二MEC-CDN节点还可以被预先配置与第一MEC-CDN节点相同的IP。例如，第一MEC-CDN节点的IP为IP1，第二MEC-CDN节点的IP为IP2，用户设备与第一MEC-CDN节点建立了会话，获取媒体服务；当用户设备切换到第二MEC-CDN节点时，由于获取媒体服务的对象的IP地址发生变化，用户设备需要通过新的会话建立信息与第二MEC-CDN节点建立连接；当第二MEC-CDN节点的IP被配置为IP1时，对于用户设备来说，获取媒体服务的对象并没有发生变化，进而用户设备与第二MEC-CDN节点可以现有的会话信息进行快速重连。根据本公开提供的实施例，媒体服务功能单元也可以被预先配置与第一MEC-CDN节点相同的IP，该媒体服务功能单元用于提供媒体服务，可以是第二MEC-CDN节点的媒体服务功能单元，也可以是第二MEC-CDN节点所在CDN系统的媒体服务功能单元。
在步骤S204中，当用户设备进入第二MEC-CDN节点的覆盖区域时，第二MEC-CDN节点与用户设备建立连接，以使得用户设备从第二MEC-CDN节点获取媒体服务。
根据本公开提供的实施例，第二MEC-CDN节点已经做好提供媒体服务的准备工作，当用户设备进入第二MEC-CDN节点的覆盖区域，第二MEC-CDN节点通过用户设备与第一MEC-CDN节点的信令链接信息与用户设备建立连接，该信令链接信息可以是第一MEC-CDN节点通过状态信息复制到第二MEC-CDN节点上的。用户设备进入第二MEC-CDN节点的覆盖区域不包括用户设备位于第一MEC-CDN节点与第二MEC-CDN节点的交叉覆盖区域；由于第二MEC-CDN节点的IP与第一MEC-CDN节点IP相同，第二MEC-CDN节点可通过现有的信令链接信息与用户设备进行快速重连；其中，信令链接信息可包括下列信息至少之一：会话ID、认证信息，或当前媒体连接信息。
根据本公开提供的实施例，在第二MEC-CDN节点与用户设备建立连接之前，第二MEC-CDN节点根据状态信息确定没有与第一MEC-CDN节点相同的媒体分片时，预先从第一MEC-CDN节点或媒体回源获取媒体分片，该媒体分片可以指当前用户设备播放媒体相关的进度文件分片。由于第二MEC-CDN节点预先缓存媒体数据，先判断缓存的媒体数据中是否包括与第一MEC-CDN节点相同的媒体分片，若存在同样的媒体分片，则在建立连接后，第二MEC-CDN节点为用户设备提供连续的媒体服务；若第二MEC-CDN节点没有与第一MEC-CDN节点相同的媒体分片时，第二MEC-CDN节点可从媒体源获取媒体分片。媒体源可以是处于核心网的传统边缘节点，也可以是媒体URL。第二MEC-CDN节点还可以从第一MEC-CDN节点获取媒体分片，获取的方法可以是第一MEC-CDN节点推送媒体分片至第二MEC-CDN节点，也可以是第二MEC-CDN节点从第一MEC-CDN节点拉取媒体分片到本地。
根据本公开提供的实施例，当第二MEC-CDN节点与用户设备建立连接后，第二MEC-CDN节点将媒体分片推送给用户设备，以使得用户设备接受连续的媒体服务；同时第一MEC-CDN节点释放和用户设备连接。由于第二MEC-CDN预先复制了第一MEC-CDN节点的状态信息，预先建立了信令通道、媒体数据通道并缓存了相同的媒体数据，使得用户设备可以在不同的MEC覆盖区域间进行实时业务快速切换。
根据本公开提供的实施例，当第一MEC-CDN节点将用户设备的状态信息迁移到第二MEC-CDN节点的迁移时间大于预设时间阈值时，第二MEC-CDN节点与用户设备重新启动传输控制协议(Transmission Control Protocol，TCP)链接。即当迁移时间大于预设时间阈值时，第二MEC-CDN节点与用户设备通过传统的连接方式进行连接，用户设备需断开与第一MEC-CDN节点的连接，与第二MEC-CDN重新进行TCP链接。预设时间阈值可以根据第二MEC-CDN节点当前连接的用户设备的数量进行灵活设置，例如，当第二MEC-CDN节点当前连接的用户设备的数量不多时，该时间预设阈值可以为3s～10s。
根据本公开实施例提供的媒体服务在区域间的切换方法，当用户设备在第一MEC-CDN覆盖区域中进行移动的时候，第一MEC-CDN 节点从无线核心网中获取用户移动信息；当第一MEC-CDN节点判断用户设备即将移动出本节点覆盖范围时，第一MEC-CDN搜索相邻的第二MEC-CDN节点，并通过平台互通通道向第二MEC-CDN节点发送用户设备的状态信息；第二MEC-CDN节点预先做好提供媒体服务的准备，当用户完全移出第一MEC-CDN节点覆盖范围，且移动进第二MEC-CDN节点覆盖范围时，利用现有的会话信息和新的第二MEC-CDN节点进行媒体链接；第二MEC-CDN节点通过将缓存的媒体服务推送给用户设备，使得用户在进行视频业务消费的时候，可以在不同MEC覆盖区域间进行快速切换，可以做到较少时间的切换延迟，提高用户体验。
如图4所示，其为本公开实施例提供的媒体服务在区域间的切换方法的另一种流程示意图，该媒体服务在区域间的切换方法可包括步骤S401～步骤S4010。
在步骤S401中，用户设备连接到MEC-CDN1节点，接受本地的媒体流服务。
在步骤S402中，MEC-CDN1节点订阅无线核心网中AMF提供的用户移动事件通知服务。
在步骤S403中，无线核心网的AMF获知到了用户设备的移动信息，并将移动信息发给MEC-CDN1节点。
该移动信息可包括用户设备的位置变化信息，且AMF获知了用户设备的位置变化，且确定用户设备处于MEC-CDN1节点服务覆盖区域临界位置和/或MEC-CDN1节点与其他MEC-CDN节点的交叉覆盖区域时，将该移动信息发送给MEC-CDN1节点。
在步骤S404中，MEC-CDN1接收移动信息之后，确定用户设备的目的服务节点为MEC-CDN2。
MEC-CDN1节点接收到移动信息后，将该移动信息反馈给MEC管理平台，由MEC管理层根据用户设备的移动信息、用户设备的兴趣区域获知用户设备预要进入的下一个MEC-CDN2；MEC-CDN1节点也可以通知CDN系统中的全局负载均衡(Global Server Load Balance，GSLB)系统根据用户设备的移动信息选择一个最近的MEC-CDN2。当然，MEC-CDN1还可以结合两种方式综合分析，确定一个离MEC-CDN1节点 最近且符合用户设备的兴趣区域的MEC-CDN2。
在步骤S405中，MEC-CDN1的MEC平台和MEC-CDN2所在的MEC平台进行通讯，将用户设备在此MEC-CDN1上的服务的状态信息进行迁移。
可以理解的是，MEC-CDN可为虚拟节点，运行在MEC平台上，MEC节点之间可通过标准定义的通信接口进行相互通信，如ETSI MEC平台之间的接口Mp3。MEC-CDN1将用户设备的状态信息迁移/复制到MEC-CDN2上；其中，状态信息可包括但不限于用户名、媒体ID、媒体回源URL，和/或服务状态信息等。此时用户媒体数据仍然由MEC-CDN1提供。
在步骤S406中，MEC-CDN2根据状态信息预先启动和媒体源的链接，缓存部分媒体分片，并对MEC-CDN2的服务状态信息进行修改。
根据本公开提供的实施例，由于状态信息包括媒体ID，媒体回源URL等相关的媒体描述文件，此时MEC-CDN2可以预先与媒体源建立媒体数据通道，缓存部分媒体分片；同时MEC-CDN2将自身IP配置成与MEC-CDN1的IP一样，便于以后MEC-CDN2基于用户设备与MEC-CDN1的信令链接信息，与该用户设备建立连接。
在步骤S407中，MEC-CDN2没有与MEC-CDN1相同的媒体分片时，向MEC-CDN1请求相同的媒体分片。
MEC-CDN2检测缓存的媒体分片的媒体源和媒体服务参数，确定没有与MEC-CDN1相同的媒体分片时，向MEC-CDN1请求相同的媒体分片。该相同的媒体分片指的是当前用户播放媒体相关的进度文件分片。
在步骤S408中，当用户设备完全移动至MEC-CDN2的覆盖区域之后，持续请求媒体内容。
在步骤S409中，MEC-CDN2与用户设备建立连接，并响应用户的请求，将之前缓存的分片推送给用户设备。
由于MEC-CDN2的IP被配置为与MEC-CDN1的IP相同，MEC-CDN2与用户设备可基于现有的信令链接信息快速建立连接，该信令链接信息可包括但不限于会话ID、认证信息，和/或当前媒体连接信息。
当MEC-CDN2请求媒体内容时，用户设备的请求引流定向至 MEC-CDN2，之后MEC-CDN2将媒体分片推送给用户设备，以保证用户设备接收连续的媒体服务。
在步骤S4010中，用户从MEC-CDN2持续的接受媒体流，同时MEC-CDN1释放与该用户的链接资源。
根据本公开实施例提供的媒体服务在区域间的切换方法，用户设备首先和区域1中的MEC-CDN1建立连接，获取媒体服务。当用户准备从区域1移动到区域2时，MEC-CDN1从无线核心网中获取用户设备的移动信息，并预先和下一个MEC-CDN2进行通讯，将用户设备的状态信息迁移，MEC-CDN2预先缓存媒体数据；当没有与MEC-CDN1同样的媒体分片时，还可以预先从MEC-CDN1或源站获取。当用户设备移到区域2时，利用现有的会话信息和MEC-CDN2进行连接。其中，当MEC-CDN2被预先配置为与MEC-CDN1相同IP时，可以通过现有会话信息进行快速重连，并断开用户设备和区域1中MEC-CDN1的连接；对于移动性的用户设备可实现实时业务的快速切换，且通过预先缓存的媒体分片可减少用户设备请求的响应时间。
如图5所示，其为本公开实施例提供的媒体服务在区域间的切换方法的又一种流程示意图，该媒体服务在区域间的切换方法可包括步骤S501～步骤S5011。
在步骤S501中，用户设备连接到MEC-CDN1节点，接受本地的媒体流服务。
在步骤S502中，MEC-CDN1节点订阅无线核心网中AMF提供的用户移动事件通知服务。
在步骤S503中，当无线核心网的AMF获知到了用户设备的移动信息，将移动信息发给MEC-CDN1节点。
该移动信息可包括用户设备的位置变化信息，且AMF获知了用户设备的位置变化，且确定用户设备处于MEC-CDN1节点服务覆盖区域临界位置和/或MEC-CDN1节点与其他MEC-CDN节点的交叉覆盖区域时，将该移动信息发送给MEC-CDN1节点。
在步骤S504中，MEC-CDN1接收移动信息之后，确定用户设备的目的服务节点为MEC平台2，且MEC平台2反馈当前未启动MEC-CDN 节点功能。即MEC平台2上不存在MEC-CDN节点。
在步骤S505中，MEC-CDN1接收反馈信息之后，向MEC管理平台和/或MEC编排器发送业务请求，请求在MEC平台2上创建MEC-CDN2。
在步骤S506中，MEC-CDN1的MEC平台1和MEC平台2进行通讯，将用户设备在MEC-CDN1上的服务的状态信息和MEC-CDN1自身的CDN节点功能进行迁移。
可以理解的是，MEC-CDN可以为虚拟节点，运行在MEC平台上，MEC平台之间可通过标准定义的通信接口进行相互通信，如ETSI MEC平台之间的接口Mp3，之后MEC-CDN1将用户设备的状态信息迁移/复制到MEC-CDN2上。状态信息可包括但不限于用户名、媒体ID、媒体回源URL，和/或服务状态信息。此时用户媒体数据仍然由MEC-CDN1提供。进一步地，MEC-CDN1可以选择将自身的CDN节点功能和状态同步迁移/复制到MEC-CDN2上。
在步骤S507中，MEC-CDN2根据状态信息预先启动和媒体源的链接，缓存部分媒体分片，并对MEC-CDN2的服务状态信息进行修改。
根据本公开提供的实施例，由于状态信息可包括媒体ID，媒体回源URL等相关的媒体描述文件，MEC-CDN2可以预先与媒体源建立媒体数据通道，缓存部分媒体分片。同时MEC-CDN2将自身IP配置成与MEC-CDN1的IP相同，便于MEC-CDN2基于用户设备与MEC-CDN1的信令链接信息，与该用户设备建立连接。
在步骤S508中，当MEC-CDN2没有与MEC-CDN1相同的媒体分片时，向源站请求相同的媒体分片。
MEC-CDN2检测缓存的媒体分片的媒体源和媒体服务参数，确定没有与MEC-CDN1相同的媒体分片时，向源站请求相同的媒体分片。该相同的媒体分片可以指当前用户播放媒体相关的进度文件分片，源站可以是核心网的传统边缘节点。
在步骤S509中，当用户设备完全移动至MEC-CDN2的覆盖区域之后，持续请求媒体内容。
在步骤S5010中，MEC-CDN2与用户设备建立连接，并响应用户的请求，将之前缓存的分片推送给用户设备。
由于MEC-CDN2的IP被配置为与MEC-CDN1的IP相同，MEC-CDN2与用户设备可基于现有的信令链接信息快速建立连接。该信令链接信息可包括但不限于会话ID、认证信息，和/或当前媒体连接信息。
当MEC-CDN2请求媒体内容时，用户设备的请求引流定向至MEC-CDN2，之后MEC-CDN2将媒体分片推送给用户设备，以保证用户设备接收连续的媒体服务。
在步骤S5011中，用户从MEC-CDN2持续的接受媒体流，同时MEC-CDN1释放与该用户的链接资源。
根据本公开实施例提供的媒体服务在区域间的切换方法，用户设备首先和区域1中的MEC-CDN1建立连接，获取媒体服务。当用户准备从区域1移动到区域2时，MEC-CDN1从无线核心网中获取用户设备的移动信息，确定MEC-CDN平台2，且在该MEC-CDN平台2不存在MEC-CDN节点时，通过MEC-CDN管理平台创建MEC-CDN节点2(即，MEC-CDN2)，并预先和MEC-CDN2进行通讯，将用户设备的状态信息迁移；MEC-CDN2预先缓存媒体数据，当没有与MEC-CDN1同样的媒体分片时，还可以预先从MEC-CDN1或源站获取与MEC-CDN1同样的媒体分片。当用户设备移到区域2时，可利用现有的会话信息和MEC-CDN2进行连接。其中，当MEC-CDN2被预先配置为与MEC-CDN1具有相同IP时，可以通过现有会话信息进行快速重连，并断开用户设备和区域1中MEC-CDN1的连接；进而，对于移动性的用户设备可实现实时业务的快速切换，且通过预先缓存的媒体分片可减少用户设备请求的响应时间。
本公开实施例还提供一种MEC-CDN服务器，如图6所示，其为本公开实施例提供的MEC-CDN服务器的一种结构示意图。第一MEC-CDN服务器60可包括第一处理器601、第一存储器602以及第一通信总线603。第一通信总线603，可被配置为实现第一处理器601和第一存储器602之间的连接通信。第一处理器601，可被配置为执行第一存储器602中存储的一个或者多个程序，以实现上述的由第一MEC-CDN节点实现的媒体服务在区域间的切换方法的至少一个步骤。
本公开实施例还提供另一种第二MEC-CDN服务器，如图7所示， 其为本公开实施例提供的该另一种MEC-CDN服务器的一种结构示意图。第二MEC-CDN服务器70可包括第二处理器701、第二存储器702以及第二通信总线703。第二通信总线703，可被配置为实现第二处理器701和第二存储器702之间的连接通信。第二处理器701，可被配置为执行第二存储器702中存储的一个或者多个程序，以实现上述的由第二MEC-CDN节点实现的媒体服务在区域间的切换方法的至少一个步骤。
如图8所示，其为本公开实施例提供的MEC-CDN节点的一种功能架构示意图。该虚拟MEC-CDN节点的主要逻辑功能主要由运行在一台或者多台虚拟机器(Virtual Machine，VM)上的软件所组成。其中MEC-CDN节点可以进一步分成两个子系统，分别为基于MEC边缘服务器的业务管理子系统功能和媒体服务功能。业务管理子系统向5GC(进一步为5GC中的AMF模块)订阅用户移动信息，并根据这些信息对CDN媒体服务功能进行调整和配置。媒体服务功能为用户设备提供媒体服务；媒体服务功能可以是虚拟的，也可以是实体的节点，由业务管理子系统控制。
基于MEC-CDN的功能可主要包括但不限于：存储/缓存功能、流媒体服务功能、业务管理功能，和/或负载均衡功能。MEC-CDN的节点APP运行在MEC平台上，该平台也可部署其他应用。根据本公开提供的实施例，MEC平台针对CDN业务，则需要部署CDN业务注册能力，流量管理策略，和/或本地DNS(Local DNS，LDNS)等能力。还需要部署用户移动性事件订阅监测功能，具体向5GC中的AMF模块订阅，以及用户设备状态迁移功能。该MEC平台将用户请求的媒体链路引导到本地媒体服务MEC-CDN节点，为用户提供本地化的流媒体服务。
可以理解的是，图8中的MEC宿主机(MEC host)和MEC平台(MEC platform)是现有的技术，符合ETSI MEC规范的定义，且图8中的数据面通道/虚拟底层架构为现有MEC本身的能力，在此不再进行赘述。上述MEC-CDN服务器的硬件结构可以是MEC宿主机。
如图9所示，其为本公开实施例提供的CDN系统的一种结构示意图。该CDN系统可至少包括第一MEC-CDN服务器901、第二MEC-CDN 服务器902、核心网903，以及用户终端(或用户设备)904。应当理解的是，任一MEC-CDN服务器可包括MEC-CDN节点以及MEC-CDN节点依附的MEC平台。
第一MEC-CDN服务器901与第二MEC-CDN服务器902存在互通通道。
用户终端904与第一MEC-CDN服务器901建立连接，以获取媒体服务，且第一MEC-CDN服务器901从核心网903获取用户终端904的移动信息。
第一MEC-CDN服务器901根据移动信息确定用户终端904预移出第一MEC-CDN服务器901的覆盖范围时，确定第二MEC-CDN服务器902，并与第二MEC-CDN服务器902建立连接。
第一MEC-CDN服务器901将用户终端904的状态信息预先迁移在第二MEC-CDN服务器902上。
当用户终端904进入第二MEC-CDN服务器902的覆盖区域时，第二MEC-CDN服务器902与用户终端904建立连接，以使得用户终端904从第二MEC-CDN服务器902获取媒体服务。
本公开实施例提供的CDN系统可包括管理系统和分发系统。管理系统负责节点的状态管理，和/或配置等等。管理系统也可以额外生成一个5G AMF功能，还可以向MEC节点复制预先配置一些管理策略。分发系统可分为存储节点和GSLB系统。其中GSLB负责负载均衡，为用户设备选择最近的MEC-CDN节点进行服务。存储节点可包括传统接入节点(Point of Presence，POP)或者缓存(cache)节点，以及MEC-CDN节点。传统的POP节点根据现有的部署方式，将物理节点的边缘节点部署于核心网的边缘部分。而MEC-CDN节点则可以是虚拟化节点，由MEC服务器加载，部署于接入网络的边缘，例如，基站(Base Station，BS)或者基带处理单元(Base band Unite，BBU)。
本公开实施例还提供一种存储介质，该存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、计算机程序模块或其他数据)的任何方法或技术中实施的易失性或非易失性、可移除或不可移除的介质。存储介质包括但不限于RAM(Random Access Memory，随 机存取存储器),ROM(Read-Only Memory，只读存储器),EEPROM(Electrically Erasable Programmable read only memory，带电可擦可编程只读存储器)、闪存或其他存储器技术、CD-ROM(Compact Disc Read-Only Memory，光盘只读存储器)，数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。
本公开实施例提供的存储介质可被配置为存储一个或者多个计算机程序，其存储的一个或者多个计算机程序可被处理器执行，以实现上述媒体服务在区域间的切换方法的至少一个步骤。
可见，本领域的技术人员应该明白，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件(可以用计算装置可执行的计算机程序代码来实现)、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。
此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、计算机程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。所以，本公开不限制于任何特定的硬件和软件结合。
以上内容是结合具体的实施方式对本公开实施例所作的进一步详细说明，不能认定本公开的具体实施只局限于这些说明。对于本公开所属技术领域的普通技术人员来说，在不脱离本公开构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本公开的保护范围。

Claims (14)

  1. 一种媒体服务在区域间的切换方法，包括：
    第一移动边缘计算MEC-内容分发网络CDN节点从核心网获取用户设备的移动信息；其中，所述用户设备与所述第一MEC-CDN节点建立了连接，并从所述第一MEC-CDN节点获取媒体服务；
    响应于根据所述移动信息确定所述用户设备预移出所述第一MEC-CDN节点的覆盖范围，所述第一MEC-CDN节点确定第二MEC-CDN节点和/或所述第二MEC-CDN节点依附的第二MEC平台，并与所述第二MEC-CDN节点建立连接；
    所述第一MEC-CDN节点将所述用户设备的状态信息迁移至所述第二MEC-CDN节点上；以及
    响应于确定所述用户设备进入所述第二MEC-CDN节点的覆盖区域，所述第二MEC-CDN节点与所述用户设备建立连接，以使得所述用户设备从所述第二MEC-CDN节点获取所述媒体服务。
  2. 如权利要求1所述的媒体服务在区域间的切换方法，其中，所述第一MEC-CDN节点根据所述移动信息确定所述用户设备预移出所述第一MEC-CDN节点的覆盖范围，包括：
    响应于确定所述用户设备处于所述第一MEC-CDN节点服务覆盖区域的临界位置和/或所述第一MEC-CDN节点与其他节点交叉覆盖的区域，所述第一MEC-CDN节点确定所述用户设备预移出所述第一MEC-CDN节点的覆盖范围。
  3. 如权利要求1所述的媒体服务在区域间的切换方法，其中，确定所述第二MEC-CDN节点和/或所述第二MEC平台，包括：
    MEC管理平台根据所述用户设备的兴趣区域选择所述第二MEC-CDN节点和/或所述第二MEC平台，以及所述第一MEC-CDN节点从所述MEC管理平台获取所述第二MEC-CDN节点和/或所述第二MEC平台的信息；和/或
    所述第一MEC-CDN节点根据所述第一MEC-CDN节点所在的CDN节点管理平台配置的管理策略，确定所述第二MEC-CDN节点和/或所述第二MEC平台。
  4. 如权利要求3所述的媒体服务在区域间的切换方法，在所述第一MEC-CDN节点将所述用户设备的所述状态信息迁移至所述第二MEC-CDN节点上之前，还包括：
    响应于确定所述第二MEC平台上不存在所述第二MEC-CDN节点，所述第一MEC-CDN节点通过所述MEC管理平台和/或MEC编排器请求在所述第二MEC平台上创建所述第二MEC-CDN节点；以及
    所述第一MEC-CDN节点将自身的应用和状态迁移至所述第二MEC-CDN节点上。
  5. 如权利要求1所述的媒体服务在区域间的切换方法，其中，所述用户设备的所述状态信息包括：用户身份标识、媒体描述文件，或服务状态信息中的至少一个。
  6. 如权利要求5所述的媒体服务在区域间的切换方法，在所述第二MEC-CDN节点与所述用户设备建立连接之前，还包括：
    所述第二MEC-CDN节点根据所述用户设备的所述状态信息建立信令通道、媒体数据通道，和/或缓存媒体数据。
  7. 如权利要求6所述的媒体服务在区域间的切换方法，在所述第二MEC-CDN节点与所述用户设备建立连接之前，还包括：
    所述第二MEC-CDN节点和/或媒体服务功能单元被配置与所述第一MEC-CDN节点相同的互联网协议。
  8. 如权利要求7所述的媒体服务在区域间的切换方法，其中，所述第二MEC-CDN节点与所述用户设备建立连接，包括：
    所述第二MEC-CDN节点，基于所述用户设备与所述第一MEC-CDN节点的信令链接信息，与所述用户设备建立连接；
    其中，所述信令链接信息包括会话身份标识、认证信息，或当前媒体连接信息中的至少一个。
  9. 如权利要求1-8任一项所述的媒体服务在区域间的切换方法，在所述第二MEC-CDN节点与所述用户设备建立连接之前，还包括：
    响应于根据所述用户设备的所述状态信息确定所述第二MEC-CDN节点没有与所述第一MEC-CDN节点相同的媒体分片，所述第二MEC-CDN节点从所述第一MEC-CDN节点或媒体回源获取所述相同的 媒体分片。
  10. 如权利要求9所述的媒体服务在区域间的切换方法，还包括：
    响应于确定所述第一MEC-CDN节点向所述第二MEC-CDN节点迁移所述用户设备的所述状态信息的迁移时间大于预设时间阈值，所述第二MEC-CDN节点基于传输控制协议与所述用户设备建立连接。
  11. 一种第一MEC-CDN服务器，包括第一处理器、第一存储器，以及第一通信总线，其中：
    所述第一通信总线被配置为实现所述第一处理器和所述第一存储器之间的连接通信；以及
    所述第一处理器被配置为执行所述第一存储器中存储的一个或者多个第一程序，以实现如权利要求1至10中任一项所述的媒体服务在区域间的切换方法的由所述第一MEC-CDN节点实施的至少一个步骤。
  12. 一种第二MEC-CDN服务器，包括第二处理器、第二存储器，以及第二通信总线，其中：
    所述第二通信总线被配置为实现所述第二处理器和所述第二存储器之间的连接通信；以及
    所述第二处理器被配置为执行所述第二存储器中存储的一个或者多个第二程序，以实现如权利要求1至10中任一项所述的媒体服务在区域间的切换方法的由所述第二MEC-CDN节点实施的至少一个步骤。
  13. 一种内容分发网络CDN系统，包括第一移动边缘计算MEC-CDN服务器、第二MEC-CDN服务器、核心网，以及用户设备；其中：
    所述第一MEC-CDN服务器包括第一MEC-CDN节点以及所述第一MEC-CDN节点依附的第一MEC平台；
    所述第二MEC-CDN服务器包括第二MEC-CDN节点以及所述第二MEC-CDN节点依附的第二MEC平台；
    所述第一MEC-CDN服务器与所述第二MEC-CDN服务器存在互通 通道；
    所述第一MEC-CDN服务器从所述核心网获取所述用户设备的移动信息；其中，所述用户设备与所述第一MEC-CDN服务器建立了连接，并从所述第一MEC-CDN服务器获取媒体服务；
    响应于根据所述移动信息确定所述用户设备预移出所述第一MEC-CDN服务器的覆盖范围，所述第一MEC-CDN服务器确定所述第二MEC-CDN服务器，并与所述第二MEC-CDN服务器建立连接；
    所述第一MEC-CDN服务器将所述用户设备的状态信息迁移至所述第二MEC-CDN服务器上；以及
    响应于确定所述用户设备进入所述第二MEC-CDN服务器的覆盖区域，所述第二MEC-CDN服务器与所述用户设备建立连接，以使得所述用户设备从所述第二MEC-CDN服务器获取所述媒体服务。
  14. 一种存储介质，其上存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如权利要求1至10中任一项所述的媒体服务在区域间的切换方法的至少一个步骤。
PCT/CN2020/094069 2019-06-28 2020-06-03 媒体服务在区域间的切换方法、服务器、系统及存储介质 WO2020259234A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20833614.9A EP3979671A4 (en) 2019-06-28 2020-06-03 PROCEDURE FOR SWITCHING CROSS-AREA MEDIA SERVICE, SERVER, SYSTEM AND STORAGE MEDIUM
KR1020227000596A KR20220018034A (ko) 2019-06-28 2020-06-03 영역간 미디어 서비스의 전환 방법, 서버, 시스템 및 저장매체
US17/623,295 US20220368730A1 (en) 2019-06-28 2020-06-03 Inter-area media service switching method, server, system, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910574487.7A CN112153555B (zh) 2019-06-28 2019-06-28 媒体服务在区域间的切换方法、服务器、系统及存储介质
CN201910574487.7 2019-06-28

Publications (1)

Publication Number Publication Date
WO2020259234A1 true WO2020259234A1 (zh) 2020-12-30

Family

ID=73869211

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094069 WO2020259234A1 (zh) 2019-06-28 2020-06-03 媒体服务在区域间的切换方法、服务器、系统及存储介质

Country Status (5)

Country Link
US (1) US20220368730A1 (zh)
EP (1) EP3979671A4 (zh)
KR (1) KR20220018034A (zh)
CN (1) CN112153555B (zh)
WO (1) WO2020259234A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113507733A (zh) * 2021-06-18 2021-10-15 新华三技术有限公司 一种基于mec的用户切换方法、服务器和存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112751880A (zh) * 2021-01-06 2021-05-04 烽火通信科技股份有限公司 流服务异常控制方法、系统、设备及存储介质
CN112738548B (zh) * 2021-04-06 2021-06-18 北京百家视联科技有限公司 一种流媒体调度方法、装置、设备及存储介质
CN113726882B (zh) * 2021-08-30 2023-08-11 中国电信股份有限公司 基于5g网络的信息服务系统、方法及装置、设备、介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107305502A (zh) * 2016-04-21 2017-10-31 中兴通讯股份有限公司 一种应用实例迁移的方法及设备
CN108886679A (zh) * 2016-04-05 2018-11-23 华为技术有限公司 移动协同通信方法及装置
CN109151009A (zh) * 2018-08-09 2019-01-04 中国联合网络通信集团有限公司 一种基于mec的cdn节点分配方法和系统
CN109413194A (zh) * 2018-11-09 2019-03-01 中国电子科技集团公司第三十研究所 用于移动通信系统的用户信息云端协同处理及转移方法
US20190132767A1 (en) * 2017-10-27 2019-05-02 Futurewei Technologies, Inc. Method and apparatus for reducing network latency

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103718605A (zh) * 2012-07-20 2014-04-09 华为技术有限公司 一种确定切换小区的方法以及基站
EP3355615B1 (en) * 2015-10-21 2019-08-28 Huawei Technologies Co., Ltd. Mec platform handover
GB2547426A (en) * 2016-02-16 2017-08-23 Vodafone Ip Licensing Ltd Telecommunications network communication sessions
US9949133B2 (en) * 2016-08-05 2018-04-17 Nxgen Partners Ip, Llc Ultra-broadband virtualized telecom and internet
WO2018041337A1 (en) * 2016-08-30 2018-03-08 Sony Mobile Communications Inc. Relocation of mobile edge computing services
WO2019011408A1 (en) * 2017-07-10 2019-01-17 Nokia Solutions And Networks Oy MEC APPLICATION TRANSFER
CN108055680A (zh) * 2017-11-20 2018-05-18 华中科技大学 一种基于sdn的分布式epc网络快速切换方法
CN108337691A (zh) * 2018-01-19 2018-07-27 南京邮电大学 一种移动边缘面向用户移动的服务迁移方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108886679A (zh) * 2016-04-05 2018-11-23 华为技术有限公司 移动协同通信方法及装置
CN107305502A (zh) * 2016-04-21 2017-10-31 中兴通讯股份有限公司 一种应用实例迁移的方法及设备
US20190132767A1 (en) * 2017-10-27 2019-05-02 Futurewei Technologies, Inc. Method and apparatus for reducing network latency
CN109151009A (zh) * 2018-08-09 2019-01-04 中国联合网络通信集团有限公司 一种基于mec的cdn节点分配方法和系统
CN109413194A (zh) * 2018-11-09 2019-03-01 中国电子科技集团公司第三十研究所 用于移动通信系统的用户信息云端协同处理及转移方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Multi-access Edge Computing (MEC); Phase 2:Use Cases and Requirements", ETSI GS MEC 002 V2.1.1, 31 October 2018 (2018-10-31), pages 1 - 66, XP014329212 *
3GPP TSGSSA: "5G enhanced Mobile Broadband; Media Distribution (Release 15)", 3GPP TR 26.891 V0.5.0, 1 March 2018 (2018-03-01), pages 1 - 32, XP051450306 *
LV, HUAZHANG ET AL.: "CDN Subsidence Scheme for 5G MEC Edge Cloud", MOBILE COMMUNICATIONS, no. 1, 15 January 2019 (2019-01-15), pages 20 - 28, XP055771924 *
See also references of EP3979671A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113507733A (zh) * 2021-06-18 2021-10-15 新华三技术有限公司 一种基于mec的用户切换方法、服务器和存储介质
CN113507733B (zh) * 2021-06-18 2023-10-24 新华三技术有限公司 一种基于mec的用户切换方法、服务器和存储介质

Also Published As

Publication number Publication date
CN112153555B (zh) 2023-07-21
CN112153555A (zh) 2020-12-29
US20220368730A1 (en) 2022-11-17
KR20220018034A (ko) 2022-02-14
EP3979671A4 (en) 2023-06-21
EP3979671A1 (en) 2022-04-06

Similar Documents

Publication Publication Date Title
WO2020259234A1 (zh) 媒体服务在区域间的切换方法、服务器、系统及存储介质
US11470148B2 (en) Content delivery network
CN110769039B (zh) 资源调度方法及装置、电子设备和计算机可读存储介质
WO2021023018A1 (zh) 业务调度的方法及装置
KR101670521B1 (ko) 콘텐츠 중심 네트워크를 통한 세션 이전
US10764739B2 (en) Multicast handover for mobile communications
US10070348B2 (en) Hypertext transfer protocol support over hybrid access
EP3878156B1 (en) Methods and apparatuses for content delivery over mobile networks with multi-access edge computing (mec) control and user plane separation (cups)
CN113542058B (zh) 数据回源的方法、服务器及存储介质
CN107306279B (zh) 数据处理方法、内容分发网络节点和常驻网关
US9390053B2 (en) Cache device, cache control device, and methods for detecting handover
WO2021165416A1 (en) Method for delivering an audio and/or video content in a mobile network infrastructure
KR101356961B1 (ko) 컨텐츠 전송 시스템, 이를 위한 방법 및 장치
KR20140024553A (ko) 라이브 스트리밍 컨텐츠를 위한 컨텐츠 전송 서비스 방법, 및 이를 위한 장치
KR101441403B1 (ko) 컨텐츠 전송 서비스 시스템, 그의 장치 및 컨텐츠 전송 서비스 지원 방법
CN112153172B (zh) 回源地址配置方法、装置、计算机设备和可读介质
KR20130108228A (ko) 컨텐츠 전송 시스템, 이를 위한 방법 및 장치
EP2997489A1 (en) System for efficient mobile data distribution
US11729142B1 (en) System and method for on-demand edge platform computing
EP4254911A1 (en) Method for ensuring service continuity when delivering an audio and/or video content in a mobile network
US20240080792A1 (en) User equipment (ue) steering between network slices for service continuity
KR101589446B1 (ko) 컨텐츠 전송 서비스를 위한 트래픽 제어 방법 및 이를 구현한 프로그램을 기록한 컴퓨터 판독 가능한 기록 매체
CN116915595A (zh) 一种业务处理方法和系统

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: 20833614

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20227000596

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020833614

Country of ref document: EP

Effective date: 20211228