Method and apparatus for media session management for a service enabler architecture layer (SEAL) architecture

The SEAL architecture with a VAL server and media session management module addresses inefficient media session management in wireless communications by optimizing network resource allocation for vertical applications, enhancing session performance.

JP7586575B2Active Publication Date: 2024-11-19TENCENT AMERICA LLC
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2022568463
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-10-12
Filing Date
2021-10-14
Publication Date
2024-11-19
Estimated Expiration
2041-10-14

AI Technical Summary

Technical Problem

Existing wireless communication systems lack efficient methods for managing media sessions in vertical applications, particularly in environments with varying network resource demands, leading to suboptimal resource allocation and session management.

Method used

Implementing a Service Enabler Architecture Layer (SEAL) with a VAL server that includes a media session management module to process Session Description Protocol (SDP) information, enabling network resource requests and evaluations to establish or terminate media sessions based on available resources.

Benefits of technology

Enhances media session management by optimizing network resource allocation for vertical applications, ensuring efficient use of bandwidth and bit rates, thereby improving the performance of media sessions in wireless communications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007586575000002
    Figure 0007586575000002
  • Figure 0007586575000003
    Figure 0007586575000003
  • Figure 0007586575000004
    Figure 0007586575000004
Patent Text Reader

Abstract

Aspects of the present disclosure provide a method and vertical application layer (VAL) for media session management in wireless communications. The method includes obtaining Session Description Protocol (SDP) information in a Session Initiation Protocol (SIP) payload associated with a media session, and transmitting, by a processing circuit of a media session management module of a VAL server, a network resource request including the SDP information to a network resource management (NRM) server. The NRM server may be a service enabler architecture layer (SEAL) server. The network resource request may request a network resource. The method includes receiving, by the VAL server, a rating for the network resource request from the NRM server. The media session may be established or terminated based on the rating received at the media session management module of the VAL server.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 172,058, entitled "Method and Apparatus for Media Session Management for Service Enabler Architecture Layer (SEAL) Architecture," filed on October 12, 2021, which claims the benefit of priority to U.S. Provisional Application No. 63 / 172,058, entitled "Method and Apparatus of Supporting Session Description Protocol (SDP) Parameters for Media Session Management for 3GPP Service Enabler Architecture Layer (SEAL) Architecture," filed on April 7, 2021. The entire disclosure of the prior application is hereby incorporated by reference in its entirety.

[0002] This disclosure generally describes embodiments that relate to a service enabler layer for supporting vertical applications operating over wireless networks. [Background technology]

[0003] The background provided herein is intended to generally present the context of the present disclosure. The work of the present inventors is not admitted, expressly or impliedly, as prior art to the present disclosure to the extent that their work is described in this Background section, and aspects of the description that may not otherwise qualify as prior art at the time of filing.

[0004] Wireless communication systems are designed with advanced built-in features to support enterprise segments or vertical industries such as healthcare, automotive, smart factories, mission-critical communications, etc. Vertical application standards are developed to enable rapid deployment of vertical services based on the common services provided by wireless networks. A vertical domain can be an industry or a group of companies where similar products or services are produced. A vertical application provides a service or function that is useful in a particular vertical domain. Summary of the Invention

[0005] Aspects of the present disclosure provide a method and a vertical application layer (VAL) server for media session management in wireless communication. The VAL server may include a processing circuit. In one embodiment, the VAL server may include a media session management module including the processing circuit. Session Description Protocol (SDP) information in a Session Initiation Protocol (SIP) payload associated with the media session may be obtained. A network resource request including the SDP information may be sent to a network resource management (NRM) server by the processing circuit of the media session management module of the VAL server. The NRM server may be a service enabler architecture layer (SEAL) server. The network resource request may request a network resource. An evaluation for the network resource request may be received by the VAL server from the NRM server. A media session in the media session management module of the VAL server may be established or terminated based on the received evaluation.

[0006] The evaluation may include one of: (i) a denial of the network resource request; or (ii) a grant of the network resource request.

[0007] In one embodiment, the network resource request is evaluated by an NRM server to either grant the network resource request or deny the network resource request.

[0008] In one embodiment, in response to the grant of the network resource request, the requested network resources may be allocated by the NRM server, and the media session may be established based on the allocated network resources.

[0009] In one embodiment, in response to a denial of a network resource request by the NRM server, the media session may be terminated.

[0010] In one embodiment, the requested network resource is at least one of a network bandwidth requirement and a bit rate requirement.

[0011] In one embodiment, the media session is a SIP session.

[0012] In one embodiment, the evaluation is based on one of a maximum bandwidth allowed for the media session and a maximum bitrate allowed for the media session.

[0013] In one example, the network resource request further includes an identity of a VAL server and an identity of a VAL user equipment (UE).

[0014] Aspects of the present disclosure also provide a non-transitory computer-readable medium storing instructions that, when executed by a computer, cause the computer to perform a method for media session management in wireless communications. [Brief description of the drawings]

[0015] Further features, nature and various advantages of the disclosed subject matter will become more apparent from the following detailed description and the accompanying drawings.

[0016] [Figure 1] 1 illustrates a general on-network functionality model (100) according to one embodiment of the present disclosure. [Diagram 2] 2 illustrates an example workflow (200) for media session management, according to one embodiment of the present disclosure. [Diagram 3] 3 illustrates an example workflow (300) for media session management, according to one embodiment of the present disclosure. [Figure 4] 4 illustrates an example workflow (400) for media session management, according to one embodiment of the present disclosure. [Diagram 5] 5 illustrates an example workflow (500) for media session management, according to one embodiment of the present disclosure. [Figure 6] 6 shows a flow chart illustrating a process (600) according to one embodiment of the present disclosure. [Figure 7] FIG. 1 is a schematic diagram of a computer system according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] An embodiment of the present disclosure implements a service enabler layer to support vertical applications (or verticals). The service enabler layer may be referred to as a service enabler architecture layer (SEAL) in this disclosure. The SEAL may provide a common set of capabilities (or services) used by multiple verticals to facilitate the development and deployment of multiple vertical applications. For example, instead of developing auxiliary services specific to each vertical, commonly used auxiliary services may be captured in the SEAL and shared by multiple vertical applications. The use of all SEAL services by a vertical application is optional. A vertical application may decide to use any subset of services from the SEAL.

[0018] In some embodiments, the functional model for SEAL may be organized into a general SEAL service functional model and multiple specific SEAL service functional models. The general SEAL service functional model may be used as a reference model for the specific SEAL service functional models. The general functional model may include an on-network functional model and an off-network functional model. In various embodiments, the SEAL services provided to support the vertical application layers may include location management, group management, configuration management, identity management, key management, network resource management, etc.

[0019] FIG. 1 illustrates a general on-network functional model (100) according to one embodiment of the present disclosure. The model (100) may include four types of functional entities: a vertical application layer (VAL) client (111), a VAL server (121), a SEAL client (112), and a SEAL server (122). The number of each type of functional entity in the model (100) may be one or more. The VAL client and VAL server entities may belong to a VAL (101). The SEAL client and SEAL server entities may belong to a SEAL (102). The VAL client (111) and the SEAL client (112) may be included in a user equipment (UE) (110). The model (100) further includes a wireless network system (140), which is a Third Generation Partnership Project (3GPP) network system. These elements may be coupled to each other as shown in FIG. 1.

[0020] In the VAL (101), a VAL client (111) can communicate with a VAL server (121) via a VAL-UU reference point (134) that corresponds to a VAL-UU interface. In one example, the VAL-UU interface supports both unicast and multicast delivery modes.

[0021] The SEAL (102) can provide various services to the VAL (101). The SEAL client can communicate with the SEAL server via the SEAL-UU reference point (133), which corresponds to the SEAL-UU interface. The SEAL-UU interface can support both unicast and multicast delivery modes. The SEAL client can provide the service enabler layer support function to the VAL client via the SEAL-C reference point (131), which corresponds to the SEAL-C interface. The VAL server can communicate with the SEAL server via the SEAL-S reference point (which corresponds to the SEAL-S interface). The SEAL server (122) can communicate with the underlying wireless network system (e.g., 3GPP network system) (140) using the 3GPP interface (135) specified by the wireless network system (e.g., 3GPP network system) 140.

[0022] For a particular service (such as a location management service), a particular SEAL client and a particular SEAL server may form or belong to a particular on-network functional model together with a particular SEAL-UU reference point and a particular network interface of a wireless network system (e.g., a 3GPP network system).

[0023] In some embodiments, to support distributed SEAL server deployment, a SEAL server may interact with another SEAL server for the same SEAL service via a so-called SEAL-E reference point (not shown in FIG. 1). A SEAL server can interact with another SEAL server for service-to-service communication via a so-called SEAL-X reference point (not shown in FIG. 1). A SEAL server may interact with a VAL user database to store and retrieve user profiles via the VAL-UDB reference point.

[0024] In various embodiments, functional entities within a VAL system (e.g., including VAL 101 and SEAL 102) can provide application control and media-specific functions to support one or more VAL services. In the example of FIG. 1, a VAL client (111) (e.g., a vehicle-to-everything (V2X) client) can provide client-side functions corresponding to vertical applications (e.g., an unmanned aerial vehicle (UAV) client, a V2X client). The VAL client (111) can support vertical application interactions with a SEAL client (112). A VAL server (121) (e.g., a UAV server, a V2X server) can provide server-side functions corresponding to vertical applications.

[0025] In the example of FIG. 1, the SEAL client (112) can provide client-side functionality corresponding to a particular SEAL service (e.g., location management, network resource management, etc.). The SEAL client (112) can support interaction with the VAL client (111). The SEAL client can also support interaction with a corresponding SEAL client between two UEs. The SEAL server (122) can provide server-side functionality corresponding to a particular SEAL service. The SEAL server (122) can support interaction with the VAL server (121). The SEAL server can also support interaction with a corresponding SEAL server in a distributed SEAL deployment.

[0026] The functional entities in model 100 may be implemented in a variety of ways in different embodiments. For example, the functional entities may be implemented in a distributed or centralized manner. The functional entities may be implemented as software or as a combination of software and hardware.

[0027] In the example of Figure 1, a VAL user database (not shown) may contain information of user profiles associated with VAL services provided by the VAL service provider. Typically, each VAL service may have a corresponding user database, for example, a Mission Critical Push-to-Talk (MCPTT) user database, a Mission Critical Video (MCVideo) user database, and a Mission Critical Data (MCData) user database.

[0028] In some embodiments, commands related to the VAL (101) support functions between the VAL client (111) and the VAL server (121) are supported by a VAL-UU reference point (134). In one example, the VAL-UU reference point (134) is an instance of the Uu reference point as described in 3GPP TS 23.401 and 3GPP TS 23.501. In some embodiments, interactions related to the VAL support functions between the VAL clients of the two UEs may be supported by a VAL-PC5 reference point (not shown). For example, the VAL-PC5 reference point may be an instance of the PC5 reference point as described in 3GPP TS 23.303 and 3GPP TS 23.303.

[0029] In some implementations, interactions between a SEAL client (112) and a corresponding SEAL server (122) are supported by a SEAL-UU reference point (133). A particular SEAL service reference point corresponding to a SEAL-UU (133) may be specified in a particular SEAL service functional model. In some implementations, interactions between SEAL clients of two VALUEs may be supported by a SEAL-PC5 reference point (not shown). A particular SEAL-PC5 service reference point corresponding to a SEAL-PC5 may be specified in a particular SEAL service functional model.

[0030] In some embodiments, interactions between SEAL clients (111) and SEAL servers (112) within a VALUE (110) are supported by SEAL-C reference points (131). A particular SEAL service reference point that corresponds to SEAL-C (131) may be identified in a particular SEAL service functional model.

[0031] In some embodiments, the interaction between the VAL server (121) and the SEAL server (122) is supported by the SEAL-S reference point (132). A particular SEAL service reference point corresponding to the SEAL-S (132) may be identified in a particular SEAL service functional model.

[0032] In some embodiments, interactions between SEAL servers of the same type (e.g., offering the same type of SEAL service) are supported by SEAL-E reference points (not shown). Specific SEAL service reference points that correspond to SEAL-E are identified in specific SEAL service functional models.

[0033] In some embodiments, interactions between different types of SEAL servers may be supported by SEAL-X reference points. Examples of specific reference points that correspond to SEAL-X reference points may include reference point SEAL-X1 between a key management server and a group management server, and reference point SEAL-X2 between a group management server and a location management server.

[0034] The reference point VAL-UDB exists between the VAL user database and the SEAL server. The reference point VAL-USB can be used to store user profile data in a specific VAL user database and retrieve user profiles from a specific VAL user database for further configuration in the UE.

[0035] In various embodiments, different identities may be configured and used in a VAL system developed based on the model (100). In some embodiments, a VAL user may present a user identity (user ID) to an identity management server in the SEAL (102) during a user authentication transaction to provide the identity management client with a means for VAL service authentication. In general, since identity management is a common SEAL service, the identity management server uses a set of credentials (e.g., biometrics, secureID, username / password) that are not necessarily tied to a single VAL service. The user credentials uniquely identify the VAL user to the identity management server. As an example, 3GPP TS 33.434 specifies the security and authentication mechanisms required to use a user ID.

[0036] In some embodiments, the VAL User ID is a unique identifier within the VAL service that represents a VAL user. For example, the VAL User ID may be a unique resource identifier (URI). The VAL User ID is used for authentication and authorization purposes to provide VAL services to the VAL user via the VAL UE. The VAL User ID also indicates the VAL service provider with which the VAL user has a VAL service contract. The VAL user may have a VAL service contract with a VAL service provider and therefore has a unique VAL User ID for each VAL service provider. The VAL User ID may be used to access the SEAL service.

[0037] In some embodiments, the VAL UE ID is a unique identifier within the VAL service that represents the VAL UE. For example, the VAL UE ID for a V2X service is mapped to a Station ID as specified in ETSI TS 102 894-2. The VAL UE ID is used to address the VAL UE for transmitting VAL messages.

[0038] In some embodiments, the VAL Service ID is a unique identifier representing a VAL Service. The VAL Server provides a list of VAL Services to a VAL User or VAL UE. Each VAL Service is uniquely identified by a VAL Service ID, which is an identifier of the VAL Application providing the VAL Service. The VAL Service ID may be used for policy mapping, QoS handling for VAL communication, and VAL message delivery. For example, the identifier of a V2X Service, ITS-AID or PSID specified in ETSI TS 102 965 and ISO TS 17419, may be used as the V2X Service ID.

[0039] In some embodiments, the VAL Group ID is a unique identifier within the VAL Service that represents a set of VAL Users or VAL UEs according to the VAL Service. The set of VAL Users may belong to the same or different VAL Service Providers. The VAL Group ID indicates the VAL Application Server in which the group is defined.

[0040] In some embodiments, the VAL System ID is a globally unique identifier that represents the VAL system. In some embodiments, the VAL Stream ID is an identity used by the VAL Server to identify a VAL Stream.

[0041] In various embodiments, the SEAL architecture as described above can support deployments where SEAL services are deployed within and / or outside of public land mobile network (PLMN) networks. The SEAL architecture can also support centralized and distributed deployments of vertical applications. Mobile network operators (MNOs) can leverage the appropriate deployment model as appropriate and needed for their business.

[0042] The deployment model may involve multiple entities such as VAL users, VAL service providers, SEAL providers, and PLMN operators. As an example, in a possible deployment model, a SEAL server may be deployed in a PLMN operator domain and a vertical application server may be deployed in a VAL service provider domain. A SEAL server may also use a SEAL-E interface to interact with another SEAL server of the same SEAL service that is deployed in a different PLMN operator domain.

[0043] There may be multiple business relationships between the entities involved in the deployment. Based on the service specific contract, the VAL user belongs to the VAL service provider domain. The VAL service provider and the home PLMN operator may belong to the same organization. The VAL service provider may have a service contract with the SEAL service provider. Also, the VAL service provider, the SEAL service provider, and the home PLMN operator may belong to the same organization. If the VAL service provider and the home PLMN operator do not belong to the same organization, they may have a service contract.

[0044] Referring to Figure 1, the SEAL architecture can provide network resource management. More specifically, the SEAL client (112) is a network resource management (NRM) client (112). The SEAL server (122) is an NRM server (122). The NRM client (112) functional entity can act as a VAL client (111) for management of network resources. The NRM client (112) can interact with the NRM server (122).

[0045] The NRM server (122) functional entity can provide management of network resources (eg, unicast, multicast) of a wireless network system (eg, a 3GPP network system) (140) to support the VAL client (111).

[0046] Interactions related to network resource management functions between the NRM client (112) and the NRM server (122) may be supported by the SEAL-UU reference point (133) (also referred to as the NRM-UU reference point). Interactions related to network resource management functions between the VAL server (121) and the NRM server (122) may be supported by the SEAL-S reference point (132) (also referred to as the NRM-S reference point).

[0047] In some embodiments, interaction between the VAL client (111) and the NRM client (112) within the VAL UE (110) is supported by a SEAL-C reference point (131) (also referred to as the NRM-C reference point).

[0048] In various real-time media communications, a combination of Session Initiation Protocol (SIP) and Session Description Protocol (SDP) may be used for session initialization and media parameter negotiation. Both protocol data may be carried in the control plane before the actual media traffic traverses a network such as a wireless network system (140) (e.g., a 3GPP network system). SDP may be carried as a SIP payload that may include media codec-related parameters (e.g., all media codec-related parameters). SDP carries information about the media streams and may be used, for example, in a unicast scenario, to provide sufficient information to enable joining and participating in a media session.

[0049] In one embodiment, the key information carried in the SDP is the potential bandwidth usage for a particular media stream. In one example, for a payload, such as a UAV media-related payload, knowledge of the bandwidth that the payload (e.g., a UAV media-related payload) is going to use is important for resource allocation in a network, such as a wireless network system (140) (e.g., a 3GPP network system).

[0050] SEAL can support SIP for session establishment. According to one embodiment of the present disclosure, SDP data points can be added to address monitoring and management of unicast media sessions.

[0051] For media session management, the SDP in the SIP package can carry important information about media parameters, as shown below. v=0 o=Client1 2398026505 2307593197 IN IP4 100.200.130.140 s=Client1 Audio Session b=AS:64 b=RS:800 b=RR:2400 c=IN IP4 10.11.12.13 t=0 0 m=audio 15010 RTP / AVP 0 101 a=rtpmap:0 PCMU / 8000 a=rtpmap:101 telephone-event / 8000 a=sendrecv

[0052] The above SDP information is sent from the VAL server (121) to the NRM server (122) via the NRM-S reference point (132).

[0053] A parameter included in the SDP is bandwidth information, which may indicate a maximum bandwidth that may limit the successful establishment of a media session.

[0054] In one example, B=AS:bitrate may indicate the maximum bitrate allowed in the media session. In one example, B=as:64 indicates that a maximum bitrate of 64 kb / s is allowed in the media session.

[0055] FIG. 2 illustrates an exemplary workflow (or procedure) (200) for media session management, according to one embodiment of the present disclosure. In one example, FIG. 2 illustrates resource requests during VAL service communication establishment. The workflow (200) may be implemented by a VAL Server (221), an NRM Server (222), a SIP Core (223), and a network system (240). In one embodiment, the resources (or network resources) requested in the workflow (200) may include unicast resources, and the workflow (200) may be for unicast resource management with the SIP Core (223).

[0056] The workflow (200) can specify how network resources are requested in a VAL service communication establishment. In one example, if concurrent sessions are used, the NRM server (222) may utilize the specified resource sharing capabilities for the underlying network policy and charging functions. The request for resources can include application type, bandwidth, priority, application identifier, resource sharing information, etc. In one example, the requested network resource includes bandwidth (e.g., maximum bandwidth for an application).

[0057] The workflow 200 may be suitably adapted and applied to any suitable type of session establishment that employs requests for network resources. In one example, Figure 2 illustrates a signaling procedure for requesting resources in a session establishment.

[0058] In one example, the pre-condition is met if, before step (S241), a VAL client requests a VAL service communication with the VAL server (221).

[0059] In (S241), the VAL server (221) can send a request for resources (also called a network resource request) to the NRM server (222) to request network resources such as bandwidth for an application. The VAL server (221) can be any suitable server for a vertical application. The VAL server (221) can be an unmanned vehicle (UAV) server for a UAV application, a V2X server for a V2X application, etc.

[0060] At (S242), the NRM server (222) can evaluate the need for network resources. In one example, the NRM server (222) further evaluates the use of resource sharing.

[0061] At (S243), the NRM Server (222) may send a session progress request including a request for resources to the SIP Core (223).

[0062] The SIP Core (223) may include many sub-entities responsible for registration, service selection, and routing within the signaling control plane. In one example, the SIP Core (223) is a 3GPP IP Multimedia Core Network Subsystem.

[0063] Data related to the functionality of the SIP Core (223), such as data for application service selection, service register identities, authentication related information, etc., may be provided by the PLMN operator in charge of the bearer plane. The source of the data, the SIP database, may therefore be part of the Home Subscriber Server (HSS). Alternatively, the data may be provided by a VAL service provider and the source of the data may be the VAL service provider's SIP database.

[0064] The SIP core local inbound / outbound proxy functional entity can act as both an inbound proxy and an outbound proxy for SIP transactions. The SIP core local inbound / outbound proxy functional entity can provide one or more of the following functions: NAT traversal, resource control, route / forward requests and responses to user agents, SIP signaling security, PLMN operator policy dependency, discovery, and address resolution.

[0065] At (S244), the PCC procedure can be initiated from the local inbound / outbound proxy (223) of the SIP core.

[0066] At (S245), the SIP core local inbound / outbound proxy (223) can send an OK message to the NRM server (222).

[0067] At (S246), the NRM server (222) can send a resource response to the VAL server (221).

[0068] At (S247), the VAL service communication may be established, for example, using a unicast bearer based on the allocated resources.

[0069] The VAL server (221) may be similar or identical to the VAL server (121), the NRM server (222) may be similar or identical to the NRM server (122), and the network system (240) may be similar or identical to the network system (140) as described with reference to Fig. 1. In one example, the network system (240) is a 3GPP network. Therefore, a detailed description of the VAL server (221) and the NRM server (222) is omitted for the sake of brevity.

[0070] The workflow 200 may be adapted as desired. Steps in the workflow 200 may be modified and / or omitted. Additional steps may be added. Any suitable order of implementation may be used.

[0071] The use of SDP for session negotiation (e.g., common usage of SDP) can occur in unicast scenarios, multicast scenarios, etc. In one embodiment, the VAL media service uses SDP information in unicast and multicast scenarios. In some examples, SDP used by unicast traffic can be more frequent than multicast in a network deployment. In some examples, the NRM server does not have the option for the VAL server to pass SDP information to the NRM server for unicast traffic. According to one embodiment of the present disclosure, SDP information can be added to the information flow from the VAL server to the NRM-S or NRM server. In some examples, a media session established (or initiated) by a VAL client with SDP is not properly addressed without adding SDP information to the information flow.

[0072] According to one embodiment of the present disclosure, the resource request (or network resource request) may support unicast SDP / SIP session establishment and include SDP information, as described in Table 1 below.

[0073] Table 1 describes the information flow of a resource request from a VAL server (eg, VAL server (121) or (221)) to an NRM server (eg, NRM server (222)) for a unicast resource. [Table 1]

[0074] As shown in Table 1, the resource request may include multiple information elements including a requester identity, a VAL user identifier (ID) or VAL UE ID, VAL service requirement information, SDP information, etc. The requester identity may describe the identity of the VAL server performing the request (or resource request). The VAL user ID or VAL UE ID may describe the identity of the VAL user or VAL UE. The VAL service requirement information may describe the VAL service requirements for unicast resources (e.g., VAL service ID, bit rate). The SDP information may describe an SDP with media and application control information (e.g., codec, bandwidth, protocol ID, forward error correction (FEC) information) applicable to the group that can use the bearer. In one example, the requester identity and the VAL user ID are mandatory in the mandatory ("M") state, and the VAL service requirement information and the SDP information are optional in the optional ("O") state. When the VAL service requirement information is not included, the NRM server may consider the default VAL service requirements for unicast resources.

[0075] FIG. 3 illustrates an exemplary workflow (or procedure) (300) for media session management, according to one embodiment of the present disclosure. In one example, FIG. 3 illustrates resource requests in VAL service communication establishment. The workflow (300) may be implemented by a VAL Server (221), an NRM Server (222), and a SIP Core (223). In one embodiment, the resources (or network resources) requested in the workflow (300) may include unicast resources, and the workflow (300) may be for unicast resource management with the SIP Core (223).

[0076] The workflow (300) can specify how network resources are requested in a VAL service communication establishment. The request for resources can include application type, bandwidth, priority, application identifier, resource sharing information, etc. In one example, the requested network resource includes bandwidth (e.g., maximum bandwidth for an application).

[0077] The workflow (300) may be suitably adapted and applied to any suitable type of session establishment that employs requests for network resources. In one example, Figure 3 illustrates a signaling procedure for requesting resources in session establishment or session initialization.

[0078] At (S310), the VAL server (221) (e.g., processing circuitry of the VAL server (221)) can send a request for resources (also referred to as a network resource request) to the NRM server (222) to request network resources such as bandwidth for an application (e.g., a UAV application, a V2X application). The VAL server (221) can be any suitable server for the vertical application. The VAL server (221) can be an unmanned vehicle (UAV) server for a UAV application, a V2X server for a V2X application, etc. In one example, the request can include SDP information (e.g., network bandwidth requirements or bandwidth), as described in Table 1.

[0079] After receiving the network resource request, the NRM server (222) can evaluate the need for network resources as described in (S242).

[0080] At (S320), the network resource request may be rejected by the NRM server (222). A rejection of the network resource request may be sent from the NRM server (222) to the VAL server (221).

[0081] At (S330), in response to rejecting the network resource request, the media session (eg, a SIP media session or a SIP session) may be terminated.

[0082] The workflow (300) illustrates an example of how a VAL server (221) (e.g., a UAE server) may request an NRM server (222) to fulfill a session establishment request. In one example, a pre-condition is met if, prior to step (S310), a VAL client requests a VAL service communication with the VAL server (221). For example, the UAV attempts to establish a media session (e.g., a SIP session) between the UAV media payload and the UAV-C or USS / UTM using the 3GPP core network via the UAV server indicating resource requirements for the media session using SIP and SDP.

[0083] The workflow 300 may be adapted as desired. Steps in the workflow 300 may be modified and / or omitted. Additional steps may be added. Any suitable order of implementation may be used.

[0084] FIG. 4 illustrates an exemplary workflow (or procedure) (400) for media session management, according to one embodiment of the present disclosure. In one example, FIG. 4 illustrates resource requests in VAL service communication establishment. The workflow (400) may be implemented by a VAL Server (221), an NRM Server (222), and a SIP Core (223). In one embodiment, the resources (or network resources) requested in the workflow (400) may include unicast resources, and the workflow (400) may be for unicast resource management with the SIP Core (223).

[0085] The workflow (400) can specify how network resources are requested during VAL service communication establishment. The request for resources can include application type, bandwidth, priority, application identifier, resource sharing information, etc. In one example, the requested network resource includes bandwidth (e.g., maximum bandwidth for the application).

[0086] The workflow (400) may be suitably adapted and applied to any suitable type of session establishment that employs requests for network resources. In one example, Figure 4 illustrates a signaling procedure for requesting resources in session establishment or session initialization.

[0087] At (S410), the VAL server (221) (e.g., processing circuitry of the VAL server (221)) can send a request for resources (also referred to as a network resource request) to the NRM server (222) to request network resources such as bandwidth for an application (e.g., UAV application, V2X application). The VAL server (221) can be any suitable server for the vertical application. The VAL server (221) can be an unmanned vehicle (UAV) server for a UAV application, a V2X server for a V2X application, etc. In one example, the request can include SDP information (e.g., network bandwidth requirements or bandwidth), as described in Table 1.

[0088] After receiving the network resource request, the NRM server (222) can evaluate the need for network resources as described in (S242).

[0089] At (S420), the network resource request may be granted by the NRM server (222). A grant for the network resource request may be sent from the NRM server (222) to the VAL server (221). The requested network resources may be allocated.

[0090] At (S430), in response to the grant of the network resource request, a media session (eg, a SIP media session or a SIP session) may be established, for example to initiate unicast data traffic between the UE (224) and the SIP Core (223).

[0091] The workflow (400) illustrates an example of how a VAL server (221) (e.g., a UAE server) requests the NRM server (222) to fulfill a session establishment request. In one example, a pre-condition is met if, prior to step (S410), a VAL client requests a VAL service communication with the VAL server (221). For example, the UAV attempts to establish a media session (e.g., a SIP session) between the UAV media payload and the UAV-C or USS / UTM using the 3GPP core network via the UAV server indicating resource requirements for the media session using SIP and SDP.

[0092] The workflow 400 may be adapted as desired. Steps in the workflow 400 may be modified and / or omitted. Additional steps may be added. Any suitable order of implementation may be used.

[0093] The workflows (300) and (400) described with reference to Figures 3-4 may be adapted or combined in any suitable order or in any suitable manner. For example, steps of workflow (300) may be adapted and / or steps of workflow (400) may be adapted. (i) One or more steps adapted or original from workflow (300) and (ii) One or more steps adapted or original from workflow (400) may be combined. An example of such a combination is shown in Figure 5.

[0094] FIG. 5 illustrates an exemplary workflow (or procedure) (500) for media session management, according to one embodiment of the present disclosure. In one example, FIG. 5 is used to request resources during VAL service communication establishment. The workflow (500) may be implemented by the VAL Server (221), the NRM Server (222) and the SIP Core (223). In one embodiment, the resources (or network resources) requested in the workflow (500) may include unicast resources, and the workflow (500) may be for unicast resource management with the SIP Core (223).

[0095] The workflow (500) can specify how network resources are requested in a VAL service communication establishment. The request for resources can include application type, bandwidth, priority, application identifier, resource sharing information, etc. In one example, the requested network resource includes bandwidth (e.g., maximum bandwidth for an application).

[0096] The workflow (500) may be suitably adapted and applied to any suitable type of session establishment that employs requests for network resources. In one example, Figure 5 illustrates a signaling procedure for requesting resources in session establishment or session initialization.

[0097] In (S510), the VAL server (221) (e.g., a processing circuit of the VAL server (221)) can send a request for network resources (also referred to as a network resource request) to the NRM server (222) to request network resources such as bandwidth for an application (e.g., a UAV application, a V2X application). The network resources may also be referred to as session resources.

[0098] The VAL server (221) can be any suitable server for the vertical application. The VAL server (221) can be an unmanned vehicle (UAV) server for UAV applications, a V2X server for V2X applications, etc. In one example, the VAL server (221) (e.g., a UAV server) requests the initialization of a media session using an SDP in a SIP payload. The network resource request can be referred to as a SIP session request.

[0099] At (S510), after receiving the network resource request, the NRM server (222) may evaluate the network resource request, such as the need for network resources, as described at (S242). The evaluation may include a decision to grant or reject the network resource request. In one embodiment, the network resource request is determined to be rejected, as shown in FIG. 3. In one embodiment, the network resource request is determined to be granted, as shown in FIG. 4. In one example, the NRM server (222) evaluates the network resource request as specified in section 14.3.3.2 of 3GPP TS 23.434. In one example, the request may include SDP information (e.g., network bandwidth requirement or bandwidth), as described in Table 1.

[0100] At (S520), a media session may be initiated and / or terminated based on the results of the evaluation at (S510).

[0101] The NRM server (222) may choose to reject the SIP session request due to lack of available network resources. If it is determined that the network resource request is rejected in (S510), for example, a message may be sent from the NRM server (222) to the VAL server (221) indicating the rejection of the network resource request. Thus, the media session (e.g., SIP media session or SIP session) is terminated, as described with reference to FIG. 3.

[0102] The NRM server (222) can determine that network resources can be granted from the SIP core, for example by using section 14.3.3.2 of 3GPP TS 23.434. If it is determined that the network resource request is granted in (S510), for example, a message indicating the grant of the network resource request can be sent from the NRM server (222) to the VAL server (221). The requested network resources can be allocated. Thus, a media session (e.g., a SIP media session or a SIP session) can be established or initialized in a manner similar to that described with reference to FIG. 4.

[0103] The workflow (500) illustrates an example of how a VAL server (221) (e.g., a UAE server) requests the NRM server (222) to fulfill a session establishment request. In one example, a pre-condition is met if a VAL client requests a VAL service communication with the VAL server (221) before step (S510). For example, in the case of a UAV application, the UAV attempts to establish a media session (e.g., a SIP session) between the UAV media payload and the UAV-C or USS / UTM using the 3GPP core network via the UAV server indicating resource requirements for the media session using SIP and SDP.

[0104] As shown in Figure 5, if an NRM server (e.g., NRM server (222)) determines that there are not enough network resources (e.g., network bandwidth) for a particular SDP description, the media session (e.g., SIP session) may be immediately terminated. Otherwise, if an NRM server (e.g., NRM server (222)) determines that there are sufficient network resources (e.g., network bandwidth) for a particular SDP description and the requested network resources (e.g., network bandwidth) are allocated, the media session (e.g., SIP session) may be established.

[0105] The workflow 500 may be adapted as desired. Steps in the workflow 500 may be modified and / or omitted. Additional steps may be added. Any suitable order of implementation may be used.

[0106] FIG. 6 shows a flowchart illustrating a process (600) according to one embodiment of the present disclosure. The process (600) may be performed by a processing circuit of a VAL server (e.g., the VAL server (121), the VAL server (221)). In one embodiment, the process (600) is performed by a processing circuit of a media session management module of a VAL server (e.g., the VAL server (121), the VAL server (221)). The process (600) may be performed for media session management, such as initializing and establishing a media session, in wireless communication. In one example, the media session is a SIP session. The process (600) may start at (S601) and proceed to (S610).

[0107] At (S610), Session Description Protocol (SDP) information in a Session Initiation Protocol (SIP) payload associated with the media session may be obtained.

[0108] At (S620), the network resource request including the SDP information may be sent to an NRM server (e.g., NRM server (222)) by, for example, a processing circuit of a media session management module of a VAL server (e.g., VAL server (121), VAL server (221)). The NRM server may be a SEAL server (e.g., SEAL server (122)). The network resource request may request a network resource. In one embodiment, the requested network resource may include a unicast resource, and the process (600) may be for unicast resource management. The requested network resource may include an application type, a bandwidth requirement, a bit rate requirement, a priority, an application identifier, resource sharing information, and the like. In one example, the requested network resource may include a network bandwidth requirement. In one example, the requested network resource may include a bit rate requirement. In one example, the requested network resource is at least one of a network bandwidth requirement and a bit rate requirement. The network bandwidth requirement may indicate a bandwidth (e.g., a maximum bandwidth for an application).

[0109] In one embodiment, the network resource request may be sent using SDP in a SIP payload. In one example, the network resource request includes SDP information (e.g., network bandwidth requirements), as described in Table 1.

[0110] In one example, the network resource request includes the identity of a VAL server, the identity of a VAL user equipment (UE), and SDP information.

[0111] At (S630), an evaluation for the network resource request may be received from the NRM server, for example by a processing circuit of the VAL server. The evaluation may include one of: (i) a denial of the network resource request, or (ii) a grant of the network resource request.

[0112] In one embodiment, the network resource request is evaluated by the NRM server to grant the network resource request or to deny the network resource request. After receiving the network resource request, the NRM server (222) can evaluate the network resource request, such as the need for the network resource, as described in (S242). The evaluation can include a decision to grant or deny the network resource request. In one embodiment, the network resource request is determined to be denied, as shown in FIG. 3. In one embodiment, the network resource request is determined to be granted, as shown in FIG. 4. In one example, the NRM server evaluates the network resource request as specified in 3GPP TS 23.434, section 14.3.3.2.

[0113] A network resource request may be denied or granted, for example, by an NRM server based on the availability of network resources. A media session (eg, a SIP session) may be determined to be denied or granted based on the availability of network resources.

[0114] In one embodiment, the evaluation is based on one of a maximum bandwidth allowed for the media session and a maximum bitrate allowed for the media session.

[0115] At (S640), a media session may be established or terminated based on the received rating in a media session management module of the VAL server.

[0116] In one embodiment, in response to the grant of the network resource request, the requested network resources may be allocated, for example, by an NRM server, and a media session may be established based on the allocated network resources.

[0117] In one embodiment, in response to a denial of a network resource request, the media session may be terminated.

[0118] The process (600) can proceed to (S699) and end.

[0119] The process 600 may be adapted as desired. Steps of the workflow 600 may be modified and / or omitted. Additional steps may be added. Any suitable order of implementation may be used.

[0120] The embodiments of the present disclosure may be used separately or in combination in any order. Furthermore, each method (or embodiment) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program stored on a non-transitory computer-readable medium.

[0121] For example, including SDP information in a resource request may be combined with any of the embodiments described with reference to FIGS. The embodiments described in Table 1 may be used in any suitable media session management procedure, for session establishment (or session initialization), session modification, and the like.

[0122] The techniques described above may be implemented as computer software using computer readable instructions and physically stored on one or more computer readable mediums. The computer software may be coded using any suitable machine code or computer language that may be subject to assembly, compilation, linking, or similar mechanisms to produce code including instructions that are executable by one or more computer central processing units (CPUs), graphics processing units (GPUs), etc., directly, or through interpretation, microcode execution, etc.

[0123] The instructions may be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smart phones, gaming devices, Internet of Things devices, and the like.

[0124] Figure 7 illustrates a computer system (700) suitable for implementing certain embodiments of the disclosed subject matter. The components illustrated in Figure 7 for the computer system (700) are exemplary in nature and are not intended to suggest any limitation as to the scope of use or functionality of the computer software implementing the embodiments of the present disclosure. The arrangement of components should not be construed as having any dependency or requirement regarding any one or combination of components illustrated in the exemplary embodiment of the computer system (700).

[0125] The computer system (700) may include certain human interface input devices. Such human interface input devices may be responsive to input by one or more human users, for example, through tactile input (e.g., keystrokes, swipes, data glove movements), audio input (e.g., voice, clapping), visual input (e.g., gestures), olfactory input (not depicted). Human interface devices may also be used to capture certain media that are not necessarily directly related to conscious human input, such as audio (e.g., speech, music, ambient sounds), images (e.g., scanned images, photographic images obtained from still image cameras), and video (e.g., two-dimensional video, three-dimensional video including stereoscopic images).

[0126] The input human interface devices may include one or more (only one of each is depicted) of a keyboard (701), a mouse (702), a trackpad (703), a touch screen (710), a data glove (not shown), a joystick (705), a microphone (706), a scanner (707), and a camera (708).

[0127] The computer system (700) may also include certain human interface output devices. Such human interface output devices may stimulate one or more of the senses of a human user, for example, through haptic output, sound, light, and smell / taste. Such human interface output devices may include haptic output devices (e.g., a touch screen (710), data gloves (not shown), or a haptic feedback device that does not function as an input device, but is a haptic feedback device via a joystick (705), audio output devices (e.g., speakers (709), headphones (not depicted)), visual output devices (e.g., screens (710), including cathode ray tube (CRT) screens, LCD screens, plasma screens, OLED screens, each with or without haptic screen input capabilities, some of which may be capable of outputting two-dimensional visual output or even three-dimensional output through means such as stereoscopic output, virtual reality glasses (not depicted), holographic displays, smoke tanks (not depicted)), and printers (not depicted).

[0128] The computer system (700) may also include human-accessible storage devices, such as optical media, including CD / DVD ROM / RW (720) with CD / DVD or similar media (721), thumb drives (722), removable hard drives or solid state drives (723), legacy magnetic media such as tapes and floppy disks (not depicted), specialized ROM / ASIC / PLD based devices such as security dongles (not depicted), and their associated media.

[0129] Those skilled in the art should also understand that the term "computer-readable medium" as used in connection with the subject matter of this disclosure does not encompass transmission media, carrier waves, or other transitory signals.

[0130] The computer system (700) may also include an interface (754) to one or more communication networks (755). The networks may be, for example, wireless, wired, or optical. The networks may further be local, wide area, metropolitan, vehicular and industrial, real-time, delay tolerant, and the like. Examples of networks include Ethernet, WLAN, GSM, cellular networks including 3G, 4G, 5G, LTE, and the like, TV wired and wireless wide area digital networks including cable TV, satellite TV, and terrestrial broadcast TV, vehicular and industrial including CANBus, and the like. Certain networks typically require an external network interface adapter that is attached to a specific general-purpose data port or peripheral bus (749) (e.g., a USB port on the computer system (700)), while others are typically built into the core of the computer system (700) by attachment to a system bus (e.g., an Ethernet interface to a PC computer system or a cellular network interface to a smartphone computer system), as described below. Using any of these networks, the computer system (700) may communicate with other entities. Such communications may be one-way receive only (e.g., broadcast television), one-way transmit only (e.g., from a CANbus to a particular CANbus), or bidirectional, for example, to other computer systems using local or wide area digital networks. Specific protocols and protocol stacks may be used in each of these networks and network interfaces, as described above.

[0131] The aforementioned human interface devices, human accessible storage devices, and network interfaces may be attached to a core (740) of the computer system (700).

[0132] The cores (740) may include one or more central processing units (CPUs) (741), graphics processing units (GPUs) (742), specialized programmable processing units in the form of field programmable gate areas (FPGAs) (743), hardware accelerators for specific tasks (744), graphics adapters (750), etc. These devices may be connected through a system bus (748), along with read-only memory (ROM) (745), random access memory (746), internal mass storage such as a non-user accessible hard drive, SSD, etc. (747). In some computer systems, the system bus (748) may be accessible in the form of one or more physical plugs to allow expansion with additional CPUs, GPUs, etc. Peripheral devices may be either attached directly to the core's system bus (748) or attached through a peripheral bus (749). In one example, a screen (710) may be connected to the graphics adapter (750). Architectures for peripheral buses include PCI, USB, and the like.

[0133] The CPU (741), GPU (742), FPGA (743), and accelerator (744) may combine to execute certain instructions that may constitute the aforementioned computer code. The computer code may be stored in ROM (745) or RAM (746). Temporary data may also be stored in RAM (746), while persistent data may be stored, for example, in internal mass storage (747). Rapid storage and retrieval to any of the memory devices may be enabled through the use of cache memory, which may be closely associated with one or more of the CPU (741), GPU (742), mass storage (747), ROM (745), RAM (746), etc.

[0134] The computer-readable medium may have computer code thereon for performing various computer-implemented operations. The medium and computer code may be specially designed and constructed for the purposes of the present disclosure, or they may be of the kind well known and available to those skilled in the computer software arts.

[0135] As an example, and not by way of limitation, a computer system having the architecture (700), and in particular the core (740), can provide functionality as a result of a processor (including a CPU, GPU, FPGA, accelerator, etc.) executing software embodied in one or more tangible computer-readable media. Such computer-readable media can be media associated with the user-accessible mass storage introduced above, as well as specific storage of the core (740) of a non-transitory nature, such as the core internal mass storage (747), ROM 745, etc. Software implementing various embodiments of the present disclosure can be stored in such devices and executed by the core (740). The computer-readable media can include one or more memory devices or chips, depending on the particular needs. The software can cause the core (740), and in particular the processor therein (including a CPU, GPU, FPGA, etc.) to perform certain processes or certain portions of certain processes described herein, including defining data structures stored in RAM (746) and modifying such data structures according to the processes defined by the software. Additionally or alternatively, the computer system may provide functionality as a result of logic hardwired or otherwise embodied in circuitry (e.g., accelerator (744)), which may operate in place of or in conjunction with software to perform particular processes or particular portions of particular processes described herein. Reference to software may encompass logic, and vice versa, where appropriate. Reference to computer-readable medium may encompass circuitry (such as an integrated circuit (IC)) that stores software for execution, circuitry that embodies logic for execution, or both, where appropriate. The present disclosure encompasses any suitable combination of hardware and software.

[0136] While this disclosure has described several exemplary embodiments, there are alterations, substitutions, and various substitute equivalents which are within the scope of this disclosure. It will thus be appreciated that those skilled in the art will be able to devise many systems and methods which, although not explicitly shown or described herein, embody the principles of this disclosure and are within the spirit and scope of this disclosure.

Claims

1. 1. A method for media session management in wireless communications, comprising: obtaining, by a Vertical Application Layer (VAL) server, Session Description Protocol (SDP) information from a Session Initiation Protocol (SIP) payload associated with a media session for between a VAL client and the VAL server, the SDP information including a maximum bandwidth and a maximum bit rate allowed for the media session; sending, by a processing circuit of a media session management module of the VAL server, a network resource request including the SDP information to a network resource management (NRM) server, the NRM server being a Service Enabler Architecture Layer (SEAL) server, the network resource request requesting a network resource, the network resource being at least one of the maximum bandwidth and the maximum bit rate allowed for the media session; receiving, by the VAL server, an assessment of the network resource requirement from the NRM server, the assessment being based on at least one of the maximum bandwidth and the maximum bit rate allowed for the media session; and establishing or terminating the media session in the media session management module of the VAL server based on the received evaluation.

2. The method of claim 1 , wherein the network resource request is evaluated by the NRM server to grant the network resource request or to deny the network resource request.

3. The method of claim 1 , wherein terminating the media session is performed in response to a denial of the network resource request by the NRM server.

4. The method of claim 1 , wherein the media session is a SIP session.

5. The method of claim 4 , wherein the evaluation includes one of: (i) a denial of the network resource request; or (ii) a grant of the network resource request.

6. The method of claim 5 , wherein the network resource request further includes an identity of the VAL server and an identity of a VAL user equipment (UE).

7. A vertical application layer (VAL) server for media session management in wireless communications, comprising: A VAL server comprising a processing circuit of a media session management module of said VAL server, said processing circuit being configured to perform the method according to any one of claims 1 to 6.

8. A non-transitory computer readable medium storing instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 6.

Citation Information

Patent Citations

  • IPTV client terminal, sip-invite message generation method, IPTV system, IPTV session control method, computer program, IPTV client system, and session management device

    JP2009081828A

  • Method for operating a network and a network

    US20110320619A1

  • Session description protocol mechanisms for signaling radio access network capabilities in multimedia telephony sessions

    US20190373511A1

  • Seal system and method for provisioning inter-services communication in seal system of wireless communication network

    US20200178052A1

  • Framework for computing in radio access network (RAN)

    US20200404069A1